# Change Log ## Next Version (unreleased) PostgreSQL compatibility: support for EXTRACT(WEEK FROM dateColumn). Thanks to Prashant Bhat for the patch! Fix for a bug where we would sometimes use the wrong unique constraint to validate foreign key constraints. ## Version 1.3.169 (2012-09-09) The default jar file is now compiled for Java 6. The new jar file will probably not end up in the central Maven repository in the next few weeks because Sonatype has disabled automatic synchronization from SourceForge (which they call 'legacy sync' now). It will probably take some time until this is sorted out. The H2 jar files are deployed to http://h2database.com/m2-repo/com/h2database/h2/maven-metadata.xml and http://hsql.sourceforge.net/m2-repo/com/h2database/h2/maven-metadata.xml as usual. A part of the documentation and the H2 Console has been changed to support the Apple retina display. The CreateCluster tool could not be used if the source database contained a CLOB or BLOB. The root cause was that the TCP server did not synchronize on the session, which caused a problem when using the exclusive mode. Statement.getQueryTimeout(): only the first call to this method will query the database. If the query timeout was changed in another way than calling setQueryTimeout, this method will always return the last value. This was changed because Hibernate calls getQueryTimeout() a lot. Issue 416: PreparedStatement.setNString throws AbstractMethodError. All implemented JDBC 4 methods that don't break compatibility with Java 5 are now included in the default jar file. Issue 414: for some functions, the parameters were evaluated twice (for example "char(nextval(..))" ran "nextval(..)" twice). The ResultSetMetaData methods getSchemaName and getTableName could return null instead of "" (an empty string) as specified in the JDBC API. Added compatibility for "SET NAMES" query in MySQL compatibility mode. ## Version 1.3.168 (2012-07-13) The message "Transaction log could not be truncated" was sometimes written to the .trace.db file even if there was no problem truncating the transaction log. New system property "h2.serializeJavaObject" (default: true) that allows to disable serializing Java objects, so that the objects compareTo and toString methods can be used. Dylan has translated the H2 Console tool to Korean. Thanks a lot! Executing the statement CREATE INDEX IF ALREADY EXISTS if the index already exists no longer fails for a read only database. MVCC: concurrently updating a row could result in the row to appear deleted in the second connection, if there are multiple unique indexes (or a primary key and at least one unique index). Thanks a lot to Teruo for the patch! Fulltext search: in-memory Lucene indexes are now supported. Fulltext search: UUID primary keys are now supported. Apache Tomcat 7.x will now longer log a warning when unloading the web application, if using a connection pool. H2 Console: support the Midori browser (for Debian / Raspberry Pi) When opening a remote session, don't open a temporary file if the trace level is set to zero Use HMAC for authenticating remote LOB id's, removing the need for maintaining a cache, and removing the limit on the number of LOBs per result set. H2 Console: HTML and XML documents can now be edited in an updatable result set. There is (limited) support for editing multi-line documents. ## Version 1.3.167 (2012-05-23) H2 Console: when editing a row, an empty varchar column was replaced with a single space. Lukas Eder has updated the jOOQ documentation. Some nested joins could not be executed, for example: select * from (select * from (select * from a) a right join b b) c; MS SQL Server compatibility: ISNULL is now an alias for IFNULL. Terrence Huang has completed the translation of the H2 Console tool to Chinese. Thanks a lot! Server mode: the number of CLOB / BLOB values that were cached on the server is now the maximum of: 5 times the SERVER_RESULT_SET_FETCH_SIZE (which is 100 by default), and SysProperties.SERVER_CACHED_OBJECTS. In the trace file, the query execution time was incorrect in some cases, specially for the statement SET TRACE_LEVEL_FILE 2. The feature LOG_SIZE_LIMIT that was introduced in version 1.3.165 did not always work correctly (specially with regards to multithreading) and has been removed. The message "Transaction log could not be truncated" is still written to the .trace.db file if required. Then reading from a resource using the prefix "classpath:", the ContextClassLoader is now used if the resource can't be read otherwise. DatabaseEventListener now calls setProgress whenever a statement starts and ends. DatabaseEventListener now calls setProgress periodically while a statement is running. The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME. Issue 378: when using views, the wrong values were bound to a parameter in some cases. Terrence Huang has translated the error messages to Chinese. Thanks a lot! TRUNC was added as an alias for TRUNCATE. Small optimisation for accessing result values by column name. Fix for bug in Statement.getMoreResults(int) The SCRIPT statements now supports filtering by schema and table. Thanks a lot to Jacob Qvortrup for providing the patch! ## Version 1.3.166 (2012-04-08) 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. Issue 387: WHERE condition getting pushed into sub-query with LIMIT. ## Version 1.3.165 (2012-03-18) Better string representation for decimal values (for example 0.00000000 instead of 0E-26). Prepared statements could only be re-used if the same data types were used the second time they were executed. In error messages about referential constraint violation, the values are now included. SCRIPT and RUNSCRIPT: the password can now be set using a prepared statement. Previously, it was required to be a literal in the SQL statement. MySQL compatibility: SUBSTR with a negative start index now works like MySQL. When enabling autocommit, the transaction is now committed (as required by the JDBC API). The shell script `h2.sh` did not work with spaces in the path. It also works now with quoted spaces in the argument list. Thanks a lot to Shimizu Fumiyuki for the patch! If the transaction log could not be truncated because of an uncommitted transaction, now "Transaction log could not be truncated" is written to the .trace.db file. Before, the database file was growing and it was hard to find out what the root cause was. To avoid the database file from growing, a new feature to automatically rollback the oldest transaction is available now. To enable it, append ;LOG_SIZE_LIMIT=32 to the database URL (in that case, the oldest session is rolled back if the transaction log is 32 MB). ALTER TABLE ADD can now add more than one column at a time. Issue 380: ALTER TABLE ADD FOREIGN KEY with an explicit index didn't verify the index can be used, which would lead to a NullPointerException later on. Issue 384: the wrong kind of exception (NullPointerException) was thrown in a UNION query with an incorrect ORDER BY expression. Issue 362: support LIMIT in UPDATE statements. Browser: if no default browser is set, Google Chrome is now used if available. If not available, then Konqueror, Netscape, or Opera is used if available (as before). CSV tool: new feature to disable writing the column header (option writeColumnHeader). CSV tool: new feature to preserve the case sensitivity of column names (option caseSensitiveColumnNames). PostgreSQL compatibility: LOG(x) is base 10 in the PostgreSQL mode. ## Version 1.3.164 (2012-02-03) New built-in function ARRAY_CONTAINS. Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE. Trying to convert a VARCHAR to UUID will now fail if the text contains a character that is not a hex digit, '-', or not a whitespace. TriggerAdapter: in "before" triggers, values can be changed using the ResultSet.updateX methods. Creating a table with column data type NULL now works (even if not very useful). ALTER TABLE ALTER COLUMN no longer copies the data for widening conversions (for example if only the precision was increased) unless necessary. Multi-threaded kernel: concurrently running an online backup and updating the database resulted in a broken (transactionally incorrect) backup file in some cases. The script created by SCRIPT DROP did not always work if multiple views existed that depend on each other. MathUtils.getSecureRandom could log a warning to System.err in case the /dev/random is very slow, and the System.getProperties().toString() returned a string larger than 64 KB. The database file locking mechanism "FS" (;FILE_LOCK=FS) did not work on Linux since version 1.3.161. Sequences: the functions NEXTVAL and CURRVAL did not work as expected when using quoted, mixed case sequence names. The constructor for Csv objects is now public, and Csv.getInstance() is now deprecated. SimpleResultSet: updating a result set is now supported. Database URL: extra semicolons are not supported. ## Version 1.3.163 (2011-12-30) On out of disk space, the database could get corrupt sometimes, if later write operations succeeded. The same problem happened on other kinds of I/O exceptions (where one or some of the writes fail, but subsequent writes succeed). Now the file is closed on the first unsuccessful write operation, so that later requests fail consistently. DatabaseEventListener.diskSpaceIsLow() is no longer supported because it can't be guaranteed that it always works correctly. XMLTEXT now supports an optional parameter to escape newlines. XMLNODE now support an optional parameter to disable indentation. Csv.write now formats date, time, and timestamp values using java.sql.Date / Time / Timestamp.toString(). Previously, ResultSet.getString() was used, which didn't work well for Oracle. The shell script `h2.sh` can now be run from within a different directory. Thanks a lot to Daniel Serodio for the patch! The page size of a persistent database can now be queries using: select * from information_schema.settings where name = 'info.PAGE_SIZE' In the server mode, BLOB and CLOB objects are no longer closed when the result set is closed (as required by the JDBC spec). ## Version 1.3.162 (2011-11-26) The following system properties are no longer supported: `h2.allowBigDecimalExtensions`, `h2.emptyPassword`, `h2.minColumnNameMap`, `h2.returnLobObjects`, `h2.webMaxValueLength`. When using a VPN, starting a H2 server did not work (for some VPN software). Oracle compatibility: support for DECODE(...). Lucene fulltext search: creating an index is now faster if the table already contains data. Thanks a lot to Angel Leon from the FrostWire Team for the patch! Update statements with a column list in brackets did not work if the list only contains one column. Example: update test set (id)=(id). Read-only databases in a zip file did not work when using the -baseDir option. Issue 334: SimpleResultSet.getString now also works for Clob columns. Subqueries with an aggregate did not always work. Example: select (select count(*) from test where a = t.a and b = 0) from test t group by a Server: in some (theoretical) cases, exceptions while closing the connection were ignored. Server.createTcpServer, createPgServer, createWebServer: invalid arguments are now detected. The selectivity of LOB columns is no longer calculated because indexes on LOB columns are not supported (however this should have little effect on performance, as the selectivity is calculated from the hash code and not the data). New experimental system property "h2.modifyOnWrite": when enabled, the database file is only modified when writing to the database. When enabled, the serialized file lock is much faster for read-only operations. A NullPointerException could occur in TableView.isDeterministic for invalid views. Issue 180: when deserializing objects, the context class loader is used instead of the default class loader if the system property "h2.useThreadContextClassLoader" is set. Thanks a lot to Noah Fontes for the patch! When using the exclusive mode, LOB operations could cause the thread to block. This also affected the CreateCluster tool (when using BLOB or CLOB data). The optimization for "group by" was not working correctly if the group by column was aliased in the select list. Issue 326: improved support for case sensitive (mixed case) identifiers without quotes when using DATABASE_TO_UPPER=FALSE. ## Version 1.3.161 (2011-10-28) 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. Issue 356: for Blob objects, InputStream.skip() returned 0, causing EOFException in Blob.getBytes(.., ..). Updatable result sets: if the value is not set when inserting a new row, the default value is now used (the same behavior as MySQL, PostgreSQL, and Apache Derby) instead of NULL. Conditions of the form IN(SELECT ...) where slow and increased the database size if the subquery result size was larger then the configured MAX_MEMORY_ROWS. Issue 347: the RunScript and Shell tools now ignore empty statements. Issue 246: improved error message for data conversion problems. Issue 344: the build now supports a custom Maven repository location. Issue 334: Java functions that return CLOB or BLOB objects could not be used as tables. SimpleResultSet now supports getColumnTypeName and getColumnClassName. SimpleResultSet now has minimal BLOB and CLOB support. Improved performance for large databases (many GB), and databases with a small page size. The Polish translation has been improved by Jarosław Kokociński. When using the built-in connection pool, after calling the "shutdown" SQL statement, a warning was written to the .trace.db file about an unclosed connection. Improved compatibility for "fetch first / next row(s)". Thanks a lot to litailang for the patch! Improved compatibility with the Java 7 FileSystem abstraction. ## Version 1.3.160 (2011-09-11) Computed columns could not refer to itself. Issue 340: Comparison with "x = all(select ...)" or similar in a view or subquery that was used as a table returned the wrong result. Comparison with "x = all(select ...)" or similar returned the wrong result for some cases (for example if the subquery returned no rows, or multiple rows with the same value, or null, or if x was null). Issue 335: Could not run DROP ALL OBJECTS DELETE FILES on older databases with CLOB or BLOB data. The problem was that the metadata table was not locked in some cases, so that a rollback could result in a corrupt database in a database if the lob storage was upgraded. Source code switching using //## has been simplified. The Java 1.5 tag has been removed because is no longer needed. The JDBC methods PreparedStatement.setTimestamp, setTime, and setDate with a calendar, and the methods ResultSet.getTimestamp, getTime, and getDate with a calendar converted the value in the wrong way, so that for some timestamps the converted value was wrong (where summertime starts, one hour per year). Invalid tables names in 'order by' columns were not detected in some cases. Example: select x from dual order by y.x Issue 329: CASE expression: data type problem is not detected. Issue 311: File lock mode serialized: selecting the next value from a sequence didn't work after a pause, because the database thought this is a read-only operation. ## Version 1.3.159 (2011-08-13) 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)); Database URLs can now be re-mapped to another URL using the system property "h2.urlMap", which points to a properties file with database URL mappings. When using InputStream.skip, trying to read past the end of a BLOB failed with the exception "IO Exception: Missing lob entry: ..." [90028-...]. The in-memory file system "memFS:" now has limited support for directories. To test recovery, append ;RECOVER_TEST=64 to the database URL. This will simulate an application crash after each 64 writes to the database file. A log file named databaseName.h2.db.log is created that lists the operations. The recovery is tested using an in-memory file system, that means it may require a larger heap setting. Converting a hex string to a byte array is now faster. The SQL statement "shutdown defrag" could corrupt the database if the process was killed while the shutdown was in progress. The same problem could occur when the database setting "defrag_always" was used.