# Change Log

## Next Version (unreleased)

- 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 IndexOutOfBoundsException 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.
- 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.

## Version 1.1.118 (2009-09-04)

- SHOW COLUMNS only listed indexed columns.
- When calling SHUTDOWN IMMEDIATELY in the server mode, the .trace.db file was not closed.
- DatabaseMetaData.getPrimaryKeys: the wrong constraint name was reported if there was another constraint on the same table and columns.
- AUTO_INCREMENT now works in the same way in ALTER TABLE ALTER COLUMN as in CREATE TABLE (it does not create a primary key).
- Native fulltext search: before searching, FT_INIT() had to be called. This is no longer required.
- Better support GaeVFS (Google App Engine Virtual File System).
- JaQu: the plan is to support natural (pure Java / Scala) conditions such as (id == 1 && name.equals("Test")). A proof of concept decompiler is now included (it doesn't work yet).
- Various bugfixes and improvements in the page store mechanism (still experimental).
- PreparedStatement.setObject now converts a java.lang.Character to a string.
- H2 Console: PierPaolo Ucchino has completed the Italian translation. Thanks a lot!
- Various tools now use Java 5 var-args, such as main the methods and SimpleResultSet.addRow.
- H2 Console: indexes of tables of non-default schemas are now also listed.
- Issue 111: Multi-version concurrency / duplicate primary key after rollback.
- Issue 110: Multi-version concurrency / wrong exception is thrown.
- Parser: sequenceName.NEXTVAL and CURRVAL did not respect the schema search path.
- Issue 101: The following sequence could throw the exception "Row not found when trying to delete": start a transaction, insert many rows, delete many rows, rollback. The number of rows depends on the cache size.
- The stack trace of very common exceptions is no longer written to the .trace.db file by default.
- An optimization for OR is implemented, but disabled by default. Expressions of the type X=1 OR X=2 are converted to X IN(1, 2). To enable, set the system property h2.optimizeInList to true before loading the H2 JDBC driver.
- An optimization for IN(..) and IN(SELECT...) is implemented, but disabled by default. To enable, set the system property h2.optimizeInList to true before loading the H2 JDBC driver. If enabled, this overrides h2.optimizeIn and h2.optimizeInJoin. Unlike now, this optimization will also speed up updates and deletes.

## Version 1.1.117 (2009-08-09)

- New committer: Sam Van Oort has been contributing to H2 since quite some time in many ways (on the mailing list, documentation, and in the form of patches). He is now a committer.
- JaQu: the order of the fields in the database no longer needs to match the order in the database.
- Issue 103: MVCC: the setting MAX_MEMORY_UNDO can currently not be supported when using multi-version concurrency, that means the complete undo log must fit in memory.
- LIKE: the escape mechanism can now be disable using ESCAPE ''. The default escape character can be changed using the system property h2.defaultEscape. The default is still '\' (as in MySQL and PostgreSQL).
- Views using functions were not re-evaluated when necessary.
- Improved MySQL compatibility for SHOW COLUMNS.
- Improved PostgreSQL compatibility for timestamp literals with timezone.
- Sergi Vladykin translated the error messages to Russian. Thanks a lot!
- Support for Java 6 DatabaseMetaData.getTables, getColumns, getProcedures, and getProcedureColumns.
- Issue 101: Rollback of a large transaction (more than 100000 rows) could fail.
- Various bugfixes and improvements in the page store mechanism (still experimental).
- The functions LENGTH, OCTET_LENGTH, and BIT_LENGTH now return BIGINT.
- Data types CLOB and BLOB: the maximum precision was Integer.MAX_VALUE, it is now Long.MAX_VALUE.
- Multi-threaded kernel: creating and dropping temporary database objects and the potentially free pages list was not correctly synchronized. Thanks a lot to Eric Faulhaber for the test case and patch!
- Parsing SQL script files is now faster.
- CSV reading is now faster.
- SimpleResultSet.newInstance(SimpleRowSource rs) did not work.

## Version 1.1.116 (2009-07-18)

- Server-less multi-connection mode: more bugs are fixed.
- The built-in help (INFORMATION_SCHEMA.HELP) is smaller, shrinking the jar file size a bit.
- H2 Console: column of tables of non-default schemas are now also listed, except for schemas starting with 'INFO'.
- ALTER TABLE: removing an auto-increment or identity column didn't remove the sequence.
- Creating indexes is now a bit faster.
- PG Server: new system property h2.pgClientEncoding to explicitly set the encoding for clients that don't send the encoding (the default encoding is UTF-8). Thanks a lot to Sergi Vladykin for the patch!
- PG Server: improved compatibility by using the type ids of the PostgreSQL driver. Thanks a lot to Sergi Vladykin for the patch!
- H2 Console: Oracle system tables are no longer listed, improving performance.
- Result sets are now read-only except if the statement or prepared statement was created with the concurrency ResultSet.CONCUR_UPDATABLE. This change is required because the old behavior (all result set are updatable) violated the JDBC spec. For backward compatibility, use the system property h2.defaultResultSetConcurrency.
- New system property h2.defaultResultSetConcurrency to change the default result set concurrency.
- JDBC: using an invalid result set type or concurrency now throws an exception.
- If a pooled connection was not closed but garbage collected, a NullPointerException could occur.
- Fulltext search: a NullPointerException was thrown when updating a value that was NULL previously.
- The Recover tool did not work with .data.db files of the wrong size.
- Triggers: if there was an exception when initializing a trigger, this exception could be hidden, and in some cases (specially when using the Lucene fulltext index mechanism) a NullPointerException was thrown later on. Now the exception that occurred on init is thrown when changing data.
- The soft-references cache (CACHE_TYPE=SOFT_LRU) could throw a NullPointerException.
- To enable the new page store mechanism, append ;PAGE_STORE=TRUE to the database URL. or set the system property h2.pageStore to true. This mechanism is still experimental, and the file format will change, but it is quite stable now.

## Version 1.1.115 (2009-06-21)

- The new storage mechanism is now alpha quality. To try it out, set the system property "h2.pageStore" to "true" (java -Dh2.pageStore=true). There are still bugs to be found and fixed, for example inserting many rows references a lot of main memory. Performance is currently about the same as with the regular storage mechanism, but the database file size is smaller. The file format is not stable yet.
- ALTER TABLE could throw an exception "object already exists" in some cases.
- Views: in some situations, an ArrayIndexOutOfBoundsException was thrown when using the same view concurrently.
- java.util.UUID is now supported in PreparedStatement.setObject and user defined Java functions. ResultSet.getObject() returns a java.util.UUID when using the UUID data type.
- H2 Console: the language was reset to the browser language when disconnecting.
- H2 Console: improved Polish translation.
- Server-less multi-connection mode: more bugs are fixed.
- The download page now included the SHA1 checksums.
- Shell tool: the file encoding workaround is now documented if you run java org.h2.tools.Shell -?.
- The RunScript tool and SQL statement did not work with the compression method LZF.
- Fulltext search: searching for NULL or an empty string threw an exception.
- Lucene fulltext search: FTL_DROP_ALL did not drop the triggers.
- Backup: if the database contained CLOB or BLOB data, the backup included a file entry for the LOB directory. This caused the restore to fail.
- Data types: LONG is now an alias for BIGINT.

## Version 1.1.114 (2009-06-01)

- ResultSetMetaData.getColumnClassName returned the wrong class for CLOB and BLOB columns.
- Fulltext search: data is no longer deleted and re-inserted if the indexed columns didn't change.
- In some situations, an ArrayIndexOutOfBoundsException was thrown when adding rows. This was caused by a bug in the b-tree code.
- Microsoft Windows Vista: when using the the installer, Vista wrote "This program may not have installed correctly." This message should no longer appear (in the h2.nsi file, the line 'RequestExecutionLevel highest' was added).
- The Recover tool did not always work when the database contains referential integrity constraints.
- Java 1.5 is now required to run H2. If required, Retrotranslator can be used to create a Java 1.4 version (http://retrotranslator.sourceforge.net/).

## Version 1.1.113 (2009-05-21)

- Shell tool: the built-in commands EXIT, HELP, ?, LIST, and so on didn't work with a semicolon at the end.
- JDK 1.5 is now required to build the jar file. However it is still possible to create a jar file for Java 1.4. For details, see buildRelease.sh and buildRelease.bat. As an alternative, compile using JDK 1.5 or 1.6 and use Retrotranslator to create a Java 1.4 version (http://retrotranslator.sourceforge.net/).
- When deleting or updating many rows in a table, the space in the index file was not re-used in the default mode (persistent database, b-tree index, LOG=1). This caused the index file to grow over time. Workarounds were to delete and re-created the index file, alter the table (add a remove a column), or append ;LOG=2 to the database URL. To disable the change, set the system property h2.reuseSpaceBtreeIndex to false.
- Identifiers with a digit and then a dollar sign didn't work. Example: A1$B.
- MS SQL Server compatibility: support for linked tables with NVARCHAR, NCHAR, NCLOB, and LONGNVARCHAR.
- Android: workaround for a problem when using read-only databases in zip files (skip seems to be implemented incorrectly on the Android system).
- Calling execute() or prepareStatement() with null as the SQL statement now throws an exception.
- Benchmark: the number of executed statements was incorrect. The H2 database was loaded at the beginning of the test to collect results, now it is loaded at the very end. Thanks to Fred Toussi from HSQLDB for reporting those problems. However the changed do not affect the relative performance.
- H2 Console: command line settings are no longer stored in the properties file. They are now only used for the current process, except if they are explicitly saved.
- Cache: support for a second level soft-references cache. To enable it, append ;CACHE_TYPE=SOFT_LRU (or SOFT_TQ) to the database URL, or set the system property h2.cacheTypeDefault to "SOFT_LRU" / "SOFT_TQ". Enabling the second level cache reduces performance for small databases, but speeds up large databases. It makes sense to use it if the available memory size is unknown. Thanks a lot to Jan Kotek!

## Version 1.1.112 (2009-05-01)

- JdbcPreparedStatement.toString() could throw a NullPointerException.
- EclipseLink: added H2Platform.supportsIdentity().
- Connection pool: the default login timeout is now 5 minutes.
- After truncating tables, opening large databases could become slow because indexes were always re-built unnecessarily when opening.
- More bugs in the server-less multi-connection mode have been fixed: Sometimes parameters of prepared statements were lost when a reconnecting. Concurrent read operations were slow. To improve performance, executeQuery(..) must be used for queries (execute(..) switches to the write mode, which is slow).
- GROUP BY queries with a self-join (join to the same table) that were grouped by columns with indexes returned the wrong result in some cases.
- Improved error message when the .lock.db file modification time is in the future.
- The MERGE statement now returns 0 as the generated key if the row was updated.
- Running code coverage is now automated.
- A file system implementation can now be registered using FileSystem.register.
- The database file system is no longer included in the jar file, it moved to the test section.

## Version 1.1.111 (2009-04-10)

- In-memory databases can now run inside the Google App Engine.
- Queries that are ordered by an indexed column returned no rows in certain cases (if all rows were deleted from the table previously, and there is a low number of rows in the table, and when not using other conditions, and when using the default b tree index).
- The wrong exception was thrown when using unquoted text for the SQL statements COMMENT, ALTER USER, and SET PASSWORD.
- The built-in connection pool did not roll back transactions and enable autocommit enabled after closing a connection.
- Sometimes a StackOverflow occurred when checking for deadlock. See also http://code.google.com/p/h2database/issues/detail?id=61
- The Shell tool no longer truncates results with only one column, and displays a message if data was truncated.