# Change Log

## Next Version (unreleased)

- If the user name and password are not set or empty, then the password is not hashed. To disable this behavior, set the system property h2.emptyPassword to false. TCP server: the default user name for the management database is now an empty string.
- Cluster: auto-commit was disabled after opening a connection.
- Connection.getAutoCommit() is now much faster, specially when using the server mode.
- Statement.cancel() had no effect when using the server mode.
- SCRIPT: the SQL script no longer contains settings that match the default value.
- Statement.cancel() did not work when running RUNSCRIPT and SCRIPT.
- Statement.cancel() could cause a NullPointerException.
- In some cases (specially when using a small cache size or a large database over 1 GB) for some operations like ALTER TABLE the data was written before the transaction log entries, which could cause a corrupt database if the process was killed during the ALTER TABLE operation. Thanks a lot to Victor Pyankov for helping solve this problem!
- The Recover tool could throw a ArrayIndexOutOfBoundsException when trying to recover a corrupt database file.
- The SCRIPT command and tool now uses the default file encoding for the system now instead of UTF-8 (as before). In most cases, this will not affect existing applications, as the encoding only affects how SQL identifiers (table names and so on) that contain special characters are stored. Table data is escaped, and therefore is no problem.
- The SCRIPT command and tool now also support the CHARSET option (like RUNSCRIPT).
- When closing a database, sometimes empty space in the database was not freed up.
- Trying to create a view with parameters in the query will now throw an exception. So far, creating the view was allowed, but the parameter value was not used (null was used instead).
- New experimental feature SHUTDOWN DEFRAG. This option re-orders the pages while closing the database so that table scans are faster.
- When using the MULTI_THREADED option, concurrently reading from a database (specially from a larger database, or when using a small cache size) could throw an exception.
- When adding a comment to a column that has a check constraint, the database couldn't be re-opened.
- New system property h2.lobClientMaxSizeMemory to set the maximum size of a LOB object to keep in memory on the client side when using the server mode.

## Version 1.2.142 (2010-08-31)

- Documentation for using H2 on Android devices has been added under Tutorial - Android.
- An ArrayIndexOutOfBoundsException was thrown when querying the table information_schema.function_aliases while there are any user defined aggregate functions.
- The jar files are now about 50 KB smaller. In the last few versions they contained superfluous classes.
- The default time to compact a database when closing (system property h2.maxCompactTime) is now 0.2 seconds instead of 1 second.
- Opening an closing a database is now faster.
- In theory, when using indexes with large index rows (or when using a very small page size), removing rows could throw an internal exception in some cases.
- Inserting rows in reverse order could throw an ArrayIndexOutOfBoundsException in some cases (specially rows larger than the page size, which is 2 KB by default). Issue 226.
- H2 Console: with Chrome and Safari, resizing the table/query frame doesn't work. Issue 225.
- New experimental database file locking mechanism "FS" to use native file locking (no *.lock.db file is created in this case, and no background thread is started). This mechanism may not work on all systems (on some systems it's possible to lock the same file multiple times within the same virtual machine, and on some system native file locking is not working or unlocking is not working).

## Version 1.2.141 (2010-08-22)

- New experimental pseudo-encryption algorithm "FOG". It makes the data appear to be encrypted. This algorithm is cryptographically extremely weak, and should only be used to hide data from reading the plain text using a text editor. Please let us know if you think this is useful or not.
- Documentation: the grammar and function documentation can now be easier translated.
- Password hash: in addition to connecting with the plain text password, H2 now supports connecting with the password hash. Like this you don't have to store plain text passwords in config files. For details, see the documentation at Advanced / Password Hash.
- Lucene 3.x support was added in the source code, however it is not yet enabled by default and is not yet supported when using the default h2 jar file. To enable Lucene 3.x support, the source code of H2 needs to be switched using `./build.sh -Dlucene=3 switchSource`, and then re-compile. To switch the source code back use `./build.sh -Dlucene=2 switchSource` (replace ./build.sh with build.bat on Windows). The plan is to use Lucene 3 by default in H2 version 1.3.x. Issue 147.
- The native fulltext search could cause a Java level deadlock if searching from multiple connections concurrently.
- CREATE FORCE VIEW didn't work in most cases if a referenced table didn't exist.
- MVCC: when trying to insert two rows with the same key from two connections, the second connection immediately threw the exception "Unique index or primary key violation". Instead, the second connection now waits throwing the exception until the first connection committed the change (same as when trying to concurrently update the same row).
- Server mode: if the client ran with a different timezone setting than the server, date values got shifted by the difference between the timezones. This problem affected the data types DATE, TIME, and TIMESTAMP, when using PreparedStatement.setDate / setTime / setTimestamp and ResultSet.getDate / getTime / getTimestamp. To solve the problem, both the client and the server need to be updated (otherwise the old transfer protocol is used).
- The built-in connection pool (JdbcConnectionPool) did not always honor the login timeout (the timeout could occur much too early). Thanks a lot to Dario Fassi for the patch!
- Translation: the new messages have been translated to Spanish. Thanks a lot to Dario Fassi!
- The table INFORMATION_SCHEMA.SETTINGS now contains all H2-specific system properties (the ones that start with "h2.") and that are explicitly set. Previously, some H2-specific settings (for example h2.analyzeAuto) were missing in this list.
- EXPLAIN ANALYZE with an in-memory database threw an exception. Issue 216.
- Data modifications (inserts, updates, and deletes) are now up to 5 times faster because converting objects to byte arrays is avoided if possible.
- LOG=0 is now a bit faster (previously undo log entries were still written).
- The command line tools now say so if the source directory of an option doesn't exist.
- It is now allowed to truncate a table if referential integrity has been disabled for this table or database.
- For unencrypted databases, the automatic upgrade temporary script file is now unencrypted again.

## Version 1.2.140 (2010-07-25)

- The default MAX_LOG_SIZE is now 16 MB instead of 2 MB. Some uses cases are 3 times faster now.
- Improved cache memory usage calculation.
- Only resources that are actually used are loaded in memory. This can reduce the memory usage by about 400 KB.
- Profiling: the jar file can now be installed as an agent using java -javaagent:h2*.jar - this was be used to more accurately calculate the memory footprint of the cache. It has no effect when using H2 (using this feature in an application is not needed and not recommended).
- The cache was not used efficiently when reading (behaving like a FIFO cache instead of an LRU cache).
- Storing lobs in the database has been changed. It is now faster. Unfortunately, the change is not backward compatible; if you have used h2.lobInDatabase before you will need to re-build the database.
- SHUTDOWN COMPACT is now faster.
- H2 Console: requesting the status did not always show the window on top of others.
- H2 Console: on some system, the browser windows got opened when requesting a new one.
- The built-in profiling tool now uses a default stack depth of 32 elements and a default interval of 10 ms.
- Database files now grows in 1 MB blocks (and at least 20% at a time), instead of always 256 KB. This speeds up loading a new database.
- H2 Console: new built-in command @sleep to help profile another session.
- For improved performance, LOG=0 and LOG=1 are again supported. LOG=0 means the transaction log is disabled completely (fastest; for loading a database). LOG=1 means the transaction log is enabled, but FileDescriptor.sync is disabled (if no protection against power failure is required). LOG=2 is the default (transaction log is enabled, FileDescriptor.sync for each checkpoint).
- After deleting a lot of data (for example by dropping or altering tables, or indexes, or after a large transaction), opening a large database was very slow. Fixed.
- When killing the process after creating and dropping many tables (specially temporary tables), the database could not be opened sometimes.
- CAST(NULL AS ...) doesn't forget the data type, precision, and scale any longer.
- Experimental support for recursive queries (see 'Advanced' - 'Recursive Queries' for details).
- Problems with JDK 1.6.0_18 have been reports in the class StringUtils.quoteRemarkSQL. This method is now changed.
- The "small jar" distribution did not include the CompressTool, which was required for some operations. Fixed.
- The build tool now supports (minimalistic) shell mode, started using ./build.sh -
- IS NULL comparison with nested queries and linked tables did not work. Example: select * from (select x from test) where x is null.
- Support for null-safe equals. This includes the ANSI SQL standard syntax A IS [NOT] DISTINCT FROM B as well as the shorter A IS [NOT] B.
- Primary key violations threw a strange exception message when using a single column INT or BIGINT key.
- EXPLAIN ANALYZE now also lists the number of pages read from the file.
- Memory mapped files: There was a bug in version 1.2.139 so that memory mapped files could only be used together with split, for example: split:nioMapped: - the problem is now solved. It is still a good idea to use split:nioMapped: to work around the 2 GB limitation of memory mapped files.
- Memory mapped files: the system property h2.nioCleanerHack is now disabled by default because it was not always working as expected. Now System.gc() is used in a loop until the buffer is garbage collected. This of course is also not a nice solution, but the only one known to work. See also http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4724038
- Bugfixes for the automatic 1.1 db migration.
- If an old 1.1 database file version is found on connect, it is now possible to let the old h2 classes (v 1.2.128) connect to the database. The automatic upgrade .jar file must be present, and the url must contain NO_UPGRADE=TRUE
- The automatic upgrade temporary script file is now encrypted.

## Version 1.2.139 (2010-07-10)

- There was a bug in the internal IntIntHashMap. There were no known side effects however.
- ANALYZE now uses less memory.
- Memory mapped file system: improved error messages if there is a problem.
- The Lucene fulltext search did not work well when using special file systems such as split or nioMapped.
- The memory mapped file system (nioMapped: file prefix) couldn't seek past the file length.
- Some file system operations did not work with stacked file systems (for example split and nioMapped). This also affected the DeleteDbFiles tool.
- New experimental query cache. The cache is only used if the SQL statement and all parameters match. Each session has it's own cache with the given size. Only the last returned result per query is cached. Only SELECT statements are cached (excluding UNION and FOR UPDATE statements). This works for both statements and prepared statement. To enable, set the system property h2.commandCacheSize to a value larger than 0. There is currently no plan to enable this option by default in future versions.
- Conditions with many OR operations could throw an UnsupportedOperationException if h2.optimizeOr was enabled.
- XA connection: after transaction commit or rollback, the physical connection is set into autocommit mode.
- MULTI_THREADED did not work correctly and could throw the exception "try to add a record twice" for larger databases because cache access was not correctly synchronized.
- Automatic database upgrade from non page store is now possible. If the classes from the h2mig_pagestore_addon.jar file are in the classpath, the database will be converted to the current page store format automatically. The file can be found here: http://h2database.com/h2mig_pagestore_addon.jar
- The MultiDimension tools was extended with a few helper methods. The API was unified a bit.
- ODBC: MS Access could not link to a table with unique index or primary key. To solve this problem, index meta data is currently disabled for ODBC. When using the new H2 version to access a database over ODBC, the PostgreSQL catalog is automatically upgraded. Using a database with an upgraded PostgreSQL catalog with an older version of H2 is still possible, but not over ODBC.
- ODBC: MS Access could not link to a table with a name containing '_'.
- ODBC: additional connection settings can now be added to the database name. Example: ~/test;cipher=xtea. Therefore, encrypted databases are supported.
- Local temporary tables can now be created without having to commit a transaction using CREATE LOCAL TEMPORARY TABLE TEMP(ID INT PRIMARY KEY) TRANSACTIONAL.
- New system property h2.dropRestrict (default false) to change the default action for DROP TABLE and DROP VIEW (false for CASCADE, true for RESTRICT). The plan is to enable this property by default in version 1.3.x.
- DROP TABLE now also supports CASCADE (still the default) and RESTRICT.
- The wrong exception was thrown when trying to connect to a server if the server was not running.
- UNION queries where the first query contains a nested query were parsed incorrectly. Example: "select 1 from (select 2 from dual) union select 3 from dual" was parsed as "select 1 from ((select 2 from dual) union select 3 from dual)". Fixed.
- Support ALTER SCHEMA name RENAME TO newName (rename schema). (patch from Kerry Sainsbury)

## Version 1.2.138 (2010-06-27)

- Referential integrity: it was not allowed to delete a row with NULL in the parent table, if there was a row with NULL in the child table.
- Experimental feature to support case sensitive catalog names and database names using the DATABASE() method. To use this feature, set the system property h2.databaseToUpper to false. The plan is to set the property to false by default in version 1.3.x. Issue 204 - thanks to Sylvain Cuaz (ILM Informatique) for the patch.
- Experimental feature to support nested joins. To enable, set the system property h2.nestedJoins to true. If enabled, nested joins and right outer joins should work as expected (issues 145, 177, and 203). The plan is to enable this feature by default in version 1.3.x.
- New sample application: CachedPreparedStatements.
- When creating functions within a schema, those functions could not be used in views, nested queries, and constraints. Fixed.
- The benchmarks have been run using recent database versions.
- Version 1.2.137 could still not be converted to Java 1.4 (because the Retrotranslator doesn't support BigDecimal.precision).
- Cluster: non-admin users could not connect when one of the cluster node was stopped. Issue 206.
- DROP VIEW now supports the CASCADE and RESTRICT clauses (patch from Kerry Sainsbury)
- CREATE VIEW now supports the OR REPLACE clause (patch from Kerry Sainsbury)
- Build tool: ability to only run one test using the -Dtest=className setting. eg: build -Dtest=org.h2.test.db.TestViewDropView test (patch from Kerry Sainsbury).

## Version 1.2.137 (2010-06-06)

- Statements with a nested query and a condition that was always NULL threw an IndexOutOfBoundsException. Example: select * from (select null as x) where x=1
- The changes that were made to support large transactions also fixed a bug with large transactions (when the undo log file size is larger than 2 GB).
- Experimental feature to support very large transactions (except when using MVCC). To enable, set the system property h2.largeTransactions to true. If enabled, changes to tables without a primary key can be buffered to disk. The plan is to enable this feature by default in version 1.3.x.
- H2 Console: editing result sets is now also working for database other than H2, if they do support updatable result sets. Add "@edit" before the query. Only limited testing has been done on this feature, some data types may not work (please provide feedback if you find issues).
- Cluster: an open transaction was committed when a cluster node was stopped (because disabling the cluster executes SET CLUSTER '', which committed the transaction). Transaction are no longer committed when calling SET CLUSTER. Issue 199.
- Cluster: non-admin users couldn't connect to the cluster and couldn't disable the cluster. Issue 201.
- Cluster: NEXTVAL('sequence') was only called on one cluster node, therefore sequence values could get out of sync.
- Version 1.2.136 could not be converted to Java 1.4 (because the Retrotranslator doesn't support BigDecimal.precision). A workaround has been implemented.
- The error code of IO exceptions in CSV functions was incorrect.
- The TriggerPassData example now uses a prefix (the database name).
- The wrong exception was thrown when trying to reference a table that doesn't support references such as a table in the information schema.
- Server.shutdownTcpServer can now stop all TCP servers on this JVM.
- JdbcConnectionPool: the default connection timeout is now 30 seconds (it used to be 5 minutes).
- LOB storage: LOBs added with "h2.lobInDatabase" enabled couldn't be read later with this option disabled.

## Version 1.2.136 (2010-05-24)

- When using ORDER BY and there are both ascending and descending indexes, the database used the first index even when the second one could be used for sorting.
- Conditions of the form columnName IS NULL now use an index. To disable this feature, set the system property h2.optimizeIsNull to false.
- H2 Console: when the settings were not stored yet (for example when running for the first time), the last recently used settings were not stored. A workaround was to create the file ".h2.server.properties" manually in the current user home directory, with the contents: webAllowOthers=false, webPort=8082, webSSL=false, 0=Generic H2 (Embedded)|org.h2.Driver|jdbc\:h2\:~/test|sa (where a comma is a newline).
- The source code is now switched to Java 6 (JDK 1.6) by default. Java 5 (JDK 1.5) is still supported, and the jar file is still compiled for Java 5.
- The BOM (the byte-order-mark) character 0xfeff at the beginning of the file is ignored. This is for compatibility with Microsoft Excel.
- When opening an existing database, the cache size is set to at most half the amount of memory available for the virtual machine (Runtime.getRuntime().maxMemory()), even if the cache size setting stored in the database is larger. Setting the cache size in the database URL or explicitly using SET CACHE_SIZE overrides this value (even if larger than the physical memory).
- INFORMATION_SCHEMA.SETTINGS: the cache size is now returned in KB.
- New system property h2.selectForUpdateMvcc, the default is false (the feature is disabled). When enabled, SELECT ... FOR UPDATE only locks the selected rows in the MVCC mode. Aggregate or GROUP BY queries are not allowed in this case.
- Profiler: improved message if there was no stack trace.
- The H2 Console can now be used within another application, in a frame or iframe. Issue 197.
- Recover tool: the statistics section now includes page type counts again.
- Queries with multiple IN(...) conditions sometimes return the wrong results when there was a multi-column index for the column.
- Queries with IN(..., NULL) did sometimes return the wrong results when there was a index for the column.
- DECIMAL: faster precision and memory usage calculations.
- A new class org.h2.tools.TriggerAdapter allows to use the ResultSet interface within trigger implementations.
- A subselect which used an index could lead to wrong results. Fixed.
- Creating a cached temporary non persistent table with a primary key threw a NullPointerException.

## Version 1.2.135 (2010-05-08)

- Temporary files were not deleted when using large transactions, disabling autocommit, and closing the session without committing.
- Queries using multiple IN(..) conditions on the same table could cause repeated rows in the result set.
- Translation: Lubomir Grajciar translated the H2 Console as well as all error message to Slovensky. Thanks a lot!
- There was a possible Java level deadlock when opening an uninitialized database and using a file system that also opened a database.
- When killing the process while the database was writing a checkpoint, while it was closing, or while running recovery (while removing temporary tables from a previous run), the database could become corrupt. A new test case has been implemented to ensure such problems can not occur in the future.
- File system: new method FileSystem.setReadOnly.
- The page size for new databases can now be set in the database URL using ;PAGE_SIZE=512. Currently this feature is only used to simplify testing.
- New system property h2.functionsInSchema (default is false). If enabled, the SCRIPT statement always includes the schema name in the CREATE ALIAS statement (even if the schema is PUBLIC). This is not backward compatible with H2 versions 1.2.134 and older.
- Functions: it is no longer required to add a space after a comma in the parameter list. Example: CREATE ALIAS PARSE_INT FOR "java.lang.Integer.parseInt(java.lang.String,int)"
- Functions now reside within a schema, similar to sequences. If you do create such functions in schemas other than PUBLIC, then the database can not be opened with older versions of H2.
- Cluster: after a cluster node failed, the second cluster node can now be re-created and started without having to stop the first cluster node, and without having to stop running applications. To do that, append ;AUTO_RECONNECT=TRUE to the database URL.
- Auto-reconnect: if another connection uses the database in exclusive mode then this connection will try to re-connect until the exclusive mode ends. This is important when using the cluster mode.
- SET EXCLUSIVE now supports 0 (disable), 1 (enable), and 2 (enable and close all other connections).
- Installing the H2 as a service should now work on Windows 7. The batch files now explicitly set the directory using pushd "%~dp0".
- Temporary tables can now be 'cached', that means indexes of temporary tables can be persisted. This enables very large temporary tables (both local and global).
- The CreateCluster tool now sets the source database in exclusive mode before copying data to the new database.
- The H2 Console now stream results one statement / result set at a time (using chunked transfer encoding). To disable, set the system property h2.consoleStream to false. This feature is not supported when using a servlet container.
- The H2 Console did not call the CreateCluster tool with the correctly escaped parameters.
- Improved PostgreSQL compatibility for ALTER TABLE ALTER COLUMN.
- Commas at the end of INSERT ... VALUES (), (), are now supported.
- The H2 Console "Start Browser" button now works even when the IP address changes while the tool runs (for example, because a wireless connection breaks, or when enabling / disabling the network connection).
- When casting from float or double to BigDecimal, the result was sometimes unexpected, because "new BigDecimal(double val)" was used. Now "BigDecimal.valueOf(double val)" and "new BigDecimal(Float.toString(f))" are used. But it is still not recommended to use float or double for currency values (see data type documentation).
- Global temporary tables are now deleted when closing the database. Before, they were deleted when opening the database the next time.
- UNIQUE was not listed as a keyword.
- Improved error message when an non-SQL-exception occurred in a user defined function. The method name and parameters are included in the error message.
- For some queries, the exception did not include the SQL statement. Example: select x from system_range(1, 2) group by 'a'.
- The Shell tool will execute SQL statements passed as using the command line parameter -sql.
- If InetAddress.getLocalHost() fails, the database should now throw an exception.
- New columns INFORMATION_SCHEMA.INDEXES.INDEX_CLASS and INFORMATION_SCHEMA.TABLES.TABLE_CLASS.
- INFORMATION_SCHEMA.INDEXES.SQL now contains the CREATE INDEX statement instead of just the fully qualified index name.

## Version 1.2.134 (2010-04-23)

- New system property h2.analyzeAuto (default 0 meaning disabled) to automatically run ANALYZE after that many changes to a table. For details, see the Javadoc of this system property. The plan is to set this property to 2000 in version 1.3.x.
- JdbcXAConnection.start() does not support TMJOIN. Issue 189.
- MySQL compatibility: TIMESTAMPDIFF is now an alias for DATEDIFF.
- MERGE did not respect foreign key and check constraints.
- ALTER TABLE ALTER COLUMN: changing the data type of a column no longer makes it nullable.
- When using AUTO_SERVER=TRUE, the server is now started as a daemon thread. This was a problem when using Tomcat and a connection pool.
- Servers can now be started as a daemon thread using the command line options -tcpDaemon, -pgDaemon, and -webDaemon.
- H2 Console: the built-in commands are now documented.
- REPLACE: if any parameter is null, the result is null.
- Queries with DISTINCT and ORDER BY will now use the index on ORDER BY if possible. This is specially important for queries used inside IN(SELECT ...).
- The new statement EXPLAIN ANALYZE executes the statement, and displays the query plan with the actual row scan count for each table.
- H2 Console: the auto-complete feature didn't quote column names that need quoting. Issue 186.
- The experimental LOB storage mechanism now supports all features of the old one. To use it, set the system property "h2.lobInDatabase" to "true". If you have used this feature in version 1.2.133, you need to export and re-import the database using SCRIPT / RUNSCRIPT.
- The functions isBeforeFirst() and isAfterLast() were not compliant to the JDBC spec. If the ResultSet contains no rows, they must return false. Fixed.
- Filesystem parameters like "split:" didn't work in server mode with baseDir set.
- If baseDir is set, and a database name is given which points to a directory outside the baseDir (eg. "../dbname"), an exception is thrown.

## Version 1.2.133 (2010-04-10)

- A new experimental LOB storage mechanism is available. When enabled, CLOB and BLOB data is stored in hidden tables in the database. To use it, set the system property "h2.lobInDatabase" to "true". Compression is not yet implemented. Duplicate objects are only stored once. Usually writing is slower, but reading is faster (mainly because of caching).
- The Shell tool threw a NumberFormatException on a empty statement.
- The h2small-*.jar did not support "drop all objects delete files". Now it is supported (the DeleteDbFiles tool is now included).
- Operations that don't fit in memory are now faster. Temporary file handling was changed.
- The default maximum log stream size is now 2 MB. This is a good value according to some performance tests.
- New system property "h2.syncMethod" to configure what method to call when closing the database, on checkpoint, and on CHECKPOINT SYNC. The default is "sync" which calls RandomAccessFile.getFD().sync().
- 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;
- 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.
- 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
- When using MULTI_THREADED=TRUE, the exception following exception could be thrown: "object already exists: TABLES"
- Comparison of integer columns against float numbers was not always correct. Issue 182.
- H2 Console: Editing the result of a multi-line queries failed. Issue 183.
- H2 Console: if the settings file (.h2.properties) can't be accessed, the exception is now ignored.

## Version 1.2.132 (2010-03-21)

- The implementation of a Java to C (source code level) converter has been started. The plan is: it should be possible to convert H2 (or a part of it) to C so that the database can be run without a JVM. This will be a long term project (it may take a year or so).
- User defined table implementation can now be used using CREATE TABLE ... ENGINE. Thanks to Sergi Vladykin for implementing this feature!
- 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.
- The MERGE statement is now about 30% faster when using a PreparedStatement.
- Multi-column indexes where the second or later column was descending did not always produce correct results (rows were missing in the result set, or the result set was empty).
- When using large transactions or a small log size, the database could get very slow (profiling shows the hotspot is in FileObjectDisk.sync()).
- The Shell tool now prints the stack trace when the list mode is enabled.
- CREATE ALIAS ... AS: Compilation was incorrect if the source code contained characters that are not supported by the default file encoding.
- Issue 176: the JdbcDataSource now also supports a 'description' property.
- The Shell tool threw a ArrayIndexOutOfBoundsException after 20 statements.
- When using the small version of H2 ('jarClient'), the first call to Connection.createBlob (or similar) could throw a ClassNotFoundException because the file org.h2.store.fs.FileSystemZip is not included. This missing class is now ignored.
- Literals of type BIGINT now have the correct data type.

## Version 1.2.131 (2010-03-05)

- Older versions of H2 (version 1.2.127 and older) could not connect to a new version (version 1.2.129 and newer). The connection blocked when trying to connect. Now the connection no longer blocks, instead a SQL exception is thrown.
- In versions 1.2.129 and 1.2.130, a database could not be opened sometimes after dropping tables or indexes, and then creating new indexes for existing tables. The exception contained the text "parent not found" (version 1.2.129) or "Table not found" (version 1.2.130).
- After the database was closed, a null pointer exception could occur in Database.flush.
- An ArrayIndexOutOfBoundsException could occur in the page store (eg. on "delete from table"). Fixed.

## Version 1.2.130 (2010-02-26)

- EXPLAIN: The query plan now contains ".tableScan" if a table scan is used.
- IN(..): when combining and IN(..) condition with a condition that didn't use an index, the result could contain duplicate rows.
- IN(..): the index was not used if there were multiple IN(..) conditions.
- For foreign key constraints, the metadata column INFORMATION_SCHEMA.INDEXES.CONSTRAINT_NAME was not set for non-unique indexes.
- PostgreSQL compatibility: when using the following exception was thrown: Column "T.TYPTYPMOD" not found. Fixed. This is only when using psqlodbc_08_04*.
- A tool to migrate an old database from the non-page store format to the newest version has been added in src/tools/org/h2/dev/util/Migrate.java. This file is not included in the jar file currently.
- When using temporary tables, the database didn't shrink sometimes when closing. Also, sometimes a database could not recover normally.
- Large transactions could run out of heap space. The maximum size of a transaction is now much larger.
- The default setting for the system property h2.webMaxValueLength is now 100000 (it was 10000 before).
- Creating a database was delayed about 2 seconds if the directory didn't exist.
- Implemented INIT feature. If the database URL contains ";INIT=...;" then the DDL or DML commands following are executed on startup. Example URL: jdbc:h2:mem:test;INIT=RUNSCRIPT FROM '~/create.sql' (patch from Kerry Sainsbury).

## Version 1.2.129 (2010-02-19)

- The methods of the CloseListener are added to the Trigger interface. The interface CloseListener is removed. This is potentially a breaking change for existing triggers.
- CREATE ALIAS: error message when compiling Java code have been improved.
- MVCC: creating a table with an incorrect constraint could cause strange errors.
- Hash indexes now are only used for single column indexes.
- The cache types WEAK_* and TQ are no longer supported. A weak reference cache never frees up memory so it's the same as having a very large cache size. The TQ cache was not included in the jar file since a longer time, and was not tested.
- The file system abstraction no longer throws SQL exceptions.
- DatabaseEventListener.diskSpaceIsLow has changed.
- The CompressTool no longer throw as SQL exceptions. Instead, it throws runtime exceptions.
- SimpleResultSet.addColumn and addRow now can throw a IllegalStateException instead of a SQLException.
- When doing an index lookup, decimal values with the same value but different scale (for example 0.00 and 0.0) where not considered equal in version 1.2.128. Now they are (unlike BigDecimal.equals()).
- The BNF parser now uses the visitor pattern.
- Converting a UUID to bytes was incorrect. Because of that, updatable result sets on tables with UUID primary key did not work.
- The database URL property DATABASE_EVENT_LISTENER_OBJECT is no longer supported (there are problems passing objects when the PostgreSQL driver is installed as well).
- H2 Console: asynchronous login (using a DatabaseEventListener) is no longer supported.
- A workaround for a Windows socket problem has been implemented. Thanks a lot to Sergi Vladykin.
- The Recover tool did not convert correctly convert CLOB data with non-ASCII characters.
- Tools: the method run(String... args) has been renamed to runTool(String... args).
- Server.startWebServer(Connection) was not working as expected.
- The database URL option ACCESS_MODE_LOG is no longer supported.
- The database URL option RECOVER has currently no effect.
- Converting an old (non-page store) database is no longer supported using this version.
- The following system properties are no longer supported: h2.overflowExceptions, h2.optimizeDropDependencies, h2.optimizeGroupSorted, h2.optimizeMinMax, h2.optimizeNot, h2.optimizeIn, h2.optimizeInJoin, h2.reuseSpace*. Most of then were there for a long time, but always with the same value. There was no unit test with the other value. So changing them was potentially dangerous (not a lot, but still).
- The setting LOG has currently no effect (it only had an effect when the page store was disabled).
- Disabling the page store is no longer supported. The old storage mechanism has been removed, shrinking the jar file size by almost 10%.
- The translated resources are now stored in UTF-8 format.
- The Windows service wrapper now detects if multiple versions of H2 are installed.

## Version 1.2.128 (2010-01-30)

- There are known errors on rollback when the page store is disabled and at the same time MVCC is used. See http://code.google.com/p/h2database/issues/detail?id=158
- The DeleteDbFiles tool deleted all files in the .lob.db directory, even files that didn't belong to the database.
- Automatic conversion of old databases to the page store format failed if the database contained LOB files.
- Nested subqueries didn't work for INSERT INTO and IN(..). Example: insert into test ((select 1));
- If the database was already closed using SHUTDOWN IMMEDIATELY, closing a second connection could throw a NullPointerException if there was a local temporary table.
- Less classes are loaded when using the database in embedded mode.
- The information schema tables are only initialized when needed. This reduces memory usage and speeds up creating in-memory databases. Each in-memory database needs about 8 KB of heap memory.
- Nested UNION/INTERSECT queries with brackets could produce the wrong result if used within a subquery. Example: select count(*) from (select 1 union (select 2 intersect select 2)) x;
- Comparing an column against a constant expression with a higher precision or length than the column could give wrong results (the expression was truncated before comparing).
- Improved PostgreSQL compatibility (support SHOW DEFAULT_TRANSACTION_ISOLATION).
- Documentation: the javadocs for Csv.write and read used the wrong default charset.
- MVCC: if the table was locked in exclusive mode (such as SELECT ... FOR UPDATE), another session could query the table. This is now longer possible.
- If a FOR UPDATE query was executed twice (using a PreparedStatement), the table was not locked.
- Triggers: INSTEAD OF triggers are now supported. Such triggers can be defined on views.
- New system property h2.identifiersToUpper. If set to false, identifiers in SQL statements are case sensitive even if they are not quoted.
- Slightly improved performance if the table is already locked.
- CompressLZF: faster decompression.
- PgServer: the wrong size was sent for VARCHAR data. Thanks again to Sergi Vladykin for the patch.
- Serialized access mode (server-less multi-connection mode): fixed getGeneratedKeys() for sequences.

## Version 1.2.127 (2010-01-15)

- Serialized access mode (server-less multi-connection mode): sequences did not work as expected (there were gaps in generated values when using multiple connections).
- Page store: new databases can not be opened with older versions.
- Page store: adding data to new database is now faster.
- File system: getting the file name from a path is now faster. This should speed up BLOB and CLOB access.
- PgServer: incorrect SQL types were returned in result set meta data. Concurrently opening a database could fail (PG catalog initialization was not synchronized). Thanks a lot to Sergi Vladykin for providing the patches!
- SHOW COLUMNS did not work correctly if there where multiple indexes on the same columns.
- Page store: the wrong write count was written to the database header. This could cause the server-less multi-connection mode to fail.
- Result sets larger than 2 GB threw an exception "Negative seek offset". Fixed.
- If the system property h2.check was set to false, an ArrayIndexOutOfBoundsException could occur.
- Alter table is now supported even if a table has views defined. (Patch from Kerry Sainsbury).
- Fulltext search: exceptions within the fulltext search package had the wrong SQL state.
- The Lucene fulltext search ignored transaction rollback. Fixed using a trigger on rollback.
- Trigger can now be called on rollback.
- The shell script h2.sh ignored command line line arguments.
- When running H2 in the Google AppEngine for Java, a AccessControlException could be thrown when trying to open a read-only database. Fixed.
- The user home directory prefix (~) is now only expanded when followed by a slash or backslash, or standing alone.
- Native fulltext search: before inserting or deleting data, FT_INIT() had to be called. This is no longer required.
- The .trace.db file is now only created if required.
- Shell tool: improved PostgreSQL compatibility.
- Trying to open a database in read-only mode when a .lock.db file exists will now fail with a nice error message.
- H2 Console: data that is too long is now abbreviated as follows: text... (100000 characters). A large binary is abbreviated as follows: abcdef... (100000 bytes).
- Faster data conversion from BIGINT or INT to DECIMAL.
- Server-less multi-connection mode: try to delete log files if switching between read/write operations.
- CompressLZF: Faster decompress and improved javadocs

## Version 1.2.126 (2009-12-18)

- The ChangeFileEncryption tool will now fail with an exception if the database is still in use. The Backup tool will also fail except when running in quiet mode.
- CSVREAD: when reading the column names from the CSV file, column names that contain no special characters are considered case insensitive now.
- Optimization index conditions of the form 'column=NULL' (which is always false; unlike 'column IS NULL').
- Script command and tool: the primary key constraint is now listed before inserting the data. This will result in a smaller database when using the page store.
- Statements with IN(SELECT..) conditions could produce the wrong result. Example: index on id, name; query: select * from test where id between 1 and 3 and name in (select 'World').
- Statements with IN(..) conditions could produce the wrong result when using views or nested select statements. Example: index on id; index on name; query: select * from (select * from test) where id=1 and name in('a', 'b'). select * from (select * from test) where id=1 and name in('Hello', 'World').
- Page store: a rollback of a relatively large transaction could fail with an ArrayIndexOutOfBoundsException or a 'row not found' exception in the PageBtreeIndex in some cases.
- JaQu: the decompiler has been improved, and a few test cases already work. It is still incomplete however.
- LIKE: any letter is now allowed after the escape character (which is still '\' by default). Previously, an exception was thrown (unlike other databases) if it was not the escape character, '_' or '%'. If the escape character appears at the end of the pattern, the result is it is ignored (like PostgreSQL and MS SQL Server).
- The reserve heap memory is no longer used.
- Database.checkpoint() could throw a NullPointerException.

## Version 1.2.125 (2009-12-06)

- Lucene fulltext search: the Lucene field names now match the table column names, except if the column names start with _ (in which case another _ is prepended). Unfortunately this change means existing fulltext indexes need to be re-built.
- The shell tool now has a very simple statement history.
- The zip file system implementation now supports the '~' home directory prefix. Example database URL: jdbc:h2:zip:~/test.zip!/test
- Right outer joins on tables that were already 'inner joined' was processed incorrectly.
- Temporary files from LOB objects were not deleted early enough when using the server mode.
- Trying to alter a temporary table threw a strange exception. It is still not possible to do that, but the exception message is better now.
- When the system property h2.maxMemoryRowsDistinct was set, and using SELECT DISTINCT, the temporary table was not correctly dropped. This could cause problems in recovery when the process was killed.
- Trigger that are called before a select statement are now supported. This allows to create tables that work like materialized views.
- Non-row based triggers were called even if the action didn't match the declared action (INSERT triggers were also called when deleting rows). This has been changed. The MERGE statement calls both INSERT and DELETE triggers.
- Statements with IN(..) conditions could produce the wrong result or a data conversion error (since version 1.2.120). Examples: index on id, name, condition: id=1 and name in('Hello', 'x'); index on id, query: select * from (select * from test) where id=1 and name in('Hello', 'World').
- The CompressTool was not multithreading safe. Because of this, the following database operations where also not multithreading safe (even when using different databases): the SCRIPT command (only when using compression), the COMPRESS function, and storing CLOB or BLOB data (only when compression is enabled).
- The compression algorithm "LZF" is now about 33% faster than before when compressing small block (around 2 KB). It is much faster than Deflate, but the compression ratio is lower. Some of the optimizations are from Sam Van Oort, thanks a lot!
- Compressing large blocks of data didn't work when using the "Deflate" compression algorithm. Compressing a lot of data could run out of heap memory.
- The test cases don't access the file system directly, this simplifies GAE for Java testing. Thanks to Vince Bonfanti.
- More bugs in the server-less multi-connection mode have been fixed.
- When running against an old database, the SCRIPT statement could generate a SQL script that contained duplicate indexes (PRIMARY_KEY_E).
- JdbcConnectionPool.getConnection() could throw a NullPointerException.
- User defined functions: the source code is now available using SELECT SOURCE FROM INFORMATION_SCHEMA.FUNCTION_ALIASES.
- User defined functions with source code didn't work after re-opening the database.
- The newsfeeds are now Atom 1.0 standard compliant.
- The database is now closed after an out of memory exception, because the database could get corrupt otherwise.
- Better error message if both AUTO_SERVER and SERIALIZED parameters are set to TRUE.
- Drop table did not delete lob files in old file store (not PAGE_STORE).

## Version 1.2.124 (2009-11-20)

- Clustering: there is now a way to detect which cluster instances are running.
- ConvertTraceFile: the SQL statement statistics are better formatted (newline are removed).
- The file lock thread is now stopped when the database is closed.
- Issue 140: the Script tool now supports writing to a stream.
- Issue 138: the trace output of Statement.execute(String, int) and executeUpdate was incorrect.
- Page store: new databases can not be opened with older versions.
- Page store: multi-column indexes didn't work if the cache was very small.
- Page store: opening a database could theoretically result in an endless loop.
- Page store: adding large indexed columns could get very slow.
- Page store: after a duplicate key exception, an ArrayIndexOutOfBoundsException could be thrown (only for very large rows).
- Page store: the recover tool sometimes generated a script file that contained duplicate data.
- Page store: sometimes opening a read-only database failed.
- Page store: opening a database sometimes failed if large rows where updated, or if a table was truncated before.
- Page store: when using a very small page size (128 bytes or smaller), writing a large row could result in an endless recursion. This is only a theoretical problem, as the page size is 2 KB.
- Page store: getting the min value from a descending index with NULL entries could return the wrong result.
- Page store: improved auto-recovery after power failure.
- The JDBC client did not detect that it was not talking to an H2 server. This could result in strange exceptions when trying to connect to another kind of server.
- User defined functions can be created with source code. Example: CREATE ALIAS HI AS 'String hi() { return "Hello"; }'
- Database file lock: the exception "lock file modified in the future" is no longer thrown; instead, opening the file will be delayed by 2 seconds.
- Inserting LOBs got slower each time the process was restarted. It could loop endlessly after about 1000 process restarts.
- Issue 117: Multi-version concurrency: concurrent MERGE statements now work.
- Improved read-only database detection.

## Version 1.2.123 (2009-11-08)

- Page store: new databases can not be opened with older versions.
- Page store: updating large rows (rows with more than 2000 bytes of data) could corrupt the database.
- Page store: inserting very large rows failed with ArrayIndexOutOfBoundsException.
- When using multi-threaded kernel mode, setting disabling locking (LOCK_MODE=0) will now throw an exception. At this time this combination will result in corruption when multiple threads try to update the same table.
- The fulltext search methods and fields are now protected instead of private, to make the classes more easily extensible.
- The Lucene fulltext search now also returns the score.
- New function SCOPE_IDENTITY() to avoid problems when inserting rows in a trigger.
- Statement.getGeneratedKeys() returned the wrong value if a trigger changed the identity value after inserting the row.
- Improved error messages: identifiers and values are now quoted.
- Improved error message when casting a value failed: the column name and type is included in the message.
- Improved support for GAE for Java thanks to Vince Bonfanti.

## Version 1.2.122 (2009-10-28)

- The native fulltext search now supports streaming CLOB data.
- If the database URL ends with ;PAGE_STORE=TRUE and a database in the old format exists, it is automatically converted to the new page store format if possible. A backup of the database is created first. Automatic conversion is not supported if the database was not closed normally (if it contains uncommitted transactions).
- Dropping the current user is now allowed if another admin user exists.
- Values of type BINARY or BLOB could not be converted to the data type OTHER.
- SHUTDOWN COMPACT now fully compacts the database.
- New system properties h2.maxCompactCount and h2.maxCompactTime to allow changing the default behavior (at most 2 seconds compacting when closing the database).
- New sorted insert optimization (see Performance / Database Performance Tuning).
- Issue 116: The files h2*-sources.jar and h2*-javadoc.jar are now in the Maven repository.
- Page store: opening a large database was slow if it was not closed before.
- Page store: new write and read counters in the meta data table. Use SELECT * FROM INFORMATION_SCHEMA.SETTINGS WHERE NAME IN( 'info.FILE_WRITE_TOTAL', 'info.FILE_WRITE', 'info.FILE_READ', 'info.CACHE_MAX_SIZE', 'info.CACHE_SIZE')
- The SQL syntax is documented using (railroad) diagrams. The diagrams are HTML.
- The documentation is no longer available in Japanese because the translation was too much out of sync. Please use the Google translation instead.
- Certain queries were not sorted if subselect queries were involved
- More bugs in the server-less multi-connection mode have been fixed: 90097 The database is read only, caches must be cleared on reconnect, etc.

## Version 1.2.121 (2009-10-11)

- Better support GaeVFS (Google App Engine Virtual File System) thanks to Thanks to Vince Bonfanti.
- CSVREAD didn't close the file. Thanks to Vince Bonfanti for the patch!
- If a database in the old format exists, it is now used. The system property is used for new databases, or if databases exist in both formats. In any case, the flag in the URL overrides this logic.
- Page store bugs were fixed. Large values in indexed columns could corrupt the index.
- The page store did not work when using Retrotranslator (because the Retrotranslator doesn't support Integer.reverse and Long.reverse).
- New system property h2.pageStoreTrim to disable shrinking the database when closing (disabled by default, meaning by default the database is trimmed).

## Version 1.2.120 (2009-10-04)

- This is a beta version.
- Large updates could throw an ArrayIndexOutOfBoundsException in RowList.writeRow.
- In version 1.2, the following system properties are now enabled by default: h2.pageStore, h2.nullConcatIsNull, h2.optimizeInList. The default value for h2.defaultMaxLengthInplaceLob is now 4096 (it was 1024 with version 1.1).
- New databases are now stored in the new 'page store' file format. Existing databases are kept in the old file format. To use the old file format, append ;PAGE_STORE=FALSE to the database URL or set the system property h2.pageStore to false.
- Issue 125: Renaming primary keys was not persistent. Fixed. Unfortunately, databases created by this version can not be opened with older versions because of this change.
- Issue 124: Hibernate schema validation failed for decimal/numeric columns. This problem is fixed in the Hibernate dialect that is included with H2 (src/tools/org/hibernate/dialect/H2Dialect.java.txt), but not in Hibernate yet.
- PostgreSQL compatibility: function LASTVAL() as an alias for IDENTITY().
- Linked tables now support default values when inserting, updating or merging.
- Bugfixes in the page store.
- Possibility to set a vendor id in Constants.java, so that unofficial builds are distinguishable from official releases.
- Allow writing to linked tables in readonly databases.

## Version 1.1.119 (2009-09-26)

- SQL statements in the exception message are no longer included if they contain '--hide--'.
- Temporary local tables did not always work after reconnect if AUTO_SERVER=TRUE
- New system property h2.defaultMaxLengthInplaceLob to change the default maximum size of an in-place LOB object.
- New system property h2.nullConcatIsNull to change the default null concatenation behavior. The default will be enabled in version 1.2.
- The cache algorithm TQ is disabled in this version, because it is unstable, and because the current implementation does not have any measurable advantages over the default.
- New committer: Christian Peter. He works for Docware and helped a lot finding and fixing bugs, and generally improving the database. He is now a committer.
- ChangeFileEncryption did not work with Lob subdirectories. Fixed.
- Issue 121: JaQu: new simple update and merge methods.
- Issue 120: JaQu didn't close result sets.
- Issue 119: JaQu creates wrong WHERE conditions on some inputs.
- The new page store mechanism is now alpha-level quality. The next release will most likely be "1.2.120 beta" where this mode is enabled by default. To use it right now, append ;PAGE_STORE=TRUE to the database URL. The file format of this mode will probably not change any more.
- SELECT COUNT(*) FROM SYSTEM_RANGE(...) returned the wrong result. Fixed.
- The Recover tool now also processes the log files, however applying those changes is still a manual process.
- New sample application that shows how to pass data to a trigger.
- More bugs in the server-less multi-connection mode have been fixed: On Windows, two processes could write to the same database at the same time.
- When loading triggers or other client classes (static functions, database event listener, user aggregate functions, other JDBC drivers), the database now uses the context class loader if the class could not be found using Class.forName().
- Updating many rows with the same CLOB or BLOB values could result in FileNotFoundException.
- Statement.getConnection() threw an exception if the connection was already closed.
- The native fulltext index kept a reference to a database after the database was closed.
- Non-unique in-memory hash indexes are now supported. Thanks a lot to Sergi Vladykin for the patch!
- The optimizer does a better job for joins if indexes are missing.