Newer Sun Java versions throw expections if java.sql.Date.valueOf is not in yyyy-mm-dd format. http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6898593

Workaround for a java.sql.Date issue: years above 9999 are not formatted correctly. When calling ResultSet.getString() on a date value, an alternative formatting algorithm is used.

ROWNUM could not be used for pagination. The follow query returned no rows: select x from (select *, rownum as r from system_range(1, 3)) where r=2;

Prepared statements with nested subqueries did not always return the correct result. Example: select ?, ?, (select count(*) from test t, (select id from test where 0=?) t2 where t2.id=t.id) from test

--no commit message

When using MULTI_THREADED=TRUE, the exception following exception could be thrown: "object already exists: TABLES"

When using the multi-threaded mode, running ANALYZE concurrently in multiple connections could throw an exception.

Improved MS SQL Server compatibility: support string concatenation using "+". Thanks to Stepan for the patch!

When using the multi-threaded mode, running ANALYZE concurrently in multiple connections could throw an exception.

Multi-column indexes where the second or later column was descending did not always produce correct results.

--no commit message