H2 Console system tray icon: support for Mac OS X retina displays.
The default jar file is now compiled for Java 6.
@changelog_1003_li
@changelog_1003_li
The CreateCluster tool could not be used if the source database contained a CLOB or BLOB. The root cause was that the TCP server did not synchronize on the session, which caused a problem when using the exclusive mode.
The new jar file will probably not end up in the central Maven repository in the next few weeks because Sonatype has disabled automatic synchronization from SourceForge (which they call 'legacy sync' now). It will probably take some time until this is sorted out. The H2 jar files are deployed to http://h2database.com/m2-repo/com/h2database/h2/maven-metadata.xml and http://hsql.sourceforge.net/m2-repo/com/h2database/h2/maven-metadata.xml as usual.
@changelog_1004_li
@changelog_1004_li
Statement.getQueryTimeout(): only the first call to this method will query the database. If the query timeout was changed in another way than calling setQueryTimeout, this method will always return the last value. This was changed because Hibernate calls getQueryTimeout() a lot.
A part of the documentation and the H2 Console has been changed to support the Apple retina display.
@changelog_1005_li
@changelog_1005_li
Issue 416: PreparedStatement.setNString throws AbstractMethodError. All implemented JDBC 4 methods that don't break compatibility with Java 5 are now included in the default jar file.
The CreateCluster tool could not be used if the source database contained a CLOB or BLOB. The root cause was that the TCP server did not synchronize on the session, which caused a problem when using the exclusive mode.
@changelog_1006_li
@changelog_1006_li
Issue 414: for some functions, the parameters were evaluated twice (for example "char(nextval(..))" ran "nextval(..)" twice).
Statement.getQueryTimeout(): only the first call to this method will query the database. If the query timeout was changed in another way than calling setQueryTimeout, this method will always return the last value. This was changed because Hibernate calls getQueryTimeout() a lot.
@changelog_1007_li
@changelog_1007_li
The ResultSetMetaData methods getSchemaName and getTableName could return null instead of "" (an empty string) as specified in the JDBC API.
Issue 416: PreparedStatement.setNString throws AbstractMethodError. All implemented JDBC 4 methods that don't break compatibility with Java 5 are now included in the default jar file.
@changelog_1008_li
@changelog_1008_li
Issue 414: for some functions, the parameters were evaluated twice (for example "char(nextval(..))" ran "nextval(..)" twice).
@changelog_1009_li
The ResultSetMetaData methods getSchemaName and getTableName could return null instead of "" (an empty string) as specified in the JDBC API.
@changelog_1010_li
Added compatibility for "SET NAMES" query in MySQL compatibility mode.
Added compatibility for "SET NAMES" query in MySQL compatibility mode.
@changelog_1009_h2
@changelog_1011_h2
Version 1.3.168 (2012-07-13)
Version 1.3.168 (2012-07-13)
@changelog_1010_li
@changelog_1012_li
The message "Transaction log could not be truncated" was sometimes written to the .trace.db file even if there was no problem truncating the transaction log.
The message "Transaction log could not be truncated" was sometimes written to the .trace.db file even if there was no problem truncating the transaction log.
@changelog_1011_li
@changelog_1013_li
New system property "h2.serializeJavaObject" (default: true) that allows to disable serializing Java objects, so that the objects compareTo and toString methods can be used.
New system property "h2.serializeJavaObject" (default: true) that allows to disable serializing Java objects, so that the objects compareTo and toString methods can be used.
@changelog_1012_li
@changelog_1014_li
Dylan has translated the H2 Console tool to Korean. Thanks a lot!
Dylan has translated the H2 Console tool to Korean. Thanks a lot!
@changelog_1013_li
@changelog_1015_li
Executing the statement CREATE INDEX IF ALREADY EXISTS if the index already exists no longer fails for a read only database.
Executing the statement CREATE INDEX IF ALREADY EXISTS if the index already exists no longer fails for a read only database.
@changelog_1014_li
@changelog_1016_li
MVCC: concurrently updating a row could result in the row to appear deleted in the second connection, if there are multiple unique indexes (or a primary key and at least one unique index). Thanks a lot to Teruo for the patch!
MVCC: concurrently updating a row could result in the row to appear deleted in the second connection, if there are multiple unique indexes (or a primary key and at least one unique index). Thanks a lot to Teruo for the patch!
@changelog_1015_li
@changelog_1017_li
Fulltext search: in-memory Lucene indexes are now supported.
Fulltext search: in-memory Lucene indexes are now supported.
@changelog_1016_li
@changelog_1018_li
Fulltext search: UUID primary keys are now supported.
Fulltext search: UUID primary keys are now supported.
@changelog_1017_li
@changelog_1019_li
Apache Tomcat 7.x will now longer log a warning when unloading the web application, if using a connection pool.
Apache Tomcat 7.x will now longer log a warning when unloading the web application, if using a connection pool.
@changelog_1018_li
@changelog_1020_li
H2 Console: support the Midori browser (for Debian / Raspberry Pi)
H2 Console: support the Midori browser (for Debian / Raspberry Pi)
@changelog_1019_li
@changelog_1021_li
When opening a remote session, don't open a temporary file if the trace level is set to zero
When opening a remote session, don't open a temporary file if the trace level is set to zero
@changelog_1020_li
@changelog_1022_li
Use HMAC for authenticating remote LOB id's, removing the need for maintaining a cache, and removing the limit on the number of LOBs per result set.
Use HMAC for authenticating remote LOB id's, removing the need for maintaining a cache, and removing the limit on the number of LOBs per result set.
@changelog_1021_li
@changelog_1023_li
H2 Console: HTML and XML documents can now be edited in an updatable result set. There is (limited) support for editing multi-line documents.
H2 Console: HTML and XML documents can now be edited in an updatable result set. There is (limited) support for editing multi-line documents.
@changelog_1022_h2
@changelog_1024_h2
Version 1.3.167 (2012-05-23)
Version 1.3.167 (2012-05-23)
@changelog_1023_li
@changelog_1025_li
H2 Console: when editing a row, an empty varchar column was replaced with a single space.
H2 Console: when editing a row, an empty varchar column was replaced with a single space.
@changelog_1024_li
@changelog_1026_li
Lukas Eder has updated the jOOQ documentation.
Lukas Eder has updated the jOOQ documentation.
@changelog_1025_li
@changelog_1027_li
Some nested joins could not be executed, for example: select * from (select * from (select * from a) a right join b b) c;
Some nested joins could not be executed, for example: select * from (select * from (select * from a) a right join b b) c;
@changelog_1026_li
@changelog_1028_li
MS SQL Server compatibility: ISNULL is now an alias for IFNULL.
MS SQL Server compatibility: ISNULL is now an alias for IFNULL.
@changelog_1027_li
@changelog_1029_li
Terrence Huang has completed the translation of the H2 Console tool to Chinese. Thanks a lot!
Terrence Huang has completed the translation of the H2 Console tool to Chinese. Thanks a lot!
@changelog_1028_li
@changelog_1030_li
Server mode: the number of CLOB / BLOB values that were cached on the server is now the maximum of: 5 times the SERVER_RESULT_SET_FETCH_SIZE (which is 100 by default), and SysProperties.SERVER_CACHED_OBJECTS.
Server mode: the number of CLOB / BLOB values that were cached on the server is now the maximum of: 5 times the SERVER_RESULT_SET_FETCH_SIZE (which is 100 by default), and SysProperties.SERVER_CACHED_OBJECTS.
@changelog_1029_li
@changelog_1031_li
In the trace file, the query execution time was incorrect in some cases, specially for the statement SET TRACE_LEVEL_FILE 2.
In the trace file, the query execution time was incorrect in some cases, specially for the statement SET TRACE_LEVEL_FILE 2.
@changelog_1030_li
@changelog_1032_li
The feature LOG_SIZE_LIMIT that was introduced in version 1.3.165 did not always work correctly (specially with regards to multithreading) and has been removed. The message "Transaction log could not be truncated" is still written to the .trace.db file if required.
The feature LOG_SIZE_LIMIT that was introduced in version 1.3.165 did not always work correctly (specially with regards to multithreading) and has been removed. The message "Transaction log could not be truncated" is still written to the .trace.db file if required.
@changelog_1031_li
@changelog_1033_li
Then reading from a resource using the prefix "classpath:", the ContextClassLoader is now used if the resource can't be read otherwise.
Then reading from a resource using the prefix "classpath:", the ContextClassLoader is now used if the resource can't be read otherwise.
@changelog_1032_li
@changelog_1034_li
DatabaseEventListener now calls setProgress whenever a statement starts and ends.
DatabaseEventListener now calls setProgress whenever a statement starts and ends.
@changelog_1033_li
@changelog_1035_li
DatabaseEventListener now calls setProgress periodically while a statement is running.
DatabaseEventListener now calls setProgress periodically while a statement is running.
@changelog_1034_li
@changelog_1036_li
The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME.
The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME.
@changelog_1035_li
@changelog_1037_li
Issue 378: when using views, the wrong values were bound to a parameter in some cases.
Issue 378: when using views, the wrong values were bound to a parameter in some cases.
@changelog_1036_li
@changelog_1038_li
Terrence Huang has translated the error messages to Chinese. Thanks a lot!
Terrence Huang has translated the error messages to Chinese. Thanks a lot!
@changelog_1037_li
@changelog_1039_li
TRUNC was added as an alias for TRUNCATE.
TRUNC was added as an alias for TRUNCATE.
@changelog_1038_li
@changelog_1040_li
Small optimisation for accessing result values by column name.
Small optimisation for accessing result values by column name.
@changelog_1039_li
@changelog_1041_li
Fix for bug in Statement.getMoreResults(int)
Fix for bug in Statement.getMoreResults(int)
@changelog_1040_li
@changelog_1042_li
The SCRIPT statements now supports filtering by schema and table. Thanks a lot to Jacob Qvortrup for providing the patch!
The SCRIPT statements now supports filtering by schema and table. Thanks a lot to Jacob Qvortrup for providing the patch!
@changelog_1041_h2
@changelog_1043_h2
Version 1.3.166 (2012-04-08)
Version 1.3.166 (2012-04-08)
@changelog_1042_li
@changelog_1044_li
Indexes on column that are larger than half the page size (wide indexes) could sometimes get corrupt, resulting in an ArrayIndexOutOfBoundsException in PageBtree.getRow or "Row not found" in PageBtreeLeaf. Also, such indexes used too much disk space.
Indexes on column that are larger than half the page size (wide indexes) could sometimes get corrupt, resulting in an ArrayIndexOutOfBoundsException in PageBtree.getRow or "Row not found" in PageBtreeLeaf. Also, such indexes used too much disk space.
@changelog_1043_li
@changelog_1045_li
Server mode: when retrieving more than 64 rows each containing a CLOB or BLOB, the error message "The object is already closed" was thrown.
Server mode: when retrieving more than 64 rows each containing a CLOB or BLOB, the error message "The object is already closed" was thrown.
@changelog_1044_li
@changelog_1046_li
ConvertTraceFile: the time in the trace file is now parsed as a long.
ConvertTraceFile: the time in the trace file is now parsed as a long.
@changelog_1045_li
@changelog_1047_li
Invalid connection settings are now detected.
Invalid connection settings are now detected.
@changelog_1046_li
@changelog_1048_li
Issue 387: WHERE condition getting pushed into sub-query with LIMIT.
Issue 387: WHERE condition getting pushed into sub-query with LIMIT.
@changelog_1047_h2
@changelog_1049_h2
Version 1.3.165 (2012-03-18)
Version 1.3.165 (2012-03-18)
@changelog_1048_li
@changelog_1050_li
Better string representation for decimal values (for example 0.00000000 instead of 0E-26).
Better string representation for decimal values (for example 0.00000000 instead of 0E-26).
@changelog_1049_li
@changelog_1051_li
Prepared statements could only be re-used if the same data types were used the second time they were executed.
Prepared statements could only be re-used if the same data types were used the second time they were executed.
@changelog_1050_li
@changelog_1052_li
In error messages about referential constraint violation, the values are now included.
In error messages about referential constraint violation, the values are now included.
@changelog_1051_li
@changelog_1053_li
SCRIPT and RUNSCRIPT: the password can now be set using a prepared statement. Previously, it was required to be a literal in the SQL statement.
SCRIPT and RUNSCRIPT: the password can now be set using a prepared statement. Previously, it was required to be a literal in the SQL statement.
@changelog_1052_li
@changelog_1054_li
MySQL compatibility: SUBSTR with a negative start index now works like MySQL.
MySQL compatibility: SUBSTR with a negative start index now works like MySQL.
@changelog_1053_li
@changelog_1055_li
When enabling autocommit, the transaction is now committed (as required by the JDBC API).
When enabling autocommit, the transaction is now committed (as required by the JDBC API).
@changelog_1054_li
@changelog_1056_li
The shell script <code>h2.sh</code> did not work with spaces in the path. It also works now with quoted spaces in the argument list. Thanks a lot to Shimizu Fumiyuki for the patch!
The shell script <code>h2.sh</code> did not work with spaces in the path. It also works now with quoted spaces in the argument list. Thanks a lot to Shimizu Fumiyuki for the patch!
@changelog_1055_li
@changelog_1057_li
If the transaction log could not be truncated because of an uncommitted transaction, now "Transaction log could not be truncated" is written to the .trace.db file. Before, the database file was growing and it was hard to find out what the root cause was. To avoid the database file from growing, a new feature to automatically rollback the oldest transaction is available now. To enable it, append ;LOG_SIZE_LIMIT=32 to the database URL (in that case, the oldest session is rolled back if the transaction log is 32 MB).
If the transaction log could not be truncated because of an uncommitted transaction, now "Transaction log could not be truncated" is written to the .trace.db file. Before, the database file was growing and it was hard to find out what the root cause was. To avoid the database file from growing, a new feature to automatically rollback the oldest transaction is available now. To enable it, append ;LOG_SIZE_LIMIT=32 to the database URL (in that case, the oldest session is rolled back if the transaction log is 32 MB).
@changelog_1056_li
@changelog_1058_li
ALTER TABLE ADD can now add more than one column at a time.
ALTER TABLE ADD can now add more than one column at a time.
@changelog_1057_li
@changelog_1059_li
Issue 380: ALTER TABLE ADD FOREIGN KEY with an explicit index didn't verify the index can be used, which would lead to a NullPointerException later on.
Issue 380: ALTER TABLE ADD FOREIGN KEY with an explicit index didn't verify the index can be used, which would lead to a NullPointerException later on.
@changelog_1058_li
@changelog_1060_li
Issue 384: the wrong kind of exception (NullPointerException) was thrown in a UNION query with an incorrect ORDER BY expression.
Issue 384: the wrong kind of exception (NullPointerException) was thrown in a UNION query with an incorrect ORDER BY expression.
@changelog_1059_li
@changelog_1061_li
Issue 362: support LIMIT in UPDATE statements.
Issue 362: support LIMIT in UPDATE statements.
@changelog_1060_li
@changelog_1062_li
Browser: if no default browser is set, Google Chrome is now used if available. If not available, then Konqueror, Netscape, or Opera is used if available (as before).
Browser: if no default browser is set, Google Chrome is now used if available. If not available, then Konqueror, Netscape, or Opera is used if available (as before).
@changelog_1061_li
@changelog_1063_li
CSV tool: new feature to disable writing the column header (option writeColumnHeader).
CSV tool: new feature to disable writing the column header (option writeColumnHeader).
@changelog_1062_li
@changelog_1064_li
CSV tool: new feature to preserve the case sensitivity of column names (option caseSensitiveColumnNames).
CSV tool: new feature to preserve the case sensitivity of column names (option caseSensitiveColumnNames).
@changelog_1063_li
@changelog_1065_li
PostgreSQL compatibility: LOG(x) is base 10 in the PostgreSQL mode.
PostgreSQL compatibility: LOG(x) is base 10 in the PostgreSQL mode.
@changelog_1064_h2
@changelog_1066_h2
Version 1.3.164 (2012-02-03)
Version 1.3.164 (2012-02-03)
@changelog_1065_li
@changelog_1067_li
New built-in function ARRAY_CONTAINS.
New built-in function ARRAY_CONTAINS.
@changelog_1066_li
@changelog_1068_li
Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
@changelog_1067_li
@changelog_1069_li
Trying to convert a VARCHAR to UUID will now fail if the text contains a character that is not a hex digit, '-', or not a whitespace.
Trying to convert a VARCHAR to UUID will now fail if the text contains a character that is not a hex digit, '-', or not a whitespace.
@changelog_1068_li
@changelog_1070_li
TriggerAdapter: in "before" triggers, values can be changed using the ResultSet.updateX methods.
TriggerAdapter: in "before" triggers, values can be changed using the ResultSet.updateX methods.
@changelog_1069_li
@changelog_1071_li
Creating a table with column data type NULL now works (even if not very useful).
Creating a table with column data type NULL now works (even if not very useful).
@changelog_1070_li
@changelog_1072_li
ALTER TABLE ALTER COLUMN no longer copies the data for widening conversions (for example if only the precision was increased) unless necessary.
ALTER TABLE ALTER COLUMN no longer copies the data for widening conversions (for example if only the precision was increased) unless necessary.
@changelog_1071_li
@changelog_1073_li
Multi-threaded kernel: concurrently running an online backup and updating the database resulted in a broken (transactionally incorrect) backup file in some cases.
Multi-threaded kernel: concurrently running an online backup and updating the database resulted in a broken (transactionally incorrect) backup file in some cases.
@changelog_1072_li
@changelog_1074_li
The script created by SCRIPT DROP did not always work if multiple views existed that depend on each other.
The script created by SCRIPT DROP did not always work if multiple views existed that depend on each other.
@changelog_1073_li
@changelog_1075_li
MathUtils.getSecureRandom could log a warning to System.err in case the /dev/random is very slow, and the System.getProperties().toString() returned a string larger than 64 KB.
MathUtils.getSecureRandom could log a warning to System.err in case the /dev/random is very slow, and the System.getProperties().toString() returned a string larger than 64 KB.
@changelog_1074_li
@changelog_1076_li
The database file locking mechanism "FS" (;FILE_LOCK=FS) did not work on Linux since version 1.3.161.
The database file locking mechanism "FS" (;FILE_LOCK=FS) did not work on Linux since version 1.3.161.
@changelog_1075_li
@changelog_1077_li
Sequences: the functions NEXTVAL and CURRVAL did not work as expected when using quoted, mixed case sequence names.
Sequences: the functions NEXTVAL and CURRVAL did not work as expected when using quoted, mixed case sequence names.
@changelog_1076_li
@changelog_1078_li
The constructor for Csv objects is now public, and Csv.getInstance() is now deprecated.
The constructor for Csv objects is now public, and Csv.getInstance() is now deprecated.
@changelog_1077_li
@changelog_1079_li
SimpleResultSet: updating a result set is now supported.
SimpleResultSet: updating a result set is now supported.
@changelog_1078_li
@changelog_1080_li
Database URL: extra semicolons are not supported.
Database URL: extra semicolons are not supported.
@changelog_1079_h2
@changelog_1081_h2
Version 1.3.163 (2011-12-30)
Version 1.3.163 (2011-12-30)
@changelog_1080_li
@changelog_1082_li
On out of disk space, the database could get corrupt sometimes, if later write operations succeeded. The same problem happened on other kinds of I/O exceptions (where one or some of the writes fail, but subsequent writes succeed). Now the file is closed on the first unsuccessful write operation, so that later requests fail consistently.
On out of disk space, the database could get corrupt sometimes, if later write operations succeeded. The same problem happened on other kinds of I/O exceptions (where one or some of the writes fail, but subsequent writes succeed). Now the file is closed on the first unsuccessful write operation, so that later requests fail consistently.
@changelog_1081_li
@changelog_1083_li
DatabaseEventListener.diskSpaceIsLow() is no longer supported because it can't be guaranteed that it always works correctly.
DatabaseEventListener.diskSpaceIsLow() is no longer supported because it can't be guaranteed that it always works correctly.
@changelog_1082_li
@changelog_1084_li
XMLTEXT now supports an optional parameter to escape newlines.
XMLTEXT now supports an optional parameter to escape newlines.
@changelog_1083_li
@changelog_1085_li
XMLNODE now support an optional parameter to disable indentation.
XMLNODE now support an optional parameter to disable indentation.
@changelog_1084_li
@changelog_1086_li
Csv.write now formats date, time, and timestamp values using java.sql.Date / Time / Timestamp.toString(). Previously, ResultSet.getString() was used, which didn't work well for Oracle.
Csv.write now formats date, time, and timestamp values using java.sql.Date / Time / Timestamp.toString(). Previously, ResultSet.getString() was used, which didn't work well for Oracle.
@changelog_1085_li
@changelog_1087_li
The shell script <code>h2.sh</code> can now be run from within a different directory. Thanks a lot to Daniel Serodio for the patch!
The shell script <code>h2.sh</code> can now be run from within a different directory. Thanks a lot to Daniel Serodio for the patch!
@changelog_1086_li
@changelog_1088_li
The page size of a persistent database can now be queries using: select * from information_schema.settings where name = 'info.PAGE_SIZE'
The page size of a persistent database can now be queries using: select * from information_schema.settings where name = 'info.PAGE_SIZE'
@changelog_1087_li
@changelog_1089_li
In the server mode, BLOB and CLOB objects are no longer closed when the result set is closed (as required by the JDBC spec).
In the server mode, BLOB and CLOB objects are no longer closed when the result set is closed (as required by the JDBC spec).
@changelog_1088_h2
@changelog_1090_h2
Version 1.3.162 (2011-11-26)
Version 1.3.162 (2011-11-26)
@changelog_1089_li
@changelog_1091_li
The following system properties are no longer supported: <code>h2.allowBigDecimalExtensions</code>, <code>h2.emptyPassword</code>, <code>h2.minColumnNameMap</code>, <code>h2.returnLobObjects</code>, <code>h2.webMaxValueLength</code>.
The following system properties are no longer supported: <code>h2.allowBigDecimalExtensions</code>, <code>h2.emptyPassword</code>, <code>h2.minColumnNameMap</code>, <code>h2.returnLobObjects</code>, <code>h2.webMaxValueLength</code>.
@changelog_1090_li
@changelog_1092_li
When using a VPN, starting a H2 server did not work (for some VPN software).
When using a VPN, starting a H2 server did not work (for some VPN software).
@changelog_1091_li
@changelog_1093_li
Oracle compatibility: support for DECODE(...).
Oracle compatibility: support for DECODE(...).
@changelog_1092_li
@changelog_1094_li
Lucene fulltext search: creating an index is now faster if the table already contains data. Thanks a lot to Angel Leon from the FrostWire Team for the patch!
Lucene fulltext search: creating an index is now faster if the table already contains data. Thanks a lot to Angel Leon from the FrostWire Team for the patch!
@changelog_1093_li
@changelog_1095_li
Update statements with a column list in brackets did not work if the list only contains one column. Example: update test set (id)=(id).
Update statements with a column list in brackets did not work if the list only contains one column. Example: update test set (id)=(id).
@changelog_1094_li
@changelog_1096_li
Read-only databases in a zip file did not work when using the -baseDir option.
Read-only databases in a zip file did not work when using the -baseDir option.
@changelog_1095_li
@changelog_1097_li
Issue 334: SimpleResultSet.getString now also works for Clob columns.
Issue 334: SimpleResultSet.getString now also works for Clob columns.
@changelog_1096_li
@changelog_1098_li
Subqueries with an aggregate did not always work. Example: select (select count(*) from test where a = t.a and b = 0) from test t group by a
Subqueries with an aggregate did not always work. Example: select (select count(*) from test where a = t.a and b = 0) from test t group by a
@changelog_1097_li
@changelog_1099_li
Server: in some (theoretical) cases, exceptions while closing the connection were ignored.
Server: in some (theoretical) cases, exceptions while closing the connection were ignored.
@changelog_1098_li
@changelog_1100_li
Server.createTcpServer, createPgServer, createWebServer: invalid arguments are now detected.
Server.createTcpServer, createPgServer, createWebServer: invalid arguments are now detected.
@changelog_1099_li
@changelog_1101_li
The selectivity of LOB columns is no longer calculated because indexes on LOB columns are not supported (however this should have little effect on performance, as the selectivity is calculated from the hash code and not the data).
The selectivity of LOB columns is no longer calculated because indexes on LOB columns are not supported (however this should have little effect on performance, as the selectivity is calculated from the hash code and not the data).
@changelog_1100_li
@changelog_1102_li
New experimental system property "h2.modifyOnWrite": when enabled, the database file is only modified when writing to the database. When enabled, the serialized file lock is much faster for read-only operations.
New experimental system property "h2.modifyOnWrite": when enabled, the database file is only modified when writing to the database. When enabled, the serialized file lock is much faster for read-only operations.
@changelog_1101_li
@changelog_1103_li
A NullPointerException could occur in TableView.isDeterministic for invalid views.
A NullPointerException could occur in TableView.isDeterministic for invalid views.
@changelog_1102_li
@changelog_1104_li
Issue 180: when deserializing objects, the context class loader is used instead of the default class loader if the system property "h2.useThreadContextClassLoader" is set. Thanks a lot to Noah Fontes for the patch!
Issue 180: when deserializing objects, the context class loader is used instead of the default class loader if the system property "h2.useThreadContextClassLoader" is set. Thanks a lot to Noah Fontes for the patch!
@changelog_1103_li
@changelog_1105_li
When using the exclusive mode, LOB operations could cause the thread to block. This also affected the CreateCluster tool (when using BLOB or CLOB data).
When using the exclusive mode, LOB operations could cause the thread to block. This also affected the CreateCluster tool (when using BLOB or CLOB data).
@changelog_1104_li
@changelog_1106_li
The optimization for "group by" was not working correctly if the group by column was aliased in the select list.
The optimization for "group by" was not working correctly if the group by column was aliased in the select list.
@changelog_1105_li
@changelog_1107_li
Issue 326: improved support for case sensitive (mixed case) identifiers without quotes when using DATABASE_TO_UPPER=FALSE.
Issue 326: improved support for case sensitive (mixed case) identifiers without quotes when using DATABASE_TO_UPPER=FALSE.
@changelog_1106_h2
@changelog_1108_h2
Version 1.3.161 (2011-10-28)
Version 1.3.161 (2011-10-28)
@changelog_1107_li
@changelog_1109_li
Issue 351: MySQL mode: can not create a table with the column "KEY", and can not open databases where such a table already exists.
Issue 351: MySQL mode: can not create a table with the column "KEY", and can not open databases where such a table already exists.
@changelog_1108_li
@changelog_1110_li
TCP server: when using the trace option ("-trace"), the trace output contained unnecessary stack traces when stopping the server.
TCP server: when using the trace option ("-trace"), the trace output contained unnecessary stack traces when stopping the server.
@changelog_1109_li
@changelog_1111_li
Issue 354: when using the multi-threaded kernel option, and multiple threads concurrently prepared SQL statements that use the same view or the same index of a view, then in some cases an infinite loop could occur.
Issue 354: when using the multi-threaded kernel option, and multiple threads concurrently prepared SQL statements that use the same view or the same index of a view, then in some cases an infinite loop could occur.
@changelog_1110_li
@changelog_1112_li
Issue 350: when using instead of triggers, executeUpdate for delete operations always returned 0.
Issue 350: when using instead of triggers, executeUpdate for delete operations always returned 0.
@changelog_1111_li
@changelog_1113_li
Some timestamps with timezone were not converted correctly. For example, in the PST timezone, the timestamp 2011-10-26 08:00:00Z was converted to 2011-10-25 25:00:00 instead of 2011-10-26 01:00:00. Depending on the database operation, this caused subsequent error.
Some timestamps with timezone were not converted correctly. For example, in the PST timezone, the timestamp 2011-10-26 08:00:00Z was converted to 2011-10-25 25:00:00 instead of 2011-10-26 01:00:00. Depending on the database operation, this caused subsequent error.
@changelog_1112_li
@changelog_1114_li
Sequences with cache size smaller than 0 did not work correctly.
Sequences with cache size smaller than 0 did not work correctly.
@changelog_1113_li
@changelog_1115_li
Issue 356: for Blob objects, InputStream.skip() returned 0, causing EOFException in Blob.getBytes(.., ..).
Issue 356: for Blob objects, InputStream.skip() returned 0, causing EOFException in Blob.getBytes(.., ..).
@changelog_1114_li
@changelog_1116_li
Updatable result sets: if the value is not set when inserting a new row, the default value is now used (the same behavior as MySQL, PostgreSQL, and Apache Derby) instead of NULL.
Updatable result sets: if the value is not set when inserting a new row, the default value is now used (the same behavior as MySQL, PostgreSQL, and Apache Derby) instead of NULL.
@changelog_1115_li
@changelog_1117_li
Conditions of the form IN(SELECT ...) where slow and increased the database size if the subquery result size was larger then the configured MAX_MEMORY_ROWS.
Conditions of the form IN(SELECT ...) where slow and increased the database size if the subquery result size was larger then the configured MAX_MEMORY_ROWS.
@changelog_1116_li
@changelog_1118_li
Issue 347: the RunScript and Shell tools now ignore empty statements.
Issue 347: the RunScript and Shell tools now ignore empty statements.
@changelog_1117_li
@changelog_1119_li
Issue 246: improved error message for data conversion problems.
Issue 246: improved error message for data conversion problems.
@changelog_1118_li
@changelog_1120_li
Issue 344: the build now supports a custom Maven repository location.
Issue 344: the build now supports a custom Maven repository location.
@changelog_1119_li
@changelog_1121_li
Issue 334: Java functions that return CLOB or BLOB objects could not be used as tables.
Issue 334: Java functions that return CLOB or BLOB objects could not be used as tables.
@changelog_1120_li
@changelog_1122_li
SimpleResultSet now supports getColumnTypeName and getColumnClassName.
SimpleResultSet now supports getColumnTypeName and getColumnClassName.
@changelog_1121_li
@changelog_1123_li
SimpleResultSet now has minimal BLOB and CLOB support.
SimpleResultSet now has minimal BLOB and CLOB support.
@changelog_1122_li
@changelog_1124_li
Improved performance for large databases (many GB), and databases with a small page size.
Improved performance for large databases (many GB), and databases with a small page size.
@changelog_1123_li
@changelog_1125_li
The Polish translation has been improved by Jarosław Kokociński.
The Polish translation has been improved by Jarosław Kokociński.
@changelog_1124_li
@changelog_1126_li
When using the built-in connection pool, after calling the "shutdown" SQL statement, a warning was written to the .trace.db file about an unclosed connection.
When using the built-in connection pool, after calling the "shutdown" SQL statement, a warning was written to the .trace.db file about an unclosed connection.
@changelog_1125_li
@changelog_1127_li
Improved compatibility for "fetch first / next row(s)". Thanks a lot to litailang for the patch!
Improved compatibility for "fetch first / next row(s)". Thanks a lot to litailang for the patch!
@changelog_1126_li
@changelog_1128_li
Improved compatibility with the Java 7 FileSystem abstraction.
Improved compatibility with the Java 7 FileSystem abstraction.
@changelog_1127_h2
@changelog_1129_h2
Version 1.3.160 (2011-09-11)
Version 1.3.160 (2011-09-11)
@changelog_1128_li
@changelog_1130_li
Computed columns could not refer to itself.
Computed columns could not refer to itself.
@changelog_1129_li
@changelog_1131_li
Issue 340: Comparison with "x = all(select ...)" or similar in a view or subquery that was used as a table returned the wrong result.
Issue 340: Comparison with "x = all(select ...)" or similar in a view or subquery that was used as a table returned the wrong result.
@changelog_1130_li
@changelog_1132_li
Comparison with "x = all(select ...)" or similar returned the wrong result for some cases (for example if the subquery returned no rows, or multiple rows with the same value, or null, or if x was null).
Comparison with "x = all(select ...)" or similar returned the wrong result for some cases (for example if the subquery returned no rows, or multiple rows with the same value, or null, or if x was null).
@changelog_1131_li
@changelog_1133_li
Issue 335: Could not run DROP ALL OBJECTS DELETE FILES on older databases with CLOB or BLOB data. The problem was that the metadata table was not locked in some cases, so that a rollback could result in a corrupt database in a database if the lob storage was upgraded.
Issue 335: Could not run DROP ALL OBJECTS DELETE FILES on older databases with CLOB or BLOB data. The problem was that the metadata table was not locked in some cases, so that a rollback could result in a corrupt database in a database if the lob storage was upgraded.
@changelog_1132_li
@changelog_1134_li
Source code switching using //## has been simplified. The Java 1.5 tag has been removed because is no longer needed.
Source code switching using //## has been simplified. The Java 1.5 tag has been removed because is no longer needed.
@changelog_1133_li
@changelog_1135_li
The JDBC methods PreparedStatement.setTimestamp, setTime, and setDate with a calendar, and the methods ResultSet.getTimestamp, getTime, and getDate with a calendar converted the value in the wrong way, so that for some timestamps the converted value was wrong (where summertime starts, one hour per year).
The JDBC methods PreparedStatement.setTimestamp, setTime, and setDate with a calendar, and the methods ResultSet.getTimestamp, getTime, and getDate with a calendar converted the value in the wrong way, so that for some timestamps the converted value was wrong (where summertime starts, one hour per year).
@changelog_1134_li
@changelog_1136_li
Invalid tables names in 'order by' columns were not detected in some cases. Example: select x from dual order by y.x
Invalid tables names in 'order by' columns were not detected in some cases. Example: select x from dual order by y.x
@changelog_1135_li
@changelog_1137_li
Issue 329: CASE expression: data type problem is not detected.
Issue 329: CASE expression: data type problem is not detected.
@changelog_1136_li
@changelog_1138_li
Issue 311: File lock mode serialized: selecting the next value from a sequence didn't work after a pause, because the database thought this is a read-only operation.
Issue 311: File lock mode serialized: selecting the next value from a sequence didn't work after a pause, because the database thought this is a read-only operation.
@changelog_1137_h2
@changelog_1139_h2
Version 1.3.159 (2011-08-13)
Version 1.3.159 (2011-08-13)
@changelog_1138_li
@changelog_1140_li
Creating a temporary table with the option 'transactional' will now also create the indexes in transactional mode, if the indexes are included in the 'create table' statement as follows: "create local temporary table temp(id int primary key, name varchar, constraint x index(name)) transactional".
Creating a temporary table with the option 'transactional' will now also create the indexes in transactional mode, if the indexes are included in the 'create table' statement as follows: "create local temporary table temp(id int primary key, name varchar, constraint x index(name)) transactional".
@changelog_1139_li
@changelog_1141_li
The database file size grows now 35%, but at most 256 MB at a time.
The database file size grows now 35%, but at most 256 MB at a time.
@changelog_1140_li
@changelog_1142_li
Improved error message on network configuration problems.
Improved error message on network configuration problems.
@changelog_1141_li
@changelog_1143_li
The build now support an offline build using ./build.sh offline. This will list the required dependencies if jar files are missing.
The build now support an offline build using ./build.sh offline. This will list the required dependencies if jar files are missing.
@changelog_1142_li
@changelog_1144_li
The BLOB / CLOB data was dropped a little bit before the table was dropped. This could cause "lob not found" errors when the process was killed while a table was dropped.
The BLOB / CLOB data was dropped a little bit before the table was dropped. This could cause "lob not found" errors when the process was killed while a table was dropped.
@changelog_1143_li
@changelog_1145_li
"group_concat(distinct ...)" did not work correctly in a view or subquery (the 'distinct' was lost). Example: select * from (select group_concat(distinct 1) from system_range(1, 3));
"group_concat(distinct ...)" did not work correctly in a view or subquery (the 'distinct' was lost). Example: select * from (select group_concat(distinct 1) from system_range(1, 3));
@changelog_1144_li
@changelog_1146_li
Database URLs can now be re-mapped to another URL using the system property "h2.urlMap", which points to a properties file with database URL mappings.
Database URLs can now be re-mapped to another URL using the system property "h2.urlMap", which points to a properties file with database URL mappings.
@changelog_1145_li
@changelog_1147_li
When using InputStream.skip, trying to read past the end of a BLOB failed with the exception "IO Exception: Missing lob entry: ..." [90028-...].
When using InputStream.skip, trying to read past the end of a BLOB failed with the exception "IO Exception: Missing lob entry: ..." [90028-...].
@changelog_1146_li
@changelog_1148_li
The in-memory file system "memFS:" now has limited support for directories.
The in-memory file system "memFS:" now has limited support for directories.
@changelog_1147_li
@changelog_1149_li
To test recovery, append ;RECOVER_TEST=64 to the database URL. This will simulate an application crash after each 64 writes to the database file. A log file named databaseName.h2.db.log is created that lists the operations. The recovery is tested using an in-memory file system, that means it may require a larger heap setting.
To test recovery, append ;RECOVER_TEST=64 to the database URL. This will simulate an application crash after each 64 writes to the database file. A log file named databaseName.h2.db.log is created that lists the operations. The recovery is tested using an in-memory file system, that means it may require a larger heap setting.
@changelog_1148_li
@changelog_1150_li
Converting a hex string to a byte array is now faster.
Converting a hex string to a byte array is now faster.
@changelog_1149_li
@changelog_1151_li
The SQL statement "shutdown defrag" could corrupt the database if the process was killed while the shutdown was in progress. The same problem could occur when the database setting "defrag_always" was used.
The SQL statement "shutdown defrag" could corrupt the database if the process was killed while the shutdown was in progress. The same problem could occur when the database setting "defrag_always" was used.
@changelog_1150_h2
@changelog_1152_h2
Version 1.3.158 (2011-07-17)
Version 1.3.158 (2011-07-17)
@changelog_1151_li
@changelog_1153_li
Fulltext search (native): after re-opening the connection once the fulltext index was created, a transaction rollback did not roll back the modifications in the index.
Fulltext search (native): after re-opening the connection once the fulltext index was created, a transaction rollback did not roll back the modifications in the index.
@changelog_1152_li
@changelog_1154_li
Support for ROW_NUMBER() OVER() as an alias for ROWNUM() for compatibility with PostgreSQL and Apache Derby.
Support for ROW_NUMBER() OVER() as an alias for ROWNUM() for compatibility with PostgreSQL and Apache Derby.
@changelog_1153_li
@changelog_1155_li
Issue 325: a deadlock in the fulltext search could occur if the connection that was used while initializing the fulltext search was later used to query the database. This was actually not only a problem for fulltext search, but also for other triggers that used the initializing connection later on.
Issue 325: a deadlock in the fulltext search could occur if the connection that was used while initializing the fulltext search was later used to query the database. This was actually not only a problem for fulltext search, but also for other triggers that used the initializing connection later on.
@changelog_1154_li
@changelog_1156_li
DATABASE_TO_UPPER: when set to false, all identifier names (table names, column names) are case sensitive (except aggregate, built-in functions, data types, and keywords). This is for improved compatibility with MySQL and PostgreSQL.
DATABASE_TO_UPPER: when set to false, all identifier names (table names, column names) are case sensitive (except aggregate, built-in functions, data types, and keywords). This is for improved compatibility with MySQL and PostgreSQL.
@changelog_1155_li
@changelog_1157_li
When upgrading from an older 1.3.x version to version 1.3.157, when using BLOB or CLOB data, the database could only be opened once.
When upgrading from an older 1.3.x version to version 1.3.157, when using BLOB or CLOB data, the database could only be opened once.
@changelog_1156_li
@changelog_1158_li
SUM on a boolean expression will now count the number of 'true' rows.
SUM on a boolean expression will now count the number of 'true' rows.
@changelog_1157_li
@changelog_1159_li
Simplified test cases using assertThrows(...).
Simplified test cases using assertThrows(...).
@changelog_1158_li
@changelog_1160_li
A Java function that returns a result set that was generated using the provided connection could cause an internal error in some cases. Now such result sets are copied early on.
A Java function that returns a result set that was generated using the provided connection could cause an internal error in some cases. Now such result sets are copied early on.
@changelog_1159_li
@changelog_1161_li
Data type RESULT_SET: information_schema.function_aliases returned type 0; now type -10 is returned (the same as Oracle: OracleTypes.CURSOR = -10).
Data type RESULT_SET: information_schema.function_aliases returned type 0; now type -10 is returned (the same as Oracle: OracleTypes.CURSOR = -10).
@changelog_1160_li
@changelog_1162_li
Data type RESULT_SET: tables with columns of type RESULT_SET could be created, but no data could be persisted in this column.
Data type RESULT_SET: tables with columns of type RESULT_SET could be created, but no data could be persisted in this column.
@changelog_1161_li
@changelog_1163_li
H2 Console: improved system tray icon for Mac OS X (transparent background).
H2 Console: improved system tray icon for Mac OS X (transparent background).
@changelog_1162_li
@changelog_1164_li
String.toUpperCase() was used a few places, which is problematic when using the Turkish locale. The method has been replaced with toUpperCase(Locale.ENGLISH) to solve such problems.
String.toUpperCase() was used a few places, which is problematic when using the Turkish locale. The method has been replaced with toUpperCase(Locale.ENGLISH) to solve such problems.
@changelog_1163_li
@changelog_1165_li
Shell tool: the built-in command "distinct" has been removed (use the SQL statements "show tables" / "show columns from tableName" instead). The result set formatting has been improved.
Shell tool: the built-in command "distinct" has been removed (use the SQL statements "show tables" / "show columns from tableName" instead). The result set formatting has been improved.
@changelog_1164_li
@changelog_1166_li
MERGE: if a unique key was violated (but not the primary key or the key columns of the merge itself), the wrong exception was thrown.
MERGE: if a unique key was violated (but not the primary key or the key columns of the merge itself), the wrong exception was thrown.
@changelog_1165_li
@changelog_1167_li
IBM DB2 and Apache Derby compatibility: support the pseudo-table SYSIBM.SYSDUMMY1.
IBM DB2 and Apache Derby compatibility: support the pseudo-table SYSIBM.SYSDUMMY1.
@changelog_1166_li
@changelog_1168_li
ROWNUM() did not work in combination with IN(..). The following query did not work as expected: select * from (select rownum r from test) where r in (1, 2).
ROWNUM() did not work in combination with IN(..). The following query did not work as expected: select * from (select rownum r from test) where r in (1, 2).
@changelog_1167_li
@changelog_1169_li
H2 Console autocomplete: the autocomplete feature didn't support quoted names.
H2 Console autocomplete: the autocomplete feature didn't support quoted names.
@changelog_1168_li
@changelog_1170_li
It is now longer allowed to create an index on a CLOB or BLOB column (except for in-memory databases or indexes), because recovery doesn't work on such columns. Fulltext indexes on such column are still supported of course.
It is now longer allowed to create an index on a CLOB or BLOB column (except for in-memory databases or indexes), because recovery doesn't work on such columns. Fulltext indexes on such column are still supported of course.
@changelog_1169_li
@changelog_1171_li
The PUBLIC schema could be renamed, which could result in a database that can't be opened normally. Now it can no longer be renamed. The schema INFORMATION_SCHEMA can also no longer be renamed.
The PUBLIC schema could be renamed, which could result in a database that can't be opened normally. Now it can no longer be renamed. The schema INFORMATION_SCHEMA can also no longer be renamed.
@changelog_1170_li
@changelog_1172_li
Server mode: the problem with server and client using different timezones with different daylight saving rules has been solved (this only applies when both the client and the server use this or a newer version).
Server mode: the problem with server and client using different timezones with different daylight saving rules has been solved (this only applies when both the client and the server use this or a newer version).
@changelog_1171_li
@changelog_1173_li
There is a new system property "h2.storeLocalTime" to avoid problems opening a database file in a timezone that has different daylight saving rules (see also below).
There is a new system property "h2.storeLocalTime" to avoid problems opening a database file in a timezone that has different daylight saving rules (see also below).
@changelog_1172_li
@changelog_1174_li
Date, time, and timestamp data type processing has been re-implemented. Time now supports nanoseconds resolution and now now supports a wider range (negative and large values), similar to PostgreSQL.
Date, time, and timestamp data type processing has been re-implemented. Time now supports nanoseconds resolution and now now supports a wider range (negative and large values), similar to PostgreSQL.
@changelog_1173_li
@changelog_1175_li
SQL statements with a non-breaking space were considered invalid.
SQL statements with a non-breaking space were considered invalid.
@changelog_1174_h2
@changelog_1176_h2
Version 1.3.157 (2011-06-25)
Version 1.3.157 (2011-06-25)
@changelog_1175_li
@changelog_1177_li
The syntax for CREATE TABLE ... AS SELECT ... has been changed: options such as NOT PERSISTENT are now before the query (AS SELECT), because otherwise they might be interpreted as a part of the query.
The syntax for CREATE TABLE ... AS SELECT ... has been changed: options such as NOT PERSISTENT are now before the query (AS SELECT), because otherwise they might be interpreted as a part of the query.
@changelog_1176_li
@changelog_1178_li
With version 1.3.156, the DB2 mode could not be used with CLOB and BLOB data.
With version 1.3.156, the DB2 mode could not be used with CLOB and BLOB data.
@changelog_1177_li
@changelog_1179_li
When upgrading from an older 1.3.x version to version 1.3.156, CLOB and BLOB data was lost in many cases.
When upgrading from an older 1.3.x version to version 1.3.156, CLOB and BLOB data was lost in many cases.
@changelog_1178_li
@changelog_1180_li
The optimization for COUNT(..) on columns that are not nullable was also used for COUNT(DISTINCT ..), which is incorrect.
The optimization for COUNT(..) on columns that are not nullable was also used for COUNT(DISTINCT ..), which is incorrect.
@changelog_1179_li
@changelog_1181_li
PgServer: non-admin users could not open a database.
PgServer: non-admin users could not open a database.
@changelog_1180_li
@changelog_1182_li
Non-admin users could not open a database using a mode (MODE=xxx) if the database was already open, even if the mode matched.
Non-admin users could not open a database using a mode (MODE=xxx) if the database was already open, even if the mode matched.
@changelog_1181_li
@changelog_1183_li
The SQL state of the following exceptions has been changed: From 90009, 90010, 90011 to 22007: "Cannot parse DATE/TIME/TIMESTAMP constant ...".
The SQL state of the following exceptions has been changed: From 90009, 90010, 90011 to 22007: "Cannot parse DATE/TIME/TIMESTAMP constant ...".
@changelog_1182_li
@changelog_1184_li
There is a problem when opening a database file in a timezone that has different daylight saving rules: the time part of dates where the daylight saving doesn't match will differ. This is not a problem within regions that use the same rules (such as, within USA, or within Europe), even if the timezone itself is different. As a workaround, export the database to a SQL script using the old timezone, and create a new database in the new timezone. The same problem occurs when accessing a database over TCP/IP if the client and server timezones use different rules, if an old server or client is used.
There is a problem when opening a database file in a timezone that has different daylight saving rules: the time part of dates where the daylight saving doesn't match will differ. This is not a problem within regions that use the same rules (such as, within USA, or within Europe), even if the timezone itself is different. As a workaround, export the database to a SQL script using the old timezone, and create a new database in the new timezone. The same problem occurs when accessing a database over TCP/IP if the client and server timezones use different rules, if an old server or client is used.
#H2 Console system tray icon: support for Mac OS X retina displays.
#The default jar file is now compiled for Java 6.
@changelog_1003_li
@changelog_1003_li
#The CreateCluster tool could not be used if the source database contained a CLOB or BLOB. The root cause was that the TCP server did not synchronize on the session, which caused a problem when using the exclusive mode.
#The new jar file will probably not end up in the central Maven repository in the next few weeks because Sonatype has disabled automatic synchronization from SourceForge (which they call 'legacy sync' now). It will probably take some time until this is sorted out. The H2 jar files are deployed to http://h2database.com/m2-repo/com/h2database/h2/maven-metadata.xml and http://hsql.sourceforge.net/m2-repo/com/h2database/h2/maven-metadata.xml as usual.
@changelog_1004_li
@changelog_1004_li
#Statement.getQueryTimeout(): only the first call to this method will query the database. If the query timeout was changed in another way than calling setQueryTimeout, this method will always return the last value. This was changed because Hibernate calls getQueryTimeout() a lot.
#A part of the documentation and the H2 Console has been changed to support the Apple retina display.
@changelog_1005_li
@changelog_1005_li
#Issue 416: PreparedStatement.setNString throws AbstractMethodError. All implemented JDBC 4 methods that don't break compatibility with Java 5 are now included in the default jar file.
#The CreateCluster tool could not be used if the source database contained a CLOB or BLOB. The root cause was that the TCP server did not synchronize on the session, which caused a problem when using the exclusive mode.
@changelog_1006_li
@changelog_1006_li
#Issue 414: for some functions, the parameters were evaluated twice (for example "char(nextval(..))" ran "nextval(..)" twice).
#Statement.getQueryTimeout(): only the first call to this method will query the database. If the query timeout was changed in another way than calling setQueryTimeout, this method will always return the last value. This was changed because Hibernate calls getQueryTimeout() a lot.
@changelog_1007_li
@changelog_1007_li
#The ResultSetMetaData methods getSchemaName and getTableName could return null instead of "" (an empty string) as specified in the JDBC API.
#Issue 416: PreparedStatement.setNString throws AbstractMethodError. All implemented JDBC 4 methods that don't break compatibility with Java 5 are now included in the default jar file.
@changelog_1008_li
@changelog_1008_li
#Issue 414: for some functions, the parameters were evaluated twice (for example "char(nextval(..))" ran "nextval(..)" twice).
@changelog_1009_li
#The ResultSetMetaData methods getSchemaName and getTableName could return null instead of "" (an empty string) as specified in the JDBC API.
@changelog_1010_li
#Added compatibility for "SET NAMES" query in MySQL compatibility mode.
#Added compatibility for "SET NAMES" query in MySQL compatibility mode.
@changelog_1009_h2
@changelog_1011_h2
#Version 1.3.168 (2012-07-13)
#Version 1.3.168 (2012-07-13)
@changelog_1010_li
@changelog_1012_li
#The message "Transaction log could not be truncated" was sometimes written to the .trace.db file even if there was no problem truncating the transaction log.
#The message "Transaction log could not be truncated" was sometimes written to the .trace.db file even if there was no problem truncating the transaction log.
@changelog_1011_li
@changelog_1013_li
#New system property "h2.serializeJavaObject" (default: true) that allows to disable serializing Java objects, so that the objects compareTo and toString methods can be used.
#New system property "h2.serializeJavaObject" (default: true) that allows to disable serializing Java objects, so that the objects compareTo and toString methods can be used.
@changelog_1012_li
@changelog_1014_li
#Dylan has translated the H2 Console tool to Korean. Thanks a lot!
#Dylan has translated the H2 Console tool to Korean. Thanks a lot!
@changelog_1013_li
@changelog_1015_li
#Executing the statement CREATE INDEX IF ALREADY EXISTS if the index already exists no longer fails for a read only database.
#Executing the statement CREATE INDEX IF ALREADY EXISTS if the index already exists no longer fails for a read only database.
@changelog_1014_li
@changelog_1016_li
#MVCC: concurrently updating a row could result in the row to appear deleted in the second connection, if there are multiple unique indexes (or a primary key and at least one unique index). Thanks a lot to Teruo for the patch!
#MVCC: concurrently updating a row could result in the row to appear deleted in the second connection, if there are multiple unique indexes (or a primary key and at least one unique index). Thanks a lot to Teruo for the patch!
@changelog_1015_li
@changelog_1017_li
#Fulltext search: in-memory Lucene indexes are now supported.
#Fulltext search: in-memory Lucene indexes are now supported.
@changelog_1016_li
@changelog_1018_li
#Fulltext search: UUID primary keys are now supported.
#Fulltext search: UUID primary keys are now supported.
@changelog_1017_li
@changelog_1019_li
#Apache Tomcat 7.x will now longer log a warning when unloading the web application, if using a connection pool.
#Apache Tomcat 7.x will now longer log a warning when unloading the web application, if using a connection pool.
@changelog_1018_li
@changelog_1020_li
#H2 Console: support the Midori browser (for Debian / Raspberry Pi)
#H2 Console: support the Midori browser (for Debian / Raspberry Pi)
@changelog_1019_li
@changelog_1021_li
#When opening a remote session, don't open a temporary file if the trace level is set to zero
#When opening a remote session, don't open a temporary file if the trace level is set to zero
@changelog_1020_li
@changelog_1022_li
#Use HMAC for authenticating remote LOB id's, removing the need for maintaining a cache, and removing the limit on the number of LOBs per result set.
#Use HMAC for authenticating remote LOB id's, removing the need for maintaining a cache, and removing the limit on the number of LOBs per result set.
@changelog_1021_li
@changelog_1023_li
#H2 Console: HTML and XML documents can now be edited in an updatable result set. There is (limited) support for editing multi-line documents.
#H2 Console: HTML and XML documents can now be edited in an updatable result set. There is (limited) support for editing multi-line documents.
@changelog_1022_h2
@changelog_1024_h2
#Version 1.3.167 (2012-05-23)
#Version 1.3.167 (2012-05-23)
@changelog_1023_li
@changelog_1025_li
#H2 Console: when editing a row, an empty varchar column was replaced with a single space.
#H2 Console: when editing a row, an empty varchar column was replaced with a single space.
@changelog_1024_li
@changelog_1026_li
#Lukas Eder has updated the jOOQ documentation.
#Lukas Eder has updated the jOOQ documentation.
@changelog_1025_li
@changelog_1027_li
#Some nested joins could not be executed, for example: select * from (select * from (select * from a) a right join b b) c;
#Some nested joins could not be executed, for example: select * from (select * from (select * from a) a right join b b) c;
@changelog_1026_li
@changelog_1028_li
#MS SQL Server compatibility: ISNULL is now an alias for IFNULL.
#MS SQL Server compatibility: ISNULL is now an alias for IFNULL.
@changelog_1027_li
@changelog_1029_li
#Terrence Huang has completed the translation of the H2 Console tool to Chinese. Thanks a lot!
#Terrence Huang has completed the translation of the H2 Console tool to Chinese. Thanks a lot!
@changelog_1028_li
@changelog_1030_li
#Server mode: the number of CLOB / BLOB values that were cached on the server is now the maximum of: 5 times the SERVER_RESULT_SET_FETCH_SIZE (which is 100 by default), and SysProperties.SERVER_CACHED_OBJECTS.
#Server mode: the number of CLOB / BLOB values that were cached on the server is now the maximum of: 5 times the SERVER_RESULT_SET_FETCH_SIZE (which is 100 by default), and SysProperties.SERVER_CACHED_OBJECTS.
@changelog_1029_li
@changelog_1031_li
#In the trace file, the query execution time was incorrect in some cases, specially for the statement SET TRACE_LEVEL_FILE 2.
#In the trace file, the query execution time was incorrect in some cases, specially for the statement SET TRACE_LEVEL_FILE 2.
@changelog_1030_li
@changelog_1032_li
#The feature LOG_SIZE_LIMIT that was introduced in version 1.3.165 did not always work correctly (specially with regards to multithreading) and has been removed. The message "Transaction log could not be truncated" is still written to the .trace.db file if required.
#The feature LOG_SIZE_LIMIT that was introduced in version 1.3.165 did not always work correctly (specially with regards to multithreading) and has been removed. The message "Transaction log could not be truncated" is still written to the .trace.db file if required.
@changelog_1031_li
@changelog_1033_li
#Then reading from a resource using the prefix "classpath:", the ContextClassLoader is now used if the resource can't be read otherwise.
#Then reading from a resource using the prefix "classpath:", the ContextClassLoader is now used if the resource can't be read otherwise.
@changelog_1032_li
@changelog_1034_li
#DatabaseEventListener now calls setProgress whenever a statement starts and ends.
#DatabaseEventListener now calls setProgress whenever a statement starts and ends.
@changelog_1033_li
@changelog_1035_li
#DatabaseEventListener now calls setProgress periodically while a statement is running.
#DatabaseEventListener now calls setProgress periodically while a statement is running.
@changelog_1034_li
@changelog_1036_li
#The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME.
#The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME.
@changelog_1035_li
@changelog_1037_li
#Issue 378: when using views, the wrong values were bound to a parameter in some cases.
#Issue 378: when using views, the wrong values were bound to a parameter in some cases.
@changelog_1036_li
@changelog_1038_li
#Terrence Huang has translated the error messages to Chinese. Thanks a lot!
#Terrence Huang has translated the error messages to Chinese. Thanks a lot!
@changelog_1037_li
@changelog_1039_li
#TRUNC was added as an alias for TRUNCATE.
#TRUNC was added as an alias for TRUNCATE.
@changelog_1038_li
@changelog_1040_li
#Small optimisation for accessing result values by column name.
#Small optimisation for accessing result values by column name.
@changelog_1039_li
@changelog_1041_li
#Fix for bug in Statement.getMoreResults(int)
#Fix for bug in Statement.getMoreResults(int)
@changelog_1040_li
@changelog_1042_li
#The SCRIPT statements now supports filtering by schema and table. Thanks a lot to Jacob Qvortrup for providing the patch!
#The SCRIPT statements now supports filtering by schema and table. Thanks a lot to Jacob Qvortrup for providing the patch!
@changelog_1041_h2
@changelog_1043_h2
#Version 1.3.166 (2012-04-08)
#Version 1.3.166 (2012-04-08)
@changelog_1042_li
@changelog_1044_li
#Indexes on column that are larger than half the page size (wide indexes) could sometimes get corrupt, resulting in an ArrayIndexOutOfBoundsException in PageBtree.getRow or "Row not found" in PageBtreeLeaf. Also, such indexes used too much disk space.
#Indexes on column that are larger than half the page size (wide indexes) could sometimes get corrupt, resulting in an ArrayIndexOutOfBoundsException in PageBtree.getRow or "Row not found" in PageBtreeLeaf. Also, such indexes used too much disk space.
@changelog_1043_li
@changelog_1045_li
#Server mode: when retrieving more than 64 rows each containing a CLOB or BLOB, the error message "The object is already closed" was thrown.
#Server mode: when retrieving more than 64 rows each containing a CLOB or BLOB, the error message "The object is already closed" was thrown.
@changelog_1044_li
@changelog_1046_li
#ConvertTraceFile: the time in the trace file is now parsed as a long.
#ConvertTraceFile: the time in the trace file is now parsed as a long.
@changelog_1045_li
@changelog_1047_li
#Invalid connection settings are now detected.
#Invalid connection settings are now detected.
@changelog_1046_li
@changelog_1048_li
#Issue 387: WHERE condition getting pushed into sub-query with LIMIT.
#Issue 387: WHERE condition getting pushed into sub-query with LIMIT.
@changelog_1047_h2
@changelog_1049_h2
#Version 1.3.165 (2012-03-18)
#Version 1.3.165 (2012-03-18)
@changelog_1048_li
@changelog_1050_li
#Better string representation for decimal values (for example 0.00000000 instead of 0E-26).
#Better string representation for decimal values (for example 0.00000000 instead of 0E-26).
@changelog_1049_li
@changelog_1051_li
#Prepared statements could only be re-used if the same data types were used the second time they were executed.
#Prepared statements could only be re-used if the same data types were used the second time they were executed.
@changelog_1050_li
@changelog_1052_li
#In error messages about referential constraint violation, the values are now included.
#In error messages about referential constraint violation, the values are now included.
@changelog_1051_li
@changelog_1053_li
#SCRIPT and RUNSCRIPT: the password can now be set using a prepared statement. Previously, it was required to be a literal in the SQL statement.
#SCRIPT and RUNSCRIPT: the password can now be set using a prepared statement. Previously, it was required to be a literal in the SQL statement.
@changelog_1052_li
@changelog_1054_li
#MySQL compatibility: SUBSTR with a negative start index now works like MySQL.
#MySQL compatibility: SUBSTR with a negative start index now works like MySQL.
@changelog_1053_li
@changelog_1055_li
#When enabling autocommit, the transaction is now committed (as required by the JDBC API).
#When enabling autocommit, the transaction is now committed (as required by the JDBC API).
@changelog_1054_li
@changelog_1056_li
#The shell script <code>h2.sh</code> did not work with spaces in the path. It also works now with quoted spaces in the argument list. Thanks a lot to Shimizu Fumiyuki for the patch!
#The shell script <code>h2.sh</code> did not work with spaces in the path. It also works now with quoted spaces in the argument list. Thanks a lot to Shimizu Fumiyuki for the patch!
@changelog_1055_li
@changelog_1057_li
#If the transaction log could not be truncated because of an uncommitted transaction, now "Transaction log could not be truncated" is written to the .trace.db file. Before, the database file was growing and it was hard to find out what the root cause was. To avoid the database file from growing, a new feature to automatically rollback the oldest transaction is available now. To enable it, append ;LOG_SIZE_LIMIT=32 to the database URL (in that case, the oldest session is rolled back if the transaction log is 32 MB).
#If the transaction log could not be truncated because of an uncommitted transaction, now "Transaction log could not be truncated" is written to the .trace.db file. Before, the database file was growing and it was hard to find out what the root cause was. To avoid the database file from growing, a new feature to automatically rollback the oldest transaction is available now. To enable it, append ;LOG_SIZE_LIMIT=32 to the database URL (in that case, the oldest session is rolled back if the transaction log is 32 MB).
@changelog_1056_li
@changelog_1058_li
#ALTER TABLE ADD can now add more than one column at a time.
#ALTER TABLE ADD can now add more than one column at a time.
@changelog_1057_li
@changelog_1059_li
#Issue 380: ALTER TABLE ADD FOREIGN KEY with an explicit index didn't verify the index can be used, which would lead to a NullPointerException later on.
#Issue 380: ALTER TABLE ADD FOREIGN KEY with an explicit index didn't verify the index can be used, which would lead to a NullPointerException later on.
@changelog_1058_li
@changelog_1060_li
#Issue 384: the wrong kind of exception (NullPointerException) was thrown in a UNION query with an incorrect ORDER BY expression.
#Issue 384: the wrong kind of exception (NullPointerException) was thrown in a UNION query with an incorrect ORDER BY expression.
@changelog_1059_li
@changelog_1061_li
#Issue 362: support LIMIT in UPDATE statements.
#Issue 362: support LIMIT in UPDATE statements.
@changelog_1060_li
@changelog_1062_li
#Browser: if no default browser is set, Google Chrome is now used if available. If not available, then Konqueror, Netscape, or Opera is used if available (as before).
#Browser: if no default browser is set, Google Chrome is now used if available. If not available, then Konqueror, Netscape, or Opera is used if available (as before).
@changelog_1061_li
@changelog_1063_li
#CSV tool: new feature to disable writing the column header (option writeColumnHeader).
#CSV tool: new feature to disable writing the column header (option writeColumnHeader).
@changelog_1062_li
@changelog_1064_li
#CSV tool: new feature to preserve the case sensitivity of column names (option caseSensitiveColumnNames).
#CSV tool: new feature to preserve the case sensitivity of column names (option caseSensitiveColumnNames).
@changelog_1063_li
@changelog_1065_li
#PostgreSQL compatibility: LOG(x) is base 10 in the PostgreSQL mode.
#PostgreSQL compatibility: LOG(x) is base 10 in the PostgreSQL mode.
@changelog_1064_h2
@changelog_1066_h2
#Version 1.3.164 (2012-02-03)
#Version 1.3.164 (2012-02-03)
@changelog_1065_li
@changelog_1067_li
#New built-in function ARRAY_CONTAINS.
#New built-in function ARRAY_CONTAINS.
@changelog_1066_li
@changelog_1068_li
#Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
#Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
@changelog_1067_li
@changelog_1069_li
#Trying to convert a VARCHAR to UUID will now fail if the text contains a character that is not a hex digit, '-', or not a whitespace.
#Trying to convert a VARCHAR to UUID will now fail if the text contains a character that is not a hex digit, '-', or not a whitespace.
@changelog_1068_li
@changelog_1070_li
#TriggerAdapter: in "before" triggers, values can be changed using the ResultSet.updateX methods.
#TriggerAdapter: in "before" triggers, values can be changed using the ResultSet.updateX methods.
@changelog_1069_li
@changelog_1071_li
#Creating a table with column data type NULL now works (even if not very useful).
#Creating a table with column data type NULL now works (even if not very useful).
@changelog_1070_li
@changelog_1072_li
#ALTER TABLE ALTER COLUMN no longer copies the data for widening conversions (for example if only the precision was increased) unless necessary.
#ALTER TABLE ALTER COLUMN no longer copies the data for widening conversions (for example if only the precision was increased) unless necessary.
@changelog_1071_li
@changelog_1073_li
#Multi-threaded kernel: concurrently running an online backup and updating the database resulted in a broken (transactionally incorrect) backup file in some cases.
#Multi-threaded kernel: concurrently running an online backup and updating the database resulted in a broken (transactionally incorrect) backup file in some cases.
@changelog_1072_li
@changelog_1074_li
#The script created by SCRIPT DROP did not always work if multiple views existed that depend on each other.
#The script created by SCRIPT DROP did not always work if multiple views existed that depend on each other.
@changelog_1073_li
@changelog_1075_li
#MathUtils.getSecureRandom could log a warning to System.err in case the /dev/random is very slow, and the System.getProperties().toString() returned a string larger than 64 KB.
#MathUtils.getSecureRandom could log a warning to System.err in case the /dev/random is very slow, and the System.getProperties().toString() returned a string larger than 64 KB.
@changelog_1074_li
@changelog_1076_li
#The database file locking mechanism "FS" (;FILE_LOCK=FS) did not work on Linux since version 1.3.161.
#The database file locking mechanism "FS" (;FILE_LOCK=FS) did not work on Linux since version 1.3.161.
@changelog_1075_li
@changelog_1077_li
#Sequences: the functions NEXTVAL and CURRVAL did not work as expected when using quoted, mixed case sequence names.
#Sequences: the functions NEXTVAL and CURRVAL did not work as expected when using quoted, mixed case sequence names.
@changelog_1076_li
@changelog_1078_li
#The constructor for Csv objects is now public, and Csv.getInstance() is now deprecated.
#The constructor for Csv objects is now public, and Csv.getInstance() is now deprecated.
@changelog_1077_li
@changelog_1079_li
#SimpleResultSet: updating a result set is now supported.
#SimpleResultSet: updating a result set is now supported.
@changelog_1078_li
@changelog_1080_li
#Database URL: extra semicolons are not supported.
#Database URL: extra semicolons are not supported.
@changelog_1079_h2
@changelog_1081_h2
#Version 1.3.163 (2011-12-30)
#Version 1.3.163 (2011-12-30)
@changelog_1080_li
@changelog_1082_li
#On out of disk space, the database could get corrupt sometimes, if later write operations succeeded. The same problem happened on other kinds of I/O exceptions (where one or some of the writes fail, but subsequent writes succeed). Now the file is closed on the first unsuccessful write operation, so that later requests fail consistently.
#On out of disk space, the database could get corrupt sometimes, if later write operations succeeded. The same problem happened on other kinds of I/O exceptions (where one or some of the writes fail, but subsequent writes succeed). Now the file is closed on the first unsuccessful write operation, so that later requests fail consistently.
@changelog_1081_li
@changelog_1083_li
#DatabaseEventListener.diskSpaceIsLow() is no longer supported because it can't be guaranteed that it always works correctly.
#DatabaseEventListener.diskSpaceIsLow() is no longer supported because it can't be guaranteed that it always works correctly.
@changelog_1082_li
@changelog_1084_li
#XMLTEXT now supports an optional parameter to escape newlines.
#XMLTEXT now supports an optional parameter to escape newlines.
@changelog_1083_li
@changelog_1085_li
#XMLNODE now support an optional parameter to disable indentation.
#XMLNODE now support an optional parameter to disable indentation.
@changelog_1084_li
@changelog_1086_li
#Csv.write now formats date, time, and timestamp values using java.sql.Date / Time / Timestamp.toString(). Previously, ResultSet.getString() was used, which didn't work well for Oracle.
#Csv.write now formats date, time, and timestamp values using java.sql.Date / Time / Timestamp.toString(). Previously, ResultSet.getString() was used, which didn't work well for Oracle.
@changelog_1085_li
@changelog_1087_li
#The shell script <code>h2.sh</code> can now be run from within a different directory. Thanks a lot to Daniel Serodio for the patch!
#The shell script <code>h2.sh</code> can now be run from within a different directory. Thanks a lot to Daniel Serodio for the patch!
@changelog_1086_li
@changelog_1088_li
#The page size of a persistent database can now be queries using: select * from information_schema.settings where name = 'info.PAGE_SIZE'
#The page size of a persistent database can now be queries using: select * from information_schema.settings where name = 'info.PAGE_SIZE'
@changelog_1087_li
@changelog_1089_li
#In the server mode, BLOB and CLOB objects are no longer closed when the result set is closed (as required by the JDBC spec).
#In the server mode, BLOB and CLOB objects are no longer closed when the result set is closed (as required by the JDBC spec).
@changelog_1088_h2
@changelog_1090_h2
#Version 1.3.162 (2011-11-26)
#Version 1.3.162 (2011-11-26)
@changelog_1089_li
@changelog_1091_li
#The following system properties are no longer supported: <code>h2.allowBigDecimalExtensions</code>, <code>h2.emptyPassword</code>, <code>h2.minColumnNameMap</code>, <code>h2.returnLobObjects</code>, <code>h2.webMaxValueLength</code>.
#The following system properties are no longer supported: <code>h2.allowBigDecimalExtensions</code>, <code>h2.emptyPassword</code>, <code>h2.minColumnNameMap</code>, <code>h2.returnLobObjects</code>, <code>h2.webMaxValueLength</code>.
@changelog_1090_li
@changelog_1092_li
#When using a VPN, starting a H2 server did not work (for some VPN software).
#When using a VPN, starting a H2 server did not work (for some VPN software).
@changelog_1091_li
@changelog_1093_li
#Oracle compatibility: support for DECODE(...).
#Oracle compatibility: support for DECODE(...).
@changelog_1092_li
@changelog_1094_li
#Lucene fulltext search: creating an index is now faster if the table already contains data. Thanks a lot to Angel Leon from the FrostWire Team for the patch!
#Lucene fulltext search: creating an index is now faster if the table already contains data. Thanks a lot to Angel Leon from the FrostWire Team for the patch!
@changelog_1093_li
@changelog_1095_li
#Update statements with a column list in brackets did not work if the list only contains one column. Example: update test set (id)=(id).
#Update statements with a column list in brackets did not work if the list only contains one column. Example: update test set (id)=(id).
@changelog_1094_li
@changelog_1096_li
#Read-only databases in a zip file did not work when using the -baseDir option.
#Read-only databases in a zip file did not work when using the -baseDir option.
@changelog_1095_li
@changelog_1097_li
#Issue 334: SimpleResultSet.getString now also works for Clob columns.
#Issue 334: SimpleResultSet.getString now also works for Clob columns.
@changelog_1096_li
@changelog_1098_li
#Subqueries with an aggregate did not always work. Example: select (select count(*) from test where a = t.a and b = 0) from test t group by a
#Subqueries with an aggregate did not always work. Example: select (select count(*) from test where a = t.a and b = 0) from test t group by a
@changelog_1097_li
@changelog_1099_li
#Server: in some (theoretical) cases, exceptions while closing the connection were ignored.
#Server: in some (theoretical) cases, exceptions while closing the connection were ignored.
@changelog_1098_li
@changelog_1100_li
#Server.createTcpServer, createPgServer, createWebServer: invalid arguments are now detected.
#Server.createTcpServer, createPgServer, createWebServer: invalid arguments are now detected.
@changelog_1099_li
@changelog_1101_li
#The selectivity of LOB columns is no longer calculated because indexes on LOB columns are not supported (however this should have little effect on performance, as the selectivity is calculated from the hash code and not the data).
#The selectivity of LOB columns is no longer calculated because indexes on LOB columns are not supported (however this should have little effect on performance, as the selectivity is calculated from the hash code and not the data).
@changelog_1100_li
@changelog_1102_li
#New experimental system property "h2.modifyOnWrite": when enabled, the database file is only modified when writing to the database. When enabled, the serialized file lock is much faster for read-only operations.
#New experimental system property "h2.modifyOnWrite": when enabled, the database file is only modified when writing to the database. When enabled, the serialized file lock is much faster for read-only operations.
@changelog_1101_li
@changelog_1103_li
#A NullPointerException could occur in TableView.isDeterministic for invalid views.
#A NullPointerException could occur in TableView.isDeterministic for invalid views.
@changelog_1102_li
@changelog_1104_li
#Issue 180: when deserializing objects, the context class loader is used instead of the default class loader if the system property "h2.useThreadContextClassLoader" is set. Thanks a lot to Noah Fontes for the patch!
#Issue 180: when deserializing objects, the context class loader is used instead of the default class loader if the system property "h2.useThreadContextClassLoader" is set. Thanks a lot to Noah Fontes for the patch!
@changelog_1103_li
@changelog_1105_li
#When using the exclusive mode, LOB operations could cause the thread to block. This also affected the CreateCluster tool (when using BLOB or CLOB data).
#When using the exclusive mode, LOB operations could cause the thread to block. This also affected the CreateCluster tool (when using BLOB or CLOB data).
@changelog_1104_li
@changelog_1106_li
#The optimization for "group by" was not working correctly if the group by column was aliased in the select list.
#The optimization for "group by" was not working correctly if the group by column was aliased in the select list.
@changelog_1105_li
@changelog_1107_li
#Issue 326: improved support for case sensitive (mixed case) identifiers without quotes when using DATABASE_TO_UPPER=FALSE.
#Issue 326: improved support for case sensitive (mixed case) identifiers without quotes when using DATABASE_TO_UPPER=FALSE.
@changelog_1106_h2
@changelog_1108_h2
#Version 1.3.161 (2011-10-28)
#Version 1.3.161 (2011-10-28)
@changelog_1107_li
@changelog_1109_li
#Issue 351: MySQL mode: can not create a table with the column "KEY", and can not open databases where such a table already exists.
#Issue 351: MySQL mode: can not create a table with the column "KEY", and can not open databases where such a table already exists.
@changelog_1108_li
@changelog_1110_li
#TCP server: when using the trace option ("-trace"), the trace output contained unnecessary stack traces when stopping the server.
#TCP server: when using the trace option ("-trace"), the trace output contained unnecessary stack traces when stopping the server.
@changelog_1109_li
@changelog_1111_li
#Issue 354: when using the multi-threaded kernel option, and multiple threads concurrently prepared SQL statements that use the same view or the same index of a view, then in some cases an infinite loop could occur.
#Issue 354: when using the multi-threaded kernel option, and multiple threads concurrently prepared SQL statements that use the same view or the same index of a view, then in some cases an infinite loop could occur.
@changelog_1110_li
@changelog_1112_li
#Issue 350: when using instead of triggers, executeUpdate for delete operations always returned 0.
#Issue 350: when using instead of triggers, executeUpdate for delete operations always returned 0.
@changelog_1111_li
@changelog_1113_li
#Some timestamps with timezone were not converted correctly. For example, in the PST timezone, the timestamp 2011-10-26 08:00:00Z was converted to 2011-10-25 25:00:00 instead of 2011-10-26 01:00:00. Depending on the database operation, this caused subsequent error.
#Some timestamps with timezone were not converted correctly. For example, in the PST timezone, the timestamp 2011-10-26 08:00:00Z was converted to 2011-10-25 25:00:00 instead of 2011-10-26 01:00:00. Depending on the database operation, this caused subsequent error.
@changelog_1112_li
@changelog_1114_li
#Sequences with cache size smaller than 0 did not work correctly.
#Sequences with cache size smaller than 0 did not work correctly.
@changelog_1113_li
@changelog_1115_li
#Issue 356: for Blob objects, InputStream.skip() returned 0, causing EOFException in Blob.getBytes(.., ..).
#Issue 356: for Blob objects, InputStream.skip() returned 0, causing EOFException in Blob.getBytes(.., ..).
@changelog_1114_li
@changelog_1116_li
#Updatable result sets: if the value is not set when inserting a new row, the default value is now used (the same behavior as MySQL, PostgreSQL, and Apache Derby) instead of NULL.
#Updatable result sets: if the value is not set when inserting a new row, the default value is now used (the same behavior as MySQL, PostgreSQL, and Apache Derby) instead of NULL.
@changelog_1115_li
@changelog_1117_li
#Conditions of the form IN(SELECT ...) where slow and increased the database size if the subquery result size was larger then the configured MAX_MEMORY_ROWS.
#Conditions of the form IN(SELECT ...) where slow and increased the database size if the subquery result size was larger then the configured MAX_MEMORY_ROWS.
@changelog_1116_li
@changelog_1118_li
#Issue 347: the RunScript and Shell tools now ignore empty statements.
#Issue 347: the RunScript and Shell tools now ignore empty statements.
@changelog_1117_li
@changelog_1119_li
#Issue 246: improved error message for data conversion problems.
#Issue 246: improved error message for data conversion problems.
@changelog_1118_li
@changelog_1120_li
#Issue 344: the build now supports a custom Maven repository location.
#Issue 344: the build now supports a custom Maven repository location.
@changelog_1119_li
@changelog_1121_li
#Issue 334: Java functions that return CLOB or BLOB objects could not be used as tables.
#Issue 334: Java functions that return CLOB or BLOB objects could not be used as tables.
@changelog_1120_li
@changelog_1122_li
#SimpleResultSet now supports getColumnTypeName and getColumnClassName.
#SimpleResultSet now supports getColumnTypeName and getColumnClassName.
@changelog_1121_li
@changelog_1123_li
#SimpleResultSet now has minimal BLOB and CLOB support.
#SimpleResultSet now has minimal BLOB and CLOB support.
@changelog_1122_li
@changelog_1124_li
#Improved performance for large databases (many GB), and databases with a small page size.
#Improved performance for large databases (many GB), and databases with a small page size.
@changelog_1123_li
@changelog_1125_li
#The Polish translation has been improved by Jarosław Kokociński.
#The Polish translation has been improved by Jarosław Kokociński.
@changelog_1124_li
@changelog_1126_li
#When using the built-in connection pool, after calling the "shutdown" SQL statement, a warning was written to the .trace.db file about an unclosed connection.
#When using the built-in connection pool, after calling the "shutdown" SQL statement, a warning was written to the .trace.db file about an unclosed connection.
@changelog_1125_li
@changelog_1127_li
#Improved compatibility for "fetch first / next row(s)". Thanks a lot to litailang for the patch!
#Improved compatibility for "fetch first / next row(s)". Thanks a lot to litailang for the patch!
@changelog_1126_li
@changelog_1128_li
#Improved compatibility with the Java 7 FileSystem abstraction.
#Improved compatibility with the Java 7 FileSystem abstraction.
@changelog_1127_h2
@changelog_1129_h2
#Version 1.3.160 (2011-09-11)
#Version 1.3.160 (2011-09-11)
@changelog_1128_li
@changelog_1130_li
#Computed columns could not refer to itself.
#Computed columns could not refer to itself.
@changelog_1129_li
@changelog_1131_li
#Issue 340: Comparison with "x = all(select ...)" or similar in a view or subquery that was used as a table returned the wrong result.
#Issue 340: Comparison with "x = all(select ...)" or similar in a view or subquery that was used as a table returned the wrong result.
@changelog_1130_li
@changelog_1132_li
#Comparison with "x = all(select ...)" or similar returned the wrong result for some cases (for example if the subquery returned no rows, or multiple rows with the same value, or null, or if x was null).
#Comparison with "x = all(select ...)" or similar returned the wrong result for some cases (for example if the subquery returned no rows, or multiple rows with the same value, or null, or if x was null).
@changelog_1131_li
@changelog_1133_li
#Issue 335: Could not run DROP ALL OBJECTS DELETE FILES on older databases with CLOB or BLOB data. The problem was that the metadata table was not locked in some cases, so that a rollback could result in a corrupt database in a database if the lob storage was upgraded.
#Issue 335: Could not run DROP ALL OBJECTS DELETE FILES on older databases with CLOB or BLOB data. The problem was that the metadata table was not locked in some cases, so that a rollback could result in a corrupt database in a database if the lob storage was upgraded.
@changelog_1132_li
@changelog_1134_li
#Source code switching using //## has been simplified. The Java 1.5 tag has been removed because is no longer needed.
#Source code switching using //## has been simplified. The Java 1.5 tag has been removed because is no longer needed.
@changelog_1133_li
@changelog_1135_li
#The JDBC methods PreparedStatement.setTimestamp, setTime, and setDate with a calendar, and the methods ResultSet.getTimestamp, getTime, and getDate with a calendar converted the value in the wrong way, so that for some timestamps the converted value was wrong (where summertime starts, one hour per year).
#The JDBC methods PreparedStatement.setTimestamp, setTime, and setDate with a calendar, and the methods ResultSet.getTimestamp, getTime, and getDate with a calendar converted the value in the wrong way, so that for some timestamps the converted value was wrong (where summertime starts, one hour per year).
@changelog_1134_li
@changelog_1136_li
#Invalid tables names in 'order by' columns were not detected in some cases. Example: select x from dual order by y.x
#Invalid tables names in 'order by' columns were not detected in some cases. Example: select x from dual order by y.x
@changelog_1135_li
@changelog_1137_li
#Issue 329: CASE expression: data type problem is not detected.
#Issue 329: CASE expression: data type problem is not detected.
@changelog_1136_li
@changelog_1138_li
#Issue 311: File lock mode serialized: selecting the next value from a sequence didn't work after a pause, because the database thought this is a read-only operation.
#Issue 311: File lock mode serialized: selecting the next value from a sequence didn't work after a pause, because the database thought this is a read-only operation.
@changelog_1137_h2
@changelog_1139_h2
#Version 1.3.159 (2011-08-13)
#Version 1.3.159 (2011-08-13)
@changelog_1138_li
@changelog_1140_li
#Creating a temporary table with the option 'transactional' will now also create the indexes in transactional mode, if the indexes are included in the 'create table' statement as follows: "create local temporary table temp(id int primary key, name varchar, constraint x index(name)) transactional".
#Creating a temporary table with the option 'transactional' will now also create the indexes in transactional mode, if the indexes are included in the 'create table' statement as follows: "create local temporary table temp(id int primary key, name varchar, constraint x index(name)) transactional".
@changelog_1139_li
@changelog_1141_li
#The database file size grows now 35%, but at most 256 MB at a time.
#The database file size grows now 35%, but at most 256 MB at a time.
@changelog_1140_li
@changelog_1142_li
#Improved error message on network configuration problems.
#Improved error message on network configuration problems.
@changelog_1141_li
@changelog_1143_li
#The build now support an offline build using ./build.sh offline. This will list the required dependencies if jar files are missing.
#The build now support an offline build using ./build.sh offline. This will list the required dependencies if jar files are missing.
@changelog_1142_li
@changelog_1144_li
#The BLOB / CLOB data was dropped a little bit before the table was dropped. This could cause "lob not found" errors when the process was killed while a table was dropped.
#The BLOB / CLOB data was dropped a little bit before the table was dropped. This could cause "lob not found" errors when the process was killed while a table was dropped.
@changelog_1143_li
@changelog_1145_li
#"group_concat(distinct ...)" did not work correctly in a view or subquery (the 'distinct' was lost). Example: select * from (select group_concat(distinct 1) from system_range(1, 3));
#"group_concat(distinct ...)" did not work correctly in a view or subquery (the 'distinct' was lost). Example: select * from (select group_concat(distinct 1) from system_range(1, 3));
@changelog_1144_li
@changelog_1146_li
#Database URLs can now be re-mapped to another URL using the system property "h2.urlMap", which points to a properties file with database URL mappings.
#Database URLs can now be re-mapped to another URL using the system property "h2.urlMap", which points to a properties file with database URL mappings.
@changelog_1145_li
@changelog_1147_li
#When using InputStream.skip, trying to read past the end of a BLOB failed with the exception "IO Exception: Missing lob entry: ..." [90028-...].
#When using InputStream.skip, trying to read past the end of a BLOB failed with the exception "IO Exception: Missing lob entry: ..." [90028-...].
@changelog_1146_li
@changelog_1148_li
#The in-memory file system "memFS:" now has limited support for directories.
#The in-memory file system "memFS:" now has limited support for directories.
@changelog_1147_li
@changelog_1149_li
#To test recovery, append ;RECOVER_TEST=64 to the database URL. This will simulate an application crash after each 64 writes to the database file. A log file named databaseName.h2.db.log is created that lists the operations. The recovery is tested using an in-memory file system, that means it may require a larger heap setting.
#To test recovery, append ;RECOVER_TEST=64 to the database URL. This will simulate an application crash after each 64 writes to the database file. A log file named databaseName.h2.db.log is created that lists the operations. The recovery is tested using an in-memory file system, that means it may require a larger heap setting.
@changelog_1148_li
@changelog_1150_li
#Converting a hex string to a byte array is now faster.
#Converting a hex string to a byte array is now faster.
@changelog_1149_li
@changelog_1151_li
#The SQL statement "shutdown defrag" could corrupt the database if the process was killed while the shutdown was in progress. The same problem could occur when the database setting "defrag_always" was used.
#The SQL statement "shutdown defrag" could corrupt the database if the process was killed while the shutdown was in progress. The same problem could occur when the database setting "defrag_always" was used.
@changelog_1150_h2
@changelog_1152_h2
#Version 1.3.158 (2011-07-17)
#Version 1.3.158 (2011-07-17)
@changelog_1151_li
@changelog_1153_li
#Fulltext search (native): after re-opening the connection once the fulltext index was created, a transaction rollback did not roll back the modifications in the index.
#Fulltext search (native): after re-opening the connection once the fulltext index was created, a transaction rollback did not roll back the modifications in the index.
@changelog_1152_li
@changelog_1154_li
#Support for ROW_NUMBER() OVER() as an alias for ROWNUM() for compatibility with PostgreSQL and Apache Derby.
#Support for ROW_NUMBER() OVER() as an alias for ROWNUM() for compatibility with PostgreSQL and Apache Derby.
@changelog_1153_li
@changelog_1155_li
#Issue 325: a deadlock in the fulltext search could occur if the connection that was used while initializing the fulltext search was later used to query the database. This was actually not only a problem for fulltext search, but also for other triggers that used the initializing connection later on.
#Issue 325: a deadlock in the fulltext search could occur if the connection that was used while initializing the fulltext search was later used to query the database. This was actually not only a problem for fulltext search, but also for other triggers that used the initializing connection later on.
@changelog_1154_li
@changelog_1156_li
#DATABASE_TO_UPPER: when set to false, all identifier names (table names, column names) are case sensitive (except aggregate, built-in functions, data types, and keywords). This is for improved compatibility with MySQL and PostgreSQL.
#DATABASE_TO_UPPER: when set to false, all identifier names (table names, column names) are case sensitive (except aggregate, built-in functions, data types, and keywords). This is for improved compatibility with MySQL and PostgreSQL.
@changelog_1155_li
@changelog_1157_li
#When upgrading from an older 1.3.x version to version 1.3.157, when using BLOB or CLOB data, the database could only be opened once.
#When upgrading from an older 1.3.x version to version 1.3.157, when using BLOB or CLOB data, the database could only be opened once.
@changelog_1156_li
@changelog_1158_li
#SUM on a boolean expression will now count the number of 'true' rows.
#SUM on a boolean expression will now count the number of 'true' rows.
@changelog_1157_li
@changelog_1159_li
#Simplified test cases using assertThrows(...).
#Simplified test cases using assertThrows(...).
@changelog_1158_li
@changelog_1160_li
#A Java function that returns a result set that was generated using the provided connection could cause an internal error in some cases. Now such result sets are copied early on.
#A Java function that returns a result set that was generated using the provided connection could cause an internal error in some cases. Now such result sets are copied early on.
@changelog_1159_li
@changelog_1161_li
#Data type RESULT_SET: information_schema.function_aliases returned type 0; now type -10 is returned (the same as Oracle: OracleTypes.CURSOR = -10).
#Data type RESULT_SET: information_schema.function_aliases returned type 0; now type -10 is returned (the same as Oracle: OracleTypes.CURSOR = -10).
@changelog_1160_li
@changelog_1162_li
#Data type RESULT_SET: tables with columns of type RESULT_SET could be created, but no data could be persisted in this column.
#Data type RESULT_SET: tables with columns of type RESULT_SET could be created, but no data could be persisted in this column.
@changelog_1161_li
@changelog_1163_li
#H2 Console: improved system tray icon for Mac OS X (transparent background).
#H2 Console: improved system tray icon for Mac OS X (transparent background).
@changelog_1162_li
@changelog_1164_li
#String.toUpperCase() was used a few places, which is problematic when using the Turkish locale. The method has been replaced with toUpperCase(Locale.ENGLISH) to solve such problems.
#String.toUpperCase() was used a few places, which is problematic when using the Turkish locale. The method has been replaced with toUpperCase(Locale.ENGLISH) to solve such problems.
@changelog_1163_li
@changelog_1165_li
#Shell tool: the built-in command "distinct" has been removed (use the SQL statements "show tables" / "show columns from tableName" instead). The result set formatting has been improved.
#Shell tool: the built-in command "distinct" has been removed (use the SQL statements "show tables" / "show columns from tableName" instead). The result set formatting has been improved.
@changelog_1164_li
@changelog_1166_li
#MERGE: if a unique key was violated (but not the primary key or the key columns of the merge itself), the wrong exception was thrown.
#MERGE: if a unique key was violated (but not the primary key or the key columns of the merge itself), the wrong exception was thrown.
@changelog_1165_li
@changelog_1167_li
#IBM DB2 and Apache Derby compatibility: support the pseudo-table SYSIBM.SYSDUMMY1.
#IBM DB2 and Apache Derby compatibility: support the pseudo-table SYSIBM.SYSDUMMY1.
@changelog_1166_li
@changelog_1168_li
#ROWNUM() did not work in combination with IN(..). The following query did not work as expected: select * from (select rownum r from test) where r in (1, 2).
#ROWNUM() did not work in combination with IN(..). The following query did not work as expected: select * from (select rownum r from test) where r in (1, 2).
@changelog_1167_li
@changelog_1169_li
#H2 Console autocomplete: the autocomplete feature didn't support quoted names.
#H2 Console autocomplete: the autocomplete feature didn't support quoted names.
@changelog_1168_li
@changelog_1170_li
#It is now longer allowed to create an index on a CLOB or BLOB column (except for in-memory databases or indexes), because recovery doesn't work on such columns. Fulltext indexes on such column are still supported of course.
#It is now longer allowed to create an index on a CLOB or BLOB column (except for in-memory databases or indexes), because recovery doesn't work on such columns. Fulltext indexes on such column are still supported of course.
@changelog_1169_li
@changelog_1171_li
#The PUBLIC schema could be renamed, which could result in a database that can't be opened normally. Now it can no longer be renamed. The schema INFORMATION_SCHEMA can also no longer be renamed.
#The PUBLIC schema could be renamed, which could result in a database that can't be opened normally. Now it can no longer be renamed. The schema INFORMATION_SCHEMA can also no longer be renamed.
@changelog_1170_li
@changelog_1172_li
#Server mode: the problem with server and client using different timezones with different daylight saving rules has been solved (this only applies when both the client and the server use this or a newer version).
#Server mode: the problem with server and client using different timezones with different daylight saving rules has been solved (this only applies when both the client and the server use this or a newer version).
@changelog_1171_li
@changelog_1173_li
#There is a new system property "h2.storeLocalTime" to avoid problems opening a database file in a timezone that has different daylight saving rules (see also below).
#There is a new system property "h2.storeLocalTime" to avoid problems opening a database file in a timezone that has different daylight saving rules (see also below).
@changelog_1172_li
@changelog_1174_li
#Date, time, and timestamp data type processing has been re-implemented. Time now supports nanoseconds resolution and now now supports a wider range (negative and large values), similar to PostgreSQL.
#Date, time, and timestamp data type processing has been re-implemented. Time now supports nanoseconds resolution and now now supports a wider range (negative and large values), similar to PostgreSQL.
@changelog_1173_li
@changelog_1175_li
#SQL statements with a non-breaking space were considered invalid.
#SQL statements with a non-breaking space were considered invalid.
@changelog_1174_h2
@changelog_1176_h2
#Version 1.3.157 (2011-06-25)
#Version 1.3.157 (2011-06-25)
@changelog_1175_li
@changelog_1177_li
#The syntax for CREATE TABLE ... AS SELECT ... has been changed: options such as NOT PERSISTENT are now before the query (AS SELECT), because otherwise they might be interpreted as a part of the query.
#The syntax for CREATE TABLE ... AS SELECT ... has been changed: options such as NOT PERSISTENT are now before the query (AS SELECT), because otherwise they might be interpreted as a part of the query.
@changelog_1176_li
@changelog_1178_li
#With version 1.3.156, the DB2 mode could not be used with CLOB and BLOB data.
#With version 1.3.156, the DB2 mode could not be used with CLOB and BLOB data.
@changelog_1177_li
@changelog_1179_li
#When upgrading from an older 1.3.x version to version 1.3.156, CLOB and BLOB data was lost in many cases.
#When upgrading from an older 1.3.x version to version 1.3.156, CLOB and BLOB data was lost in many cases.
@changelog_1178_li
@changelog_1180_li
#The optimization for COUNT(..) on columns that are not nullable was also used for COUNT(DISTINCT ..), which is incorrect.
#The optimization for COUNT(..) on columns that are not nullable was also used for COUNT(DISTINCT ..), which is incorrect.
@changelog_1179_li
@changelog_1181_li
#PgServer: non-admin users could not open a database.
#PgServer: non-admin users could not open a database.
@changelog_1180_li
@changelog_1182_li
#Non-admin users could not open a database using a mode (MODE=xxx) if the database was already open, even if the mode matched.
#Non-admin users could not open a database using a mode (MODE=xxx) if the database was already open, even if the mode matched.
@changelog_1181_li
@changelog_1183_li
#The SQL state of the following exceptions has been changed: From 90009, 90010, 90011 to 22007: "Cannot parse DATE/TIME/TIMESTAMP constant ...".
#The SQL state of the following exceptions has been changed: From 90009, 90010, 90011 to 22007: "Cannot parse DATE/TIME/TIMESTAMP constant ...".
@changelog_1182_li
@changelog_1184_li
#There is a problem when opening a database file in a timezone that has different daylight saving rules: the time part of dates where the daylight saving doesn't match will differ. This is not a problem within regions that use the same rules (such as, within USA, or within Europe), even if the timezone itself is different. As a workaround, export the database to a SQL script using the old timezone, and create a new database in the new timezone. The same problem occurs when accessing a database over TCP/IP if the client and server timezones use different rules, if an old server or client is used.
#There is a problem when opening a database file in a timezone that has different daylight saving rules: the time part of dates where the daylight saving doesn't match will differ. This is not a problem within regions that use the same rules (such as, within USA, or within Europe), even if the timezone itself is different. As a workaround, export the database to a SQL script using the old timezone, and create a new database in the new timezone. The same problem occurs when accessing a database over TCP/IP if the client and server timezones use different rules, if an old server or client is used.
@@ -543,187 +543,189 @@ build_1111_li=The rail images (one straight, four junctions, two turns) are gene
...
@@ -543,187 +543,189 @@ build_1111_li=The rail images (one straight, four junctions, two turns) are gene
build_1112_p=\ To generate railroad diagrams for other grammars, see the package <code>org.h2.jcr</code>. This package is used to generate the SQL-2 railroad diagrams for the JCR 2.0 specification.
build_1112_p=\ To generate railroad diagrams for other grammars, see the package <code>org.h2.jcr</code>. This package is used to generate the SQL-2 railroad diagrams for the JCR 2.0 specification.
changelog_1000_h1=Change Log
changelog_1000_h1=Change Log
changelog_1001_h2=Next Version (unreleased)
changelog_1001_h2=Next Version (unreleased)
changelog_1002_li=H2 Console system tray icon\:support for Mac OS X retina displays.
changelog_1002_li=The default jar file is now compiled for Java 6.
changelog_1003_li=The CreateCluster tool could not be used if the source database contained a CLOB or BLOB. The root cause was that the TCP server did not synchronize on the session, which caused a problem when using the exclusive mode.
changelog_1003_li=The new jar file will probably not end up in the central Maven repository in the next few weeks because Sonatype has disabled automatic synchronization from SourceForge (which they call 'legacy sync' now). It will probably take some time until this is sorted out. The H2 jar files are deployed to http\://h2database.com/m2-repo/com/h2database/h2/maven-metadata.xml and http\://hsql.sourceforge.net/m2-repo/com/h2database/h2/maven-metadata.xml as usual.
changelog_1004_li=Statement.getQueryTimeout()\:only the first call to this method will query the database. If the query timeout was changed in another way than calling setQueryTimeout, this method will always return the last value. This was changed because Hibernate calls getQueryTimeout() a lot.
changelog_1004_li=A part of the documentation and the H2 Console has been changed to support the Apple retina display.
changelog_1005_li=Issue 416\:PreparedStatement.setNString throws AbstractMethodError. All implemented JDBC 4 methods that don't break compatibility with Java 5 are now included in the default jar file.
changelog_1005_li=The CreateCluster tool could not be used if the source database contained a CLOB or BLOB. The root cause was that the TCP server did not synchronize on the session, which caused a problem when using the exclusive mode.
changelog_1006_li=Issue 414\:for some functions, the parameters were evaluated twice (for example "char(nextval(..))" ran "nextval(..)" twice).
changelog_1006_li=Statement.getQueryTimeout()\:only the first call to this method will query the database. If the query timeout was changed in another way than calling setQueryTimeout, this method will always return the last value. This was changed because Hibernate calls getQueryTimeout() a lot.
changelog_1007_li=The ResultSetMetaData methods getSchemaName and getTableName could return null instead of "" (an empty string) as specified in the JDBC API.
changelog_1007_li=Issue 416\:PreparedStatement.setNString throws AbstractMethodError. All implemented JDBC 4 methods that don't break compatibility with Java 5 are now included in the default jar file.
changelog_1008_li=Added compatibility for "SET NAMES" query in MySQL compatibility mode.
changelog_1008_li=Issue 414\:for some functions, the parameters were evaluated twice (for example "char(nextval(..))" ran "nextval(..)" twice).
changelog_1009_h2=Version 1.3.168 (2012-07-13)
changelog_1009_li=The ResultSetMetaData methods getSchemaName and getTableName could return null instead of "" (an empty string) as specified in the JDBC API.
changelog_1010_li=The message "Transaction log could not be truncated" was sometimes written to the .trace.db file even if there was no problem truncating the transaction log.
changelog_1010_li=Added compatibility for "SET NAMES" query in MySQL compatibility mode.
changelog_1011_li=New system property "h2.serializeJavaObject" (default\:true) that allows to disable serializing Java objects, so that the objects compareTo and toString methods can be used.
changelog_1011_h2=Version 1.3.168 (2012-07-13)
changelog_1012_li=Dylan has translated the H2 Console tool to Korean. Thanks a lot\!
changelog_1012_li=The message "Transaction log could not be truncated" was sometimes written to the .trace.db file even if there was no problem truncating the transaction log.
changelog_1013_li=Executing the statement CREATE INDEX IF ALREADY EXISTS if the index already exists no longer fails for a read only database.
changelog_1013_li=New system property "h2.serializeJavaObject" (default\:true) that allows to disable serializing Java objects, so that the objects compareTo and toString methods can be used.
changelog_1014_li=MVCC\:concurrently updating a row could result in the row to appear deleted in the second connection, if there are multiple unique indexes (or a primary key and at least one unique index). Thanks a lot to Teruo for the patch\!
changelog_1014_li=Dylan has translated the H2 Console tool to Korean. Thanks a lot\!
changelog_1015_li=Fulltext search\:in-memory Lucene indexes are now supported.
changelog_1015_li=Executing the statement CREATE INDEX IF ALREADY EXISTS if the index already exists no longer fails for a read only database.
changelog_1016_li=Fulltext search\:UUID primary keys are now supported.
changelog_1016_li=MVCC\:concurrently updating a row could result in the row to appear deleted in the second connection, if there are multiple unique indexes (or a primary key and at least one unique index). Thanks a lot to Teruo for the patch\!
changelog_1017_li=Apache Tomcat 7.x will now longer log a warning when unloading the web application, if using a connection pool.
changelog_1017_li=Fulltext search\:in-memory Lucene indexes are now supported.
changelog_1018_li=H2 Console\:support the Midori browser (for Debian / Raspberry Pi)
changelog_1018_li=Fulltext search\:UUID primary keys are now supported.
changelog_1019_li=When opening a remote session, don't open a temporary file if the trace level is set to zero
changelog_1019_li=Apache Tomcat 7.x will now longer log a warning when unloading the web application, if using a connection pool.
changelog_1020_li=Use HMAC for authenticating remote LOB id's, removing the need for maintaining a cache, and removing the limit on the number of LOBs per result set.
changelog_1020_li=H2 Console\:support the Midori browser (for Debian / Raspberry Pi)
changelog_1021_li=H2 Console\:HTML and XML documents can now be edited in an updatable result set. There is (limited) support for editing multi-line documents.
changelog_1021_li=When opening a remote session, don't open a temporary file if the trace level is set to zero
changelog_1022_h2=Version 1.3.167 (2012-05-23)
changelog_1022_li=Use HMAC for authenticating remote LOB id's, removing the need for maintaining a cache, and removing the limit on the number of LOBs per result set.
changelog_1023_li=H2 Console\:when editing a row, an empty varchar column was replaced with a single space.
changelog_1023_li=H2 Console\:HTML and XML documents can now be edited in an updatable result set. There is (limited) support for editing multi-line documents.
changelog_1024_li=Lukas Eder has updated the jOOQ documentation.
changelog_1024_h2=Version 1.3.167 (2012-05-23)
changelog_1025_li=Some nested joins could not be executed, for example\:select * from (select * from (select * from a) a right join b b) c;
changelog_1025_li=H2 Console\:when editing a row, an empty varchar column was replaced with a single space.
changelog_1026_li=MS SQL Server compatibility\:ISNULL is now an alias for IFNULL.
changelog_1026_li=Lukas Eder has updated the jOOQ documentation.
changelog_1027_li=Terrence Huang has completed the translation of the H2 Console tool to Chinese. Thanks a lot\!
changelog_1027_li=Some nested joins could not be executed, for example\:select * from (select * from (select * from a) a right join b b) c;
changelog_1028_li=Server mode\:the number of CLOB / BLOB values that were cached on the server is now the maximum of\:5 times the SERVER_RESULT_SET_FETCH_SIZE (which is 100 by default), and SysProperties.SERVER_CACHED_OBJECTS.
changelog_1028_li=MS SQL Server compatibility\:ISNULL is now an alias for IFNULL.
changelog_1029_li=In the trace file, the query execution time was incorrect in some cases, specially for the statement SET TRACE_LEVEL_FILE 2.
changelog_1029_li=Terrence Huang has completed the translation of the H2 Console tool to Chinese. Thanks a lot\!
changelog_1030_li=The feature LOG_SIZE_LIMIT that was introduced in version 1.3.165 did not always work correctly (specially with regards to multithreading) and has been removed. The message "Transaction log could not be truncated" is still written to the .trace.db file if required.
changelog_1030_li=Server mode\:the number of CLOB / BLOB values that were cached on the server is now the maximum of\:5 times the SERVER_RESULT_SET_FETCH_SIZE (which is 100 by default), and SysProperties.SERVER_CACHED_OBJECTS.
changelog_1031_li=Then reading from a resource using the prefix "classpath\:", the ContextClassLoader is now used if the resource can't be read otherwise.
changelog_1031_li=In the trace file, the query execution time was incorrect in some cases, specially for the statement SET TRACE_LEVEL_FILE 2.
changelog_1032_li=DatabaseEventListener now calls setProgress whenever a statement starts and ends.
changelog_1032_li=The feature LOG_SIZE_LIMIT that was introduced in version 1.3.165 did not always work correctly (specially with regards to multithreading) and has been removed. The message "Transaction log could not be truncated" is still written to the .trace.db file if required.
changelog_1033_li=DatabaseEventListener now calls setProgress periodically while a statement is running.
changelog_1033_li=Then reading from a resource using the prefix "classpath\:", the ContextClassLoader is now used if the resource can't be read otherwise.
changelog_1034_li=The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME.
changelog_1034_li=DatabaseEventListener now calls setProgress whenever a statement starts and ends.
changelog_1035_li=Issue 378\: when using views, the wrong values were bound to a parameter in some cases.
changelog_1035_li=DatabaseEventListener now calls setProgress periodically while a statement is running.
changelog_1036_li=Terrence Huang has translated the error messages to Chinese. Thanks a lot\!
changelog_1036_li=The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME.
changelog_1037_li=TRUNC was added as an alias for TRUNCATE.
changelog_1037_li=Issue 378\: when using views, the wrong values were bound to a parameter in some cases.
changelog_1038_li=Small optimisation for accessing result values by column name.
changelog_1038_li=Terrence Huang has translated the error messages to Chinese. Thanks a lot\!
changelog_1039_li=Fix for bug in Statement.getMoreResults(int)
changelog_1039_li=TRUNC was added as an alias for TRUNCATE.
changelog_1040_li=The SCRIPT statements now supports filtering by schema and table. Thanks a lot to Jacob Qvortrup for providing the patch\!
changelog_1040_li=Small optimisation for accessing result values by column name.
changelog_1041_h2=Version 1.3.166 (2012-04-08)
changelog_1041_li=Fix for bug in Statement.getMoreResults(int)
changelog_1042_li=Indexes on column that are larger than half the page size (wide indexes) could sometimes get corrupt, resulting in an ArrayIndexOutOfBoundsException in PageBtree.getRow or "Row not found" in PageBtreeLeaf. Also, such indexes used too much disk space.
changelog_1042_li=The SCRIPT statements now supports filtering by schema and table. Thanks a lot to Jacob Qvortrup for providing the patch\!
changelog_1043_li=Server mode\:when retrieving more than 64 rows each containing a CLOB or BLOB, the error message "The object is already closed" was thrown.
changelog_1043_h2=Version 1.3.166 (2012-04-08)
changelog_1044_li=ConvertTraceFile\:the time in the trace file is now parsed as a long.
changelog_1044_li=Indexes on column that are larger than half the page size (wide indexes) could sometimes get corrupt, resulting in an ArrayIndexOutOfBoundsException in PageBtree.getRow or "Row not found" in PageBtreeLeaf. Also, such indexes used too much disk space.
changelog_1045_li=Invalid connection settings are now detected.
changelog_1045_li=Server mode\:when retrieving more than 64 rows each containing a CLOB or BLOB, the error message "The object is already closed" was thrown.
changelog_1046_li=Issue 387\:WHERE condition getting pushed into sub-query with LIMIT.
changelog_1046_li=ConvertTraceFile\:the time in the trace file is now parsed as a long.
changelog_1047_h2=Version 1.3.165 (2012-03-18)
changelog_1047_li=Invalid connection settings are now detected.
changelog_1048_li=Better string representation for decimal values (for example 0.00000000 instead of 0E-26).
changelog_1048_li=Issue 387\:WHERE condition getting pushed into sub-query with LIMIT.
changelog_1049_li=Prepared statements could only be re-used if the same data types were used the second time they were executed.
changelog_1049_h2=Version 1.3.165 (2012-03-18)
changelog_1050_li=In error messages about referential constraint violation, the values are now included.
changelog_1050_li=Better string representation for decimal values (for example 0.00000000 instead of 0E-26).
changelog_1051_li=SCRIPT and RUNSCRIPT\:the password can now be set using a prepared statement. Previously, it was required to be a literal in the SQL statement.
changelog_1051_li=Prepared statements could only be re-used if the same data types were used the second time they were executed.
changelog_1052_li=MySQL compatibility\:SUBSTR with a negative start index now works like MySQL.
changelog_1052_li=In error messages about referential constraint violation, the values are now included.
changelog_1053_li=When enabling autocommit, the transaction is now committed (as required by the JDBC API).
changelog_1053_li=SCRIPT and RUNSCRIPT\:the password can now be set using a prepared statement. Previously, it was required to be a literal in the SQL statement.
changelog_1054_li=The shell script <code>h2.sh</code> did not work with spaces in the path. It also works now with quoted spaces in the argument list. Thanks a lot to Shimizu Fumiyuki for the patch\!
changelog_1054_li=MySQL compatibility\:SUBSTR with a negative start index now works like MySQL.
changelog_1055_li=If the transaction log could not be truncated because of an uncommitted transaction, now "Transaction log could not be truncated" is written to the .trace.db file. Before, the database file was growing and it was hard to find out what the root cause was. To avoid the database file from growing, a new feature to automatically rollback the oldest transaction is available now. To enable it, append ;LOG_SIZE_LIMIT\=32 to the database URL (in that case, the oldest session is rolled back if the transaction log is 32 MB).
changelog_1055_li=When enabling autocommit, the transaction is now committed (as required by the JDBC API).
changelog_1056_li=ALTER TABLE ADD can now add more than one column at a time.
changelog_1056_li=The shell script <code>h2.sh</code> did not work with spaces in the path. It also works now with quoted spaces in the argument list. Thanks a lot to Shimizu Fumiyuki for the patch\!
changelog_1057_li=Issue 380\:ALTER TABLE ADD FOREIGN KEY with an explicit index didn't verify the index can be used, which would lead to a NullPointerException later on.
changelog_1057_li=If the transaction log could not be truncated because of an uncommitted transaction, now "Transaction log could not be truncated" is written to the .trace.db file. Before, the database file was growing and it was hard to find out what the root cause was. To avoid the database file from growing, a new feature to automatically rollback the oldest transaction is available now. To enable it, append ;LOG_SIZE_LIMIT\=32 to the database URL (in that case, the oldest session is rolled back if the transaction log is 32 MB).
changelog_1058_li=Issue 384\:the wrong kind of exception (NullPointerException) was thrown in a UNION query with an incorrect ORDER BY expression.
changelog_1058_li=ALTER TABLE ADD can now add more than one column at a time.
changelog_1059_li=Issue 362\:support LIMIT in UPDATE statements.
changelog_1059_li=Issue 380\:ALTER TABLE ADD FOREIGN KEY with an explicit index didn't verify the index can be used, which would lead to a NullPointerException later on.
changelog_1060_li=Browser\:if no default browser is set, Google Chrome is now used if available. If not available, then Konqueror, Netscape, or Opera is used if available (as before).
changelog_1060_li=Issue 384\:the wrong kind of exception (NullPointerException) was thrown in a UNION query with an incorrect ORDER BY expression.
changelog_1061_li=CSV tool\:new feature to disable writing the column header (option writeColumnHeader).
changelog_1061_li=Issue 362\:support LIMIT in UPDATE statements.
changelog_1062_li=CSV tool\:new feature to preserve the case sensitivity of column names (option caseSensitiveColumnNames).
changelog_1062_li=Browser\:if no default browser is set, Google Chrome is now used if available. If not available, then Konqueror, Netscape, or Opera is used if available (as before).
changelog_1063_li=PostgreSQL compatibility\:LOG(x) is base 10 in the PostgreSQL mode.
changelog_1063_li=CSV tool\:new feature to disable writing the column header (option writeColumnHeader).
changelog_1064_h2=Version 1.3.164 (2012-02-03)
changelog_1064_li=CSV tool\:new feature to preserve the case sensitivity of column names (option caseSensitiveColumnNames).
changelog_1065_li=New built-in function ARRAY_CONTAINS.
changelog_1065_li=PostgreSQL compatibility\:LOG(x) is base 10 in the PostgreSQL mode.
changelog_1066_li=Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
changelog_1066_h2=Version 1.3.164 (2012-02-03)
changelog_1067_li=Trying to convert a VARCHAR to UUID will now fail if the text contains a character that is not a hex digit, '-', or not a whitespace.
changelog_1067_li=New built-in function ARRAY_CONTAINS.
changelog_1068_li=TriggerAdapter\:in "before" triggers, values can be changed using the ResultSet.updateX methods.
changelog_1068_li=Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
changelog_1069_li=Creating a table with column data type NULL now works (even if not very useful).
changelog_1069_li=Trying to convert a VARCHAR to UUID will now fail if the text contains a character that is not a hex digit, '-', or not a whitespace.
changelog_1070_li=ALTER TABLE ALTER COLUMN no longer copies the data for widening conversions (for example if only the precision was increased) unless necessary.
changelog_1070_li=TriggerAdapter\:in "before" triggers, values can be changed using the ResultSet.updateX methods.
changelog_1071_li=Multi-threaded kernel\:concurrently running an online backup and updating the database resulted in a broken (transactionally incorrect) backup file in some cases.
changelog_1071_li=Creating a table with column data type NULL now works (even if not very useful).
changelog_1072_li=The script created by SCRIPT DROP did not always work if multiple views existed that depend on each other.
changelog_1072_li=ALTER TABLE ALTER COLUMN no longer copies the data for widening conversions (for example if only the precision was increased) unless necessary.
changelog_1073_li=MathUtils.getSecureRandom could log a warning to System.err in case the /dev/random is very slow, and the System.getProperties().toString() returned a string larger than 64 KB.
changelog_1073_li=Multi-threaded kernel\:concurrently running an online backup and updating the database resulted in a broken (transactionally incorrect) backup file in some cases.
changelog_1074_li=The database file locking mechanism "FS" (;FILE_LOCK\=FS) did not work on Linux since version 1.3.161.
changelog_1074_li=The script created by SCRIPT DROP did not always work if multiple views existed that depend on each other.
changelog_1075_li=Sequences\:the functions NEXTVAL and CURRVAL did not work as expected when using quoted, mixed case sequence names.
changelog_1075_li=MathUtils.getSecureRandom could log a warning to System.err in case the /dev/random is very slow, and the System.getProperties().toString() returned a string larger than 64 KB.
changelog_1076_li=The constructor for Csv objects is now public, and Csv.getInstance() is now deprecated.
changelog_1076_li=The database file locking mechanism "FS" (;FILE_LOCK\=FS) did not work on Linux since version 1.3.161.
changelog_1077_li=SimpleResultSet\:updating a result set is now supported.
changelog_1077_li=Sequences\:the functions NEXTVAL and CURRVAL did not work as expected when using quoted, mixed case sequence names.
changelog_1078_li=Database URL\:extra semicolons are not supported.
changelog_1078_li=The constructor for Csv objects is now public, and Csv.getInstance() is now deprecated.
changelog_1079_h2=Version 1.3.163 (2011-12-30)
changelog_1079_li=SimpleResultSet\:updating a result set is now supported.
changelog_1080_li=On out of disk space, the database could get corrupt sometimes, if later write operations succeeded. The same problem happened on other kinds of I/O exceptions (where one or some of the writes fail, but subsequent writes succeed). Now the file is closed on the first unsuccessful write operation, so that later requests fail consistently.
changelog_1080_li=Database URL\:extra semicolons are not supported.
changelog_1081_li=DatabaseEventListener.diskSpaceIsLow() is no longer supported because it can't be guaranteed that it always works correctly.
changelog_1081_h2=Version 1.3.163 (2011-12-30)
changelog_1082_li=XMLTEXT now supports an optional parameter to escape newlines.
changelog_1082_li=On out of disk space, the database could get corrupt sometimes, if later write operations succeeded. The same problem happened on other kinds of I/O exceptions (where one or some of the writes fail, but subsequent writes succeed). Now the file is closed on the first unsuccessful write operation, so that later requests fail consistently.
changelog_1083_li=XMLNODE now support an optional parameter to disable indentation.
changelog_1083_li=DatabaseEventListener.diskSpaceIsLow() is no longer supported because it can't be guaranteed that it always works correctly.
changelog_1084_li=Csv.write now formats date, time, and timestamp values using java.sql.Date / Time / Timestamp.toString(). Previously, ResultSet.getString() was used, which didn't work well for Oracle.
changelog_1084_li=XMLTEXT now supports an optional parameter to escape newlines.
changelog_1085_li=The shell script <code>h2.sh</code> can now be run from within a different directory. Thanks a lot to Daniel Serodio for the patch\!
changelog_1085_li=XMLNODE now support an optional parameter to disable indentation.
changelog_1086_li=The page size of a persistent database can now be queries using\:select * from information_schema.settings where name \='info.PAGE_SIZE'
changelog_1086_li=Csv.write now formats date, time, and timestamp values using java.sql.Date / Time / Timestamp.toString(). Previously, ResultSet.getString() was used, which didn't work well for Oracle.
changelog_1087_li=In the server mode, BLOB and CLOB objects are no longer closed when the result set is closed (as required by the JDBC spec).
changelog_1087_li=The shell script <code>h2.sh</code> can now be run from within a different directory. Thanks a lot to Daniel Serodio for the patch\!
changelog_1088_h2=Version 1.3.162 (2011-11-26)
changelog_1088_li=The page size of a persistent database can now be queries using\:select * from information_schema.settings where name \='info.PAGE_SIZE'
changelog_1089_li=The following system properties are no longer supported\:<code>h2.allowBigDecimalExtensions</code>, <code>h2.emptyPassword</code>, <code>h2.minColumnNameMap</code>, <code>h2.returnLobObjects</code>, <code>h2.webMaxValueLength</code>.
changelog_1089_li=In the server mode, BLOB and CLOB objects are no longer closed when the result set is closed (as required by the JDBC spec).
changelog_1090_li=When using a VPN, starting a H2 server did not work (for some VPN software).
changelog_1090_h2=Version 1.3.162 (2011-11-26)
changelog_1091_li=Oracle compatibility\:support for DECODE(...).
changelog_1091_li=The following system properties are no longer supported\:<code>h2.allowBigDecimalExtensions</code>, <code>h2.emptyPassword</code>, <code>h2.minColumnNameMap</code>, <code>h2.returnLobObjects</code>, <code>h2.webMaxValueLength</code>.
changelog_1092_li=Lucene fulltext search\:creating an index is now faster if the table already contains data. Thanks a lot to Angel Leon from the FrostWire Team for the patch\!
changelog_1092_li=When using a VPN, starting a H2 server did not work (for some VPN software).
changelog_1093_li=Update statements with a column list in brackets did not work if the list only contains one column. Example\:update test set (id)\=(id).
changelog_1093_li=Oracle compatibility\:support for DECODE(...).
changelog_1094_li=Read-only databases in a zip file did not work when using the -baseDir option.
changelog_1094_li=Lucene fulltext search\:creating an index is now faster if the table already contains data. Thanks a lot to Angel Leon from the FrostWire Team for the patch\!
changelog_1095_li=Issue 334\:SimpleResultSet.getString now also works for Clob columns.
changelog_1095_li=Update statements with a column list in brackets did not work if the list only contains one column. Example\:update test set (id)\=(id).
changelog_1096_li=Subqueries with an aggregate did not always work. Example\:select (select count(*) from test where a \=t.a and b \=0) from test t group by a
changelog_1096_li=Read-only databases in a zip file did not work when using the -baseDir option.
changelog_1097_li=Server\:in some (theoretical) cases, exceptions while closing the connection were ignored.
changelog_1097_li=Issue 334\:SimpleResultSet.getString now also works for Clob columns.
changelog_1098_li=Server.createTcpServer, createPgServer, createWebServer\:invalid arguments are now detected.
changelog_1098_li=Subqueries with an aggregate did not always work. Example\:select (select count(*) from test where a \=t.a and b \=0) from test t group by a
changelog_1099_li=The selectivity of LOB columns is no longer calculated because indexes on LOB columns are not supported (however this should have little effect on performance, as the selectivity is calculated from the hash code and not the data).
changelog_1099_li=Server\:in some (theoretical) cases, exceptions while closing the connection were ignored.
changelog_1100_li=New experimental system property "h2.modifyOnWrite"\:when enabled, the database file is only modified when writing to the database. When enabled, the serialized file lock is much faster for read-only operations.
changelog_1100_li=Server.createTcpServer, createPgServer, createWebServer\:invalid arguments are now detected.
changelog_1101_li=A NullPointerException could occur in TableView.isDeterministic for invalid views.
changelog_1101_li=The selectivity of LOB columns is no longer calculated because indexes on LOB columns are not supported (however this should have little effect on performance, as the selectivity is calculated from the hash code and not the data).
changelog_1102_li=Issue 180\:when deserializing objects, the context class loader is used instead of the default class loader if the system property "h2.useThreadContextClassLoader" is set. Thanks a lot to Noah Fontes for the patch\!
changelog_1102_li=New experimental system property "h2.modifyOnWrite"\:when enabled, the database file is only modified when writing to the database. When enabled, the serialized file lock is much faster for read-only operations.
changelog_1103_li=When using the exclusive mode, LOB operations could cause the thread to block. This also affected the CreateCluster tool (when using BLOB or CLOB data).
changelog_1103_li=A NullPointerException could occur in TableView.isDeterministic for invalid views.
changelog_1104_li=The optimization for "group by" was not working correctly if the group by column was aliased in the select list.
changelog_1104_li=Issue 180\:when deserializing objects, the context class loader is used instead of the default class loader if the system property "h2.useThreadContextClassLoader" is set. Thanks a lot to Noah Fontes for the patch\!
changelog_1105_li=Issue 326\:improved support for case sensitive (mixed case) identifiers without quotes when using DATABASE_TO_UPPER\=FALSE.
changelog_1105_li=When using the exclusive mode, LOB operations could cause the thread to block. This also affected the CreateCluster tool (when using BLOB or CLOB data).
changelog_1106_h2=Version 1.3.161 (2011-10-28)
changelog_1106_li=The optimization for "group by" was not working correctly if the group by column was aliased in the select list.
changelog_1107_li=Issue 351\:MySQL mode\:can not create a table with the column "KEY", and can not open databases where such a table already exists.
changelog_1107_li=Issue 326\:improved support for case sensitive (mixed case) identifiers without quotes when using DATABASE_TO_UPPER\=FALSE.
changelog_1108_li=TCP server\:when using the trace option ("-trace"), the trace output contained unnecessary stack traces when stopping the server.
changelog_1108_h2=Version 1.3.161 (2011-10-28)
changelog_1109_li=Issue 354\:when using the multi-threaded kernel option, and multiple threads concurrently prepared SQL statements that use the same view or the same index of a view, then in some cases an infinite loop could occur.
changelog_1109_li=Issue 351\:MySQL mode\:can not create a table with the column "KEY", and can not open databases where such a table already exists.
changelog_1110_li=Issue 350\:when using instead of triggers, executeUpdate for delete operations always returned 0.
changelog_1110_li=TCP server\:when using the trace option ("-trace"), the trace output contained unnecessary stack traces when stopping the server.
changelog_1111_li=Some timestamps with timezone were not converted correctly. For example, in the PST timezone, the timestamp 2011-10-26 08\:00\:00Z was converted to 2011-10-25 25\:00\:00 instead of 2011-10-26 01\:00\:00. Depending on the database operation, this caused subsequent error.
changelog_1111_li=Issue 354\:when using the multi-threaded kernel option, and multiple threads concurrently prepared SQL statements that use the same view or the same index of a view, then in some cases an infinite loop could occur.
changelog_1112_li=Sequences with cache size smaller than 0 did not work correctly.
changelog_1112_li=Issue 350\:when using instead of triggers, executeUpdate for delete operations always returned 0.
changelog_1113_li=Issue 356\:for Blob objects, InputStream.skip() returned 0, causing EOFException in Blob.getBytes(.., ..).
changelog_1113_li=Some timestamps with timezone were not converted correctly. For example, in the PST timezone, the timestamp 2011-10-26 08\:00\:00Z was converted to 2011-10-25 25\:00\:00 instead of 2011-10-26 01\:00\:00. Depending on the database operation, this caused subsequent error.
changelog_1114_li=Updatable result sets\:if the value is not set when inserting a new row, the default value is now used (the same behavior as MySQL, PostgreSQL, and Apache Derby) instead of NULL.
changelog_1114_li=Sequences with cache size smaller than 0 did not work correctly.
changelog_1115_li=Conditions of the form IN(SELECT ...) where slow and increased the database size if the subquery result size was larger then the configured MAX_MEMORY_ROWS.
changelog_1115_li=Issue 356\:for Blob objects, InputStream.skip() returned 0, causing EOFException in Blob.getBytes(.., ..).
changelog_1116_li=Issue 347\:the RunScript and Shell tools now ignore empty statements.
changelog_1116_li=Updatable result sets\:if the value is not set when inserting a new row, the default value is now used (the same behavior as MySQL, PostgreSQL, and Apache Derby) instead of NULL.
changelog_1117_li=Issue 246\:improved error message for data conversion problems.
changelog_1117_li=Conditions of the form IN(SELECT ...) where slow and increased the database size if the subquery result size was larger then the configured MAX_MEMORY_ROWS.
changelog_1118_li=Issue 344\:the build now supports a custom Maven repository location.
changelog_1118_li=Issue 347\:the RunScript and Shell tools now ignore empty statements.
changelog_1119_li=Issue 334\:Java functions that return CLOB or BLOB objects could not be used as tables.
changelog_1119_li=Issue 246\:improved error message for data conversion problems.
changelog_1120_li=SimpleResultSet now supports getColumnTypeName and getColumnClassName.
changelog_1120_li=Issue 344\:the build now supports a custom Maven repository location.
changelog_1121_li=SimpleResultSet now has minimal BLOB and CLOB support.
changelog_1121_li=Issue 334\:Java functions that return CLOB or BLOB objects could not be used as tables.
changelog_1122_li=Improved performance for large databases (many GB), and databases with a small page size.
changelog_1122_li=SimpleResultSet now supports getColumnTypeName and getColumnClassName.
changelog_1123_li=The Polish translation has been improved by Jaros&\#322;aw Kokoci&\#324;ski.
changelog_1123_li=SimpleResultSet now has minimal BLOB and CLOB support.
changelog_1124_li=When using the built-in connection pool, after calling the "shutdown" SQL statement, a warning was written to the .trace.db file about an unclosed connection.
changelog_1124_li=Improved performance for large databases (many GB), and databases with a small page size.
changelog_1125_li=Improved compatibility for "fetch first / next row(s)". Thanks a lot to litailang for the patch\!
changelog_1125_li=The Polish translation has been improved by Jaros&\#322;aw Kokoci&\#324;ski.
changelog_1126_li=Improved compatibility with the Java 7 FileSystem abstraction.
changelog_1126_li=When using the built-in connection pool, after calling the "shutdown" SQL statement, a warning was written to the .trace.db file about an unclosed connection.
changelog_1127_h2=Version 1.3.160 (2011-09-11)
changelog_1127_li=Improved compatibility for "fetch first / next row(s)". Thanks a lot to litailang for the patch\!
changelog_1128_li=Computed columns could not refer to itself.
changelog_1128_li=Improved compatibility with the Java 7 FileSystem abstraction.
changelog_1129_li=Issue 340\:Comparison with "x \=all(select ...)" or similar in a view or subquery that was used as a table returned the wrong result.
changelog_1129_h2=Version 1.3.160 (2011-09-11)
changelog_1130_li=Comparison with "x \=all(select ...)" or similar returned the wrong result for some cases (for example if the subquery returned no rows, or multiple rows with the same value, or null, or if x was null).
changelog_1130_li=Computed columns could not refer to itself.
changelog_1131_li=Issue 335\:Could not run DROP ALL OBJECTS DELETE FILES on older databases with CLOB or BLOB data. The problem was that the metadata table was not locked in some cases, so that a rollback could result in a corrupt database in a database if the lob storage was upgraded.
changelog_1131_li=Issue 340\:Comparison with "x \=all(select ...)" or similar in a view or subquery that was used as a table returned the wrong result.
changelog_1132_li=Source code switching using //\#\#has been simplified. The Java 1.5 tag has been removed because is no longer needed.
changelog_1132_li=Comparison with "x \=all(select ...)" or similar returned the wrong result for some cases (for example if the subquery returned no rows, or multiple rows with the same value, or null, or if x was null).
changelog_1133_li=The JDBC methods PreparedStatement.setTimestamp, setTime, and setDate with a calendar, and the methods ResultSet.getTimestamp, getTime, and getDate with a calendar converted the value in the wrong way, so that for some timestamps the converted value was wrong (where summertime starts, one hour per year).
changelog_1133_li=Issue 335\:Could not run DROP ALL OBJECTS DELETE FILES on older databases with CLOB or BLOB data. The problem was that the metadata table was not locked in some cases, so that a rollback could result in a corrupt database in a database if the lob storage was upgraded.
changelog_1134_li=Invalid tables names in 'order by' columns were not detected in some cases. Example\:select x from dual order by y.x
changelog_1134_li=Source code switching using //\#\#has been simplified. The Java 1.5 tag has been removed because is no longer needed.
changelog_1135_li=Issue 329\:CASE expression\:data type problem is not detected.
changelog_1135_li=The JDBC methods PreparedStatement.setTimestamp, setTime, and setDate with a calendar, and the methods ResultSet.getTimestamp, getTime, and getDate with a calendar converted the value in the wrong way, so that for some timestamps the converted value was wrong (where summertime starts, one hour per year).
changelog_1136_li=Issue 311\:File lock mode serialized\:selecting the next value from a sequence didn't work after a pause, because the database thought this is a read-only operation.
changelog_1136_li=Invalid tables names in 'order by' columns were not detected in some cases. Example\:select x from dual order by y.x
changelog_1137_h2=Version 1.3.159 (2011-08-13)
changelog_1137_li=Issue 329\:CASE expression\:data type problem is not detected.
changelog_1138_li=Creating a temporary table with the option 'transactional' will now also create the indexes in transactional mode, if the indexes are included in the 'create table' statement as follows\:"create local temporary table temp(id int primary key, name varchar, constraint x index(name)) transactional".
changelog_1138_li=Issue 311\:File lock mode serialized\:selecting the next value from a sequence didn't work after a pause, because the database thought this is a read-only operation.
changelog_1139_li=The database file size grows now 35%, but at most 256 MB at a time.
changelog_1139_h2=Version 1.3.159 (2011-08-13)
changelog_1140_li=Improved error message on network configuration problems.
changelog_1140_li=Creating a temporary table with the option 'transactional' will now also create the indexes in transactional mode, if the indexes are included in the 'create table' statement as follows\:"create local temporary table temp(id int primary key, name varchar, constraint x index(name)) transactional".
changelog_1141_li=The build now support an offline build using ./build.sh offline. This will list the required dependencies if jar files are missing.
changelog_1141_li=The database file size grows now 35%, but at most 256 MB at a time.
changelog_1142_li=The BLOB / CLOB data was dropped a little bit before the table was dropped. This could cause "lob not found" errors when the process was killed while a table was dropped.
changelog_1142_li=Improved error message on network configuration problems.
changelog_1143_li="group_concat(distinct ...)"did not work correctly in a view or subquery (the 'distinct' was lost). Example\:select * from (select group_concat(distinct 1) from system_range(1, 3));
changelog_1143_li=The build now support an offline build using ./build.sh offline. This will list the required dependencies if jar files are missing.
changelog_1144_li=Database URLs can now be re-mapped to another URL using the system property "h2.urlMap", which points to a properties file with database URL mappings.
changelog_1144_li=The BLOB / CLOB data was dropped a little bit before the table was dropped. This could cause "lob not found" errors when the process was killed while a table was dropped.
changelog_1145_li=When using InputStream.skip, trying to read past the end of a BLOB failed with the exception "IO Exception\:Missing lob entry\:..." [90028-...].
changelog_1145_li="group_concat(distinct ...)"did not work correctly in a view or subquery (the 'distinct' was lost). Example\:select * from (select group_concat(distinct 1) from system_range(1, 3));
changelog_1146_li=The in-memory file system "memFS\:" now has limited support for directories.
changelog_1146_li=Database URLs can now be re-mapped to another URL using the system property "h2.urlMap", which points to a properties file with database URL mappings.
changelog_1147_li=To test recovery, append ;RECOVER_TEST\=64 to the database URL. This will simulate an application crash after each 64 writes to the database file. A log file named databaseName.h2.db.log is created that lists the operations. The recovery is tested using an in-memory file system, that means it may require a larger heap setting.
changelog_1147_li=When using InputStream.skip, trying to read past the end of a BLOB failed with the exception "IO Exception\:Missing lob entry\:..." [90028-...].
changelog_1148_li=Converting a hex string to a byte array is now faster.
changelog_1148_li=The in-memory file system "memFS\:" now has limited support for directories.
changelog_1149_li=The SQL statement "shutdown defrag" could corrupt the database if the process was killed while the shutdown was in progress. The same problem could occur when the database setting "defrag_always" was used.
changelog_1149_li=To test recovery, append ;RECOVER_TEST\=64 to the database URL. This will simulate an application crash after each 64 writes to the database file. A log file named databaseName.h2.db.log is created that lists the operations. The recovery is tested using an in-memory file system, that means it may require a larger heap setting.
changelog_1150_h2=Version 1.3.158 (2011-07-17)
changelog_1150_li=Converting a hex string to a byte array is now faster.
changelog_1151_li=Fulltext search (native)\:after re-opening the connection once the fulltext index was created, a transaction rollback did not roll back the modifications in the index.
changelog_1151_li=The SQL statement "shutdown defrag" could corrupt the database if the process was killed while the shutdown was in progress. The same problem could occur when the database setting "defrag_always" was used.
changelog_1152_li=Support for ROW_NUMBER() OVER() as an alias for ROWNUM() for compatibility with PostgreSQL and Apache Derby.
changelog_1152_h2=Version 1.3.158 (2011-07-17)
changelog_1153_li=Issue 325\:a deadlock in the fulltext search could occur if the connection that was used while initializing the fulltext search was later used to query the database. This was actually not only a problem for fulltext search, but also for other triggers that used the initializing connection later on.
changelog_1153_li=Fulltext search (native)\:after re-opening the connection once the fulltext index was created, a transaction rollback did not roll back the modifications in the index.
changelog_1154_li=DATABASE_TO_UPPER\:when set to false, all identifier names (table names, column names) are case sensitive (except aggregate, built-in functions, data types, and keywords). This is for improved compatibility with MySQL and PostgreSQL.
changelog_1154_li=Support for ROW_NUMBER() OVER() as an alias for ROWNUM() for compatibility with PostgreSQL and Apache Derby.
changelog_1155_li=When upgrading from an older 1.3.x version to version 1.3.157, when using BLOB or CLOB data, the database could only be opened once.
changelog_1155_li=Issue 325\:a deadlock in the fulltext search could occur if the connection that was used while initializing the fulltext search was later used to query the database. This was actually not only a problem for fulltext search, but also for other triggers that used the initializing connection later on.
changelog_1156_li=SUM on a boolean expression will now count the number of 'true' rows.
changelog_1156_li=DATABASE_TO_UPPER\:when set to false, all identifier names (table names, column names) are case sensitive (except aggregate, built-in functions, data types, and keywords). This is for improved compatibility with MySQL and PostgreSQL.
changelog_1157_li=Simplified test cases using assertThrows(...).
changelog_1157_li=When upgrading from an older 1.3.x version to version 1.3.157, when using BLOB or CLOB data, the database could only be opened once.
changelog_1158_li=A Java function that returns a result set that was generated using the provided connection could cause an internal error in some cases. Now such result sets are copied early on.
changelog_1158_li=SUM on a boolean expression will now count the number of 'true' rows.
changelog_1159_li=Data type RESULT_SET\:information_schema.function_aliases returned type 0; now type -10 is returned (the same as Oracle\:OracleTypes.CURSOR \=-10).
changelog_1159_li=Simplified test cases using assertThrows(...).
changelog_1160_li=Data type RESULT_SET\:tables with columns of type RESULT_SET could be created, but no data could be persisted in this column.
changelog_1160_li=A Java function that returns a result set that was generated using the provided connection could cause an internal error in some cases. Now such result sets are copied early on.
changelog_1161_li=H2 Console\:improved system tray icon for Mac OS X (transparent background).
changelog_1161_li=Data type RESULT_SET\:information_schema.function_aliases returned type 0; now type -10 is returned (the same as Oracle\:OracleTypes.CURSOR \=-10).
changelog_1162_li=String.toUpperCase() was used a few places, which is problematic when using the Turkish locale. The method has been replaced with toUpperCase(Locale.ENGLISH) to solve such problems.
changelog_1162_li=Data type RESULT_SET\:tables with columns of type RESULT_SET could be created, but no data could be persisted in this column.
changelog_1163_li=Shell tool\:the built-in command "distinct" has been removed (use the SQL statements "show tables" / "show columns from tableName" instead). The result set formatting has been improved.
changelog_1163_li=H2 Console\:improved system tray icon for Mac OS X (transparent background).
changelog_1164_li=MERGE\:if a unique key was violated (but not the primary key or the key columns of the merge itself), the wrong exception was thrown.
changelog_1164_li=String.toUpperCase() was used a few places, which is problematic when using the Turkish locale. The method has been replaced with toUpperCase(Locale.ENGLISH) to solve such problems.
changelog_1165_li=IBM DB2 and Apache Derby compatibility\:support the pseudo-table SYSIBM.SYSDUMMY1.
changelog_1165_li=Shell tool\:the built-in command "distinct" has been removed (use the SQL statements "show tables" / "show columns from tableName" instead). The result set formatting has been improved.
changelog_1166_li=ROWNUM() did not work in combination with IN(..). The following query did not work as expected\:select * from (select rownum r from test) where r in (1, 2).
changelog_1166_li=MERGE\:if a unique key was violated (but not the primary key or the key columns of the merge itself), the wrong exception was thrown.
changelog_1167_li=H2 Console autocomplete\:the autocomplete feature didn't support quoted names.
changelog_1167_li=IBM DB2 and Apache Derby compatibility\:support the pseudo-table SYSIBM.SYSDUMMY1.
changelog_1168_li=It is now longer allowed to create an index on a CLOB or BLOB column (except for in-memory databases or indexes), because recovery doesn't work on such columns. Fulltext indexes on such column are still supported of course.
changelog_1168_li=ROWNUM() did not work in combination with IN(..). The following query did not work as expected\:select * from (select rownum r from test) where r in (1, 2).
changelog_1169_li=The PUBLIC schema could be renamed, which could result in a database that can't be opened normally. Now it can no longer be renamed. The schema INFORMATION_SCHEMA can also no longer be renamed.
changelog_1169_li=H2 Console autocomplete\:the autocomplete feature didn't support quoted names.
changelog_1170_li=Server mode\:the problem with server and client using different timezones with different daylight saving rules has been solved (this only applies when both the client and the server use this or a newer version).
changelog_1170_li=It is now longer allowed to create an index on a CLOB or BLOB column (except for in-memory databases or indexes), because recovery doesn't work on such columns. Fulltext indexes on such column are still supported of course.
changelog_1171_li=There is a new system property "h2.storeLocalTime" to avoid problems opening a database file in a timezone that has different daylight saving rules (see also below).
changelog_1171_li=The PUBLIC schema could be renamed, which could result in a database that can't be opened normally. Now it can no longer be renamed. The schema INFORMATION_SCHEMA can also no longer be renamed.
changelog_1172_li=Date, time, and timestamp data type processing has been re-implemented. Time now supports nanoseconds resolution and now now supports a wider range (negative and large values), similar to PostgreSQL.
changelog_1172_li=Server mode\:the problem with server and client using different timezones with different daylight saving rules has been solved (this only applies when both the client and the server use this or a newer version).
changelog_1173_li=SQL statements with a non-breaking space were considered invalid.
changelog_1173_li=There is a new system property "h2.storeLocalTime" to avoid problems opening a database file in a timezone that has different daylight saving rules (see also below).
changelog_1174_h2=Version 1.3.157 (2011-06-25)
changelog_1174_li=Date, time, and timestamp data type processing has been re-implemented. Time now supports nanoseconds resolution and now now supports a wider range (negative and large values), similar to PostgreSQL.
changelog_1175_li=The syntax for CREATE TABLE ... AS SELECT ... has been changed\:options such as NOT PERSISTENT are now before the query (AS SELECT), because otherwise they might be interpreted as a part of the query.
changelog_1175_li=SQL statements with a non-breaking space were considered invalid.
changelog_1176_li=With version 1.3.156, the DB2 mode could not be used with CLOB and BLOB data.
changelog_1176_h2=Version 1.3.157 (2011-06-25)
changelog_1177_li=When upgrading from an older 1.3.x version to version 1.3.156, CLOB and BLOB data was lost in many cases.
changelog_1177_li=The syntax for CREATE TABLE ... AS SELECT ... has been changed\:options such as NOT PERSISTENT are now before the query (AS SELECT), because otherwise they might be interpreted as a part of the query.
changelog_1178_li=The optimization for COUNT(..) on columns that are not nullable was also used for COUNT(DISTINCT ..), which is incorrect.
changelog_1178_li=With version 1.3.156, the DB2 mode could not be used with CLOB and BLOB data.
changelog_1179_li=PgServer\:non-admin users could not open a database.
changelog_1179_li=When upgrading from an older 1.3.x version to version 1.3.156, CLOB and BLOB data was lost in many cases.
changelog_1180_li=Non-admin users could not open a database using a mode (MODE\=xxx) if the database was already open, even if the mode matched.
changelog_1180_li=The optimization for COUNT(..) on columns that are not nullable was also used for COUNT(DISTINCT ..), which is incorrect.
changelog_1181_li=The SQL state of the following exceptions has been changed\:From 90009, 90010, 90011 to 22007\:"Cannot parse DATE/TIME/TIMESTAMP constant ...".
changelog_1181_li=PgServer\:non-admin users could not open a database.
changelog_1182_li=There is a problem when opening a database file in a timezone that has different daylight saving rules\:the time part of dates where the daylight saving doesn't match will differ. This is not a problem within regions that use the same rules (such as, within USA, or within Europe), even if the timezone itself is different. As a workaround, export the database to a SQL script using the old timezone, and create a new database in the new timezone. The same problem occurs when accessing a database over TCP/IP if the client and server timezones use different rules, if an old server or client is used.
changelog_1182_li=Non-admin users could not open a database using a mode (MODE\=xxx) if the database was already open, even if the mode matched.
changelog_1183_li=The SQL state of the following exceptions has been changed\:From 90009, 90010, 90011 to 22007\:"Cannot parse DATE/TIME/TIMESTAMP constant ...".
changelog_1184_li=There is a problem when opening a database file in a timezone that has different daylight saving rules\:the time part of dates where the daylight saving doesn't match will differ. This is not a problem within regions that use the same rules (such as, within USA, or within Europe), even if the timezone itself is different. As a workaround, export the database to a SQL script using the old timezone, and create a new database in the new timezone. The same problem occurs when accessing a database over TCP/IP if the client and server timezones use different rules, if an old server or client is used.
