|
![]() [ View full size screenshot ] |
| Version | Date Released | Status | Release Notes |
| 1.3.166 | Apr 15, 2012 | New Release | · Issue 351: MySQL mode: can not create a table with the column "KEY", and can not open databases where such a table already exists. · TCP server: when using the trace option ("-trace"), the trace output contained unnecessary stack traces when stopping the server. · Issue 354: when using the multi-threaded kernel option, and multiple threads concurrently prepared SQL statements that use the same view or the same index of a view, then in some cases an infinite loop could occur. · Indexes on column that are larger than half the page size (wide indexes) could sometimes get corrupt, resulting in an ArrayIndexOutOfBoundsException in PageBtree.getRow or "Row not found" in PageBtreeLeaf. Also, such indexes used too much disk space. · Server mode: when retrieving more than 64 rows each containing a CLOB or BLOB, the error message "The object is already closed" was thrown. · ConvertTraceFile: the time in the trace file is now parsed as a long. · Invalid connection settings are now detected. · I |
| 1.3.161 | Oct 31, 2011 | New Release | · Issue 351: MySQL mode: can not create a table with the column "KEY", and can not open databases where such a table already exists. · TCP server: when using the trace option ("-trace"), the trace output contained unnecessary stack traces when stopping the server. · Issue 354: when using the multi-threaded kernel option, and multiple threads concurrently prepared SQL statements that use the same view or the same index of a view, then in some cases an infinite loop could occur. · Issue 350: when using instead of triggers, executeUpdate for delete operations always returned 0. · Some timestamps with timezone were not converted correctly. For example, in the PST timezone, the timestamp 2011-10-26 08:00:00Z was converted to 2011-10-25 25:00:00 instead of 2011-10-26 01:00:00. Depending on the database operation, this caused subsequent error. · Sequences with cache size smaller than 0 did not work correctly. |
| 1.3.159 | Aug 17, 2011 | New Release | · Creating a temporary table with the option 'transactional' will now also create the indexes in transactional mode, if the indexes are included in the 'create table' statement as follows: "create local temporary table temp(id int primary key, name varchar, constraint x index(name)) transactional". · The database file size grows now 35%, but at most 256 MB at a time. · Improved error message on network configuration problems. · The build now support an offline build using ./build.sh offline. This will list the required dependencies if jar files are missing. · The BLOB / CLOB data was dropped a little bit before the table was dropped. This could cause "lob not found" errors when the process was killed while a table was dropped. · "group_concat(distinct ...)" did not work correctly in a view or subquery (the 'distinct' was lost). Example: select * from (select group_concat(distinct 1) from system_range(1, 3)); |
| 1.3.158 | Jul 19, 2011 | New Release | · Fulltext search (native): after re-opening the connection once the fulltext index was created, a transaction rollback did not roll back the modifications in the index. · Support for ROW_NUMBER() OVER() as an alias for ROWNUM() for compatibility with PostgreSQL and Apache Derby. · Issue 325: a deadlock in the fulltext search could occur if the connection that was used while initializing the fulltext search was later used to query the database. This was actually not only a problem for fulltext search, but also for other triggers that used the initializing connection later on. · DATABASE_TO_UPPER: when set to false, all identifier names (table names, column names) are case sensitive (except aggregate, built-in functions, data types, and keywords). This is for improved compatibility with MySQL and PostgreSQL. · When upgrading from an older 1.3.x version to version 1.3.157, when using BLOB or CLOB data, the database could only be opened once. |