@@ -1705,466 +1705,484 @@ Supporting dropping an index for Lucene full-text indexes.
...
@@ -1705,466 +1705,484 @@ Supporting dropping an index for Lucene full-text indexes.
@changelog_1024_li
@changelog_1024_li
Optimized performance for SELECT ... ORDER BY X LIMIT Y OFFSET Z queries for in-memory databases using partial sort (by Sergi Vladykin).
Optimized performance for SELECT ... ORDER BY X LIMIT Y OFFSET Z queries for in-memory databases using partial sort (by Sergi Vladykin).
@changelog_1025_h2
@changelog_1025_li
Version 1.3.170 (2012-11-30)
Experimental off-heap memory storage engine "nioMemFS:" and "nioMemLZF:", suggestion from Mark Addleman.
@changelog_1026_li
@changelog_1026_li
Issue 407: The TriggerAdapter didn't work with CLOB and BLOB columns.
Issue 438: JdbcDatabaseMetaData.getSchemas() is no longer supported as of 1.3.169.
@changelog_1027_li
@changelog_1027_li
PostgreSQL compatibility: support for data types BIGSERIAL and SERIAL as an alias for AUTO_INCREMENT.
MySQL compatibility: support for ALTER TABLE tableName MODIFY [COLUMN] columnName columnDef. Patch from Ville Koskela.
@changelog_1028_li
@changelog_1028_li
Issue 417: H2 Console: the web session timeout didn't work, resulting in a memory leak. This was only a problem if the H2 Console was run for a long time and many sessions were opened.
Issue 404: SHOW COLUMNS FROM tableName does not work with ALLOW_LITERALS=NUMBERS.
@changelog_1029_li
@changelog_1029_li
Issue 412: Running the Server tool with just the option "-browser" will now log a warning.
Throw an explicit error to make it clear we don't support the TRIGGER combination of SELECT and FOR EACH ROW.
@changelog_1030_li
@changelog_1030_li
Issue 439: Utils.sortTopN does not handle single-element arrays.
@changelog_1031_h2
Version 1.3.170 (2012-11-30)
@changelog_1032_li
Issue 407: The TriggerAdapter didn't work with CLOB and BLOB columns.
@changelog_1033_li
PostgreSQL compatibility: support for data types BIGSERIAL and SERIAL as an alias for AUTO_INCREMENT.
@changelog_1034_li
Issue 417: H2 Console: the web session timeout didn't work, resulting in a memory leak. This was only a problem if the H2 Console was run for a long time and many sessions were opened.
@changelog_1035_li
Issue 412: Running the Server tool with just the option "-browser" will now log a warning.
@changelog_1036_li
Issue 411: CloseWatcher registration was not concurrency-safe.
Issue 411: CloseWatcher registration was not concurrency-safe.
@changelog_1031_li
@changelog_1037_li
MySQL compatibility: support for CONCAT_WS. Thanks a lot to litailang for the patch!
MySQL compatibility: support for CONCAT_WS. Thanks a lot to litailang for the patch!
@changelog_1032_li
@changelog_1038_li
PostgreSQL compatibility: support for EXTRACT(WEEK FROM dateColumn). Thanks to Prashant Bhat for the patch!
PostgreSQL compatibility: support for EXTRACT(WEEK FROM dateColumn). Thanks to Prashant Bhat for the patch!
@changelog_1033_li
@changelog_1039_li
Fix for a bug where we would sometimes use the wrong unique constraint to validate foreign key constraints.
Fix for a bug where we would sometimes use the wrong unique constraint to validate foreign key constraints.
@changelog_1034_li
@changelog_1040_li
Support BOM at the beginning of files for the RUNSCRIPT command
Support BOM at the beginning of files for the RUNSCRIPT command
@changelog_1035_li
@changelog_1041_li
Fix in calling SET @X = IDENTITY() where it would return NULL incorrectly
Fix in calling SET @X = IDENTITY() where it would return NULL incorrectly
@changelog_1036_li
@changelog_1042_li
Fix ABBA deadlock between adding a constraint and the H2-Log-Writer thread.
Fix ABBA deadlock between adding a constraint and the H2-Log-Writer thread.
@changelog_1037_li
@changelog_1043_li
Optimize IN(...) queries where the values are constant and of the same type.
Optimize IN(...) queries where the values are constant and of the same type.
@changelog_1038_li
@changelog_1044_li
Restore tool: the parameter "quiet" was not used and is now removed.
Restore tool: the parameter "quiet" was not used and is now removed.
@changelog_1039_li
@changelog_1045_li
Fix ConcurrentModificationException when creating tables and executing SHOW TABLES in parallel. Reported by Viktor Voytovych.
Fix ConcurrentModificationException when creating tables and executing SHOW TABLES in parallel. Reported by Viktor Voytovych.
@changelog_1040_li
@changelog_1046_li
Serialization is now pluggable using the system property "h2.javaObjectSerializer". Thanks to Sergi Vladykin for the patch!
Serialization is now pluggable using the system property "h2.javaObjectSerializer". Thanks to Sergi Vladykin for the patch!
@changelog_1041_h2
@changelog_1047_h2
Version 1.3.169 (2012-09-09)
Version 1.3.169 (2012-09-09)
@changelog_1042_li
@changelog_1048_li
The default jar file is now compiled for Java 6.
The default jar file is now compiled for Java 6.
@changelog_1043_li
@changelog_1049_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.
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_1044_li
@changelog_1050_li
A part of the documentation and the H2 Console has been changed to support the Apple retina display.
A part of the documentation and the H2 Console has been changed to support the Apple retina display.
@changelog_1045_li
@changelog_1051_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 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_1046_li
@changelog_1052_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.
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_1047_li
@changelog_1053_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.
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_1048_li
@changelog_1054_li
Issue 414: for some functions, the parameters were evaluated twice (for example "char(nextval(..))" ran "nextval(..)" twice).
Issue 414: for some functions, the parameters were evaluated twice (for example "char(nextval(..))" ran "nextval(..)" twice).
@changelog_1049_li
@changelog_1055_li
The ResultSetMetaData methods getSchemaName and getTableName could return null instead of "" (an empty string) as specified in the JDBC API.
The ResultSetMetaData methods getSchemaName and getTableName could return null instead of "" (an empty string) as specified in the JDBC API.
@changelog_1050_li
@changelog_1056_li
Added compatibility for "SET NAMES" query in MySQL compatibility mode.
Added compatibility for "SET NAMES" query in MySQL compatibility mode.
@changelog_1051_h2
@changelog_1057_h2
Version 1.3.168 (2012-07-13)
Version 1.3.168 (2012-07-13)
@changelog_1052_li
@changelog_1058_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_1053_li
@changelog_1059_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_1054_li
@changelog_1060_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_1055_li
@changelog_1061_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_1056_li
@changelog_1062_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_1057_li
@changelog_1063_li
Fulltext search: in-memory Lucene indexes are now supported.
Fulltext search: in-memory Lucene indexes are now supported.
@changelog_1058_li
@changelog_1064_li
Fulltext search: UUID primary keys are now supported.
Fulltext search: UUID primary keys are now supported.
@changelog_1059_li
@changelog_1065_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_1060_li
@changelog_1066_li
H2 Console: support the Midori browser (for Debian / Raspberry Pi)
H2 Console: support the Midori browser (for Debian / Raspberry Pi)
@changelog_1061_li
@changelog_1067_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_1062_li
@changelog_1068_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_1063_li
@changelog_1069_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_1064_h2
@changelog_1070_h2
Version 1.3.167 (2012-05-23)
Version 1.3.167 (2012-05-23)
@changelog_1065_li
@changelog_1071_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_1066_li
@changelog_1072_li
Lukas Eder has updated the jOOQ documentation.
Lukas Eder has updated the jOOQ documentation.
@changelog_1067_li
@changelog_1073_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_1068_li
@changelog_1074_li
MS SQL Server compatibility: ISNULL is now an alias for IFNULL.
MS SQL Server compatibility: ISNULL is now an alias for IFNULL.
@changelog_1069_li
@changelog_1075_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_1070_li
@changelog_1076_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_1071_li
@changelog_1077_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_1072_li
@changelog_1078_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_1073_li
@changelog_1079_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_1074_li
@changelog_1080_li
DatabaseEventListener now calls setProgress whenever a statement starts and ends.
DatabaseEventListener now calls setProgress whenever a statement starts and ends.
@changelog_1075_li
@changelog_1081_li
DatabaseEventListener now calls setProgress periodically while a statement is running.
DatabaseEventListener now calls setProgress periodically while a statement is running.
@changelog_1076_li
@changelog_1082_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_1077_li
@changelog_1083_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_1078_li
@changelog_1084_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_1079_li
@changelog_1085_li
TRUNC was added as an alias for TRUNCATE.
TRUNC was added as an alias for TRUNCATE.
@changelog_1080_li
@changelog_1086_li
Small optimisation for accessing result values by column name.
Small optimisation for accessing result values by column name.
@changelog_1081_li
@changelog_1087_li
Fix for bug in Statement.getMoreResults(int)
Fix for bug in Statement.getMoreResults(int)
@changelog_1082_li
@changelog_1088_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_1083_h2
@changelog_1089_h2
Version 1.3.166 (2012-04-08)
Version 1.3.166 (2012-04-08)
@changelog_1084_li
@changelog_1090_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_1085_li
@changelog_1091_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_1086_li
@changelog_1092_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_1087_li
@changelog_1093_li
Invalid connection settings are now detected.
Invalid connection settings are now detected.
@changelog_1088_li
@changelog_1094_li
Issue 387: WHERE condition getting pushed into sub-query with LIMIT.
Issue 387: WHERE condition getting pushed into sub-query with LIMIT.
@changelog_1089_h2
@changelog_1095_h2
Version 1.3.165 (2012-03-18)
Version 1.3.165 (2012-03-18)
@changelog_1090_li
@changelog_1096_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_1091_li
@changelog_1097_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_1092_li
@changelog_1098_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_1093_li
@changelog_1099_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_1094_li
@changelog_1100_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_1095_li
@changelog_1101_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_1096_li
@changelog_1102_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_1097_li
@changelog_1103_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_1098_li
@changelog_1104_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_1099_li
@changelog_1105_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_1100_li
@changelog_1106_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_1101_li
@changelog_1107_li
Issue 362: support LIMIT in UPDATE statements.
Issue 362: support LIMIT in UPDATE statements.
@changelog_1102_li
@changelog_1108_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_1103_li
@changelog_1109_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_1104_li
@changelog_1110_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_1105_li
@changelog_1111_li
PostgreSQL compatibility: LOG(x) is base 10 in the PostgreSQL mode.
PostgreSQL compatibility: LOG(x) is base 10 in the PostgreSQL mode.
@changelog_1106_h2
@changelog_1112_h2
Version 1.3.164 (2012-02-03)
Version 1.3.164 (2012-02-03)
@changelog_1107_li
@changelog_1113_li
New built-in function ARRAY_CONTAINS.
New built-in function ARRAY_CONTAINS.
@changelog_1108_li
@changelog_1114_li
Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
@changelog_1109_li
@changelog_1115_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_1110_li
@changelog_1116_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_1111_li
@changelog_1117_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_1112_li
@changelog_1118_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_1113_li
@changelog_1119_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_1114_li
@changelog_1120_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_1115_li
@changelog_1121_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_1116_li
@changelog_1122_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_1117_li
@changelog_1123_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_1118_li
@changelog_1124_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_1119_li
@changelog_1125_li
SimpleResultSet: updating a result set is now supported.
SimpleResultSet: updating a result set is now supported.
@changelog_1120_li
@changelog_1126_li
Database URL: extra semicolons are not supported.
Database URL: extra semicolons are not supported.
@changelog_1121_h2
@changelog_1127_h2
Version 1.3.163 (2011-12-30)
Version 1.3.163 (2011-12-30)
@changelog_1122_li
@changelog_1128_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_1123_li
@changelog_1129_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_1124_li
@changelog_1130_li
XMLTEXT now supports an optional parameter to escape newlines.
XMLTEXT now supports an optional parameter to escape newlines.
@changelog_1125_li
@changelog_1131_li
XMLNODE now support an optional parameter to disable indentation.
XMLNODE now support an optional parameter to disable indentation.
@changelog_1126_li
@changelog_1132_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_1127_li
@changelog_1133_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_1128_li
@changelog_1134_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_1129_li
@changelog_1135_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_1130_h2
@changelog_1136_h2
Version 1.3.162 (2011-11-26)
Version 1.3.162 (2011-11-26)
@changelog_1131_li
@changelog_1137_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_1132_li
@changelog_1138_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_1133_li
@changelog_1139_li
Oracle compatibility: support for DECODE(...).
Oracle compatibility: support for DECODE(...).
@changelog_1134_li
@changelog_1140_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_1135_li
@changelog_1141_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_1136_li
@changelog_1142_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_1137_li
@changelog_1143_li
Issue 334: SimpleResultSet.getString now also works for Clob columns.
Issue 334: SimpleResultSet.getString now also works for Clob columns.
@changelog_1138_li
@changelog_1144_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_1139_li
@changelog_1145_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_1140_li
@changelog_1146_li
Server.createTcpServer, createPgServer, createWebServer: invalid arguments are now detected.
Server.createTcpServer, createPgServer, createWebServer: invalid arguments are now detected.
@changelog_1141_li
@changelog_1147_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_1142_li
@changelog_1148_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_1143_li
@changelog_1149_li
A NullPointerException could occur in TableView.isDeterministic for invalid views.
A NullPointerException could occur in TableView.isDeterministic for invalid views.
@changelog_1144_li
@changelog_1150_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_1145_li
@changelog_1151_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_1146_li
@changelog_1152_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_1147_li
@changelog_1153_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_1148_h2
@changelog_1154_h2
Version 1.3.161 (2011-10-28)
Version 1.3.161 (2011-10-28)
@changelog_1149_li
@changelog_1155_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_1150_li
@changelog_1156_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_1151_li
@changelog_1157_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_1152_li
@changelog_1158_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_1153_li
@changelog_1159_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_1154_li
@changelog_1160_li
Sequences with cache size smaller than 0 did not work correctly.
Sequences with cache size smaller than 0 did not work correctly.
@changelog_1155_li
@changelog_1161_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_1156_li
@changelog_1162_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_1157_li
@changelog_1163_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_1158_li
@changelog_1164_li
Issue 347: the RunScript and Shell tools now ignore empty statements.
Issue 347: the RunScript and Shell tools now ignore empty statements.
@changelog_1159_li
@changelog_1165_li
Issue 246: improved error message for data conversion problems.
Issue 246: improved error message for data conversion problems.
@changelog_1160_li
@changelog_1166_li
Issue 344: the build now supports a custom Maven repository location.
Issue 344: the build now supports a custom Maven repository location.
@changelog_1161_li
@changelog_1167_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_1162_li
@changelog_1168_li
SimpleResultSet now supports getColumnTypeName and getColumnClassName.
SimpleResultSet now supports getColumnTypeName and getColumnClassName.
@changelog_1163_li
@changelog_1169_li
SimpleResultSet now has minimal BLOB and CLOB support.
SimpleResultSet now has minimal BLOB and CLOB support.
@changelog_1164_li
@changelog_1170_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_1165_li
@changelog_1171_li
The Polish translation has been improved by Jarosław Kokociński.
The Polish translation has been improved by Jarosław Kokociński.
@changelog_1166_li
@changelog_1172_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_1167_li
@changelog_1173_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_1168_li
@changelog_1174_li
Improved compatibility with the Java 7 FileSystem abstraction.
Improved compatibility with the Java 7 FileSystem abstraction.
@changelog_1169_h2
@changelog_1175_h2
Version 1.3.160 (2011-09-11)
Version 1.3.160 (2011-09-11)
@changelog_1170_li
@changelog_1176_li
Computed columns could not refer to itself.
Computed columns could not refer to itself.
@changelog_1171_li
@changelog_1177_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_1172_li
@changelog_1178_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_1173_li
@changelog_1179_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_1174_li
@changelog_1180_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_1175_li
@changelog_1181_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_1176_li
@changelog_1182_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_1177_li
@changelog_1183_li
Issue 329: CASE expression: data type problem is not detected.
Issue 329: CASE expression: data type problem is not detected.
@changelog_1178_li
@changelog_1184_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.
#Optimized performance for SELECT ... ORDER BY X LIMIT Y OFFSET Z queries for in-memory databases using partial sort (by Sergi Vladykin).
#Optimized performance for SELECT ... ORDER BY X LIMIT Y OFFSET Z queries for in-memory databases using partial sort (by Sergi Vladykin).
@changelog_1025_h2
@changelog_1025_li
#Version 1.3.170 (2012-11-30)
#Experimental off-heap memory storage engine "nioMemFS:" and "nioMemLZF:", suggestion from Mark Addleman.
@changelog_1026_li
@changelog_1026_li
#Issue 407: The TriggerAdapter didn't work with CLOB and BLOB columns.
#Issue 438: JdbcDatabaseMetaData.getSchemas() is no longer supported as of 1.3.169.
@changelog_1027_li
@changelog_1027_li
#PostgreSQL compatibility: support for data types BIGSERIAL and SERIAL as an alias for AUTO_INCREMENT.
#MySQL compatibility: support for ALTER TABLE tableName MODIFY [COLUMN] columnName columnDef. Patch from Ville Koskela.
@changelog_1028_li
@changelog_1028_li
#Issue 417: H2 Console: the web session timeout didn't work, resulting in a memory leak. This was only a problem if the H2 Console was run for a long time and many sessions were opened.
#Issue 404: SHOW COLUMNS FROM tableName does not work with ALLOW_LITERALS=NUMBERS.
@changelog_1029_li
@changelog_1029_li
#Issue 412: Running the Server tool with just the option "-browser" will now log a warning.
#Throw an explicit error to make it clear we don't support the TRIGGER combination of SELECT and FOR EACH ROW.
@changelog_1030_li
@changelog_1030_li
#Issue 439: Utils.sortTopN does not handle single-element arrays.
@changelog_1031_h2
#Version 1.3.170 (2012-11-30)
@changelog_1032_li
#Issue 407: The TriggerAdapter didn't work with CLOB and BLOB columns.
@changelog_1033_li
#PostgreSQL compatibility: support for data types BIGSERIAL and SERIAL as an alias for AUTO_INCREMENT.
@changelog_1034_li
#Issue 417: H2 Console: the web session timeout didn't work, resulting in a memory leak. This was only a problem if the H2 Console was run for a long time and many sessions were opened.
@changelog_1035_li
#Issue 412: Running the Server tool with just the option "-browser" will now log a warning.
@changelog_1036_li
#Issue 411: CloseWatcher registration was not concurrency-safe.
#Issue 411: CloseWatcher registration was not concurrency-safe.
@changelog_1031_li
@changelog_1037_li
#MySQL compatibility: support for CONCAT_WS. Thanks a lot to litailang for the patch!
#MySQL compatibility: support for CONCAT_WS. Thanks a lot to litailang for the patch!
@changelog_1032_li
@changelog_1038_li
#PostgreSQL compatibility: support for EXTRACT(WEEK FROM dateColumn). Thanks to Prashant Bhat for the patch!
#PostgreSQL compatibility: support for EXTRACT(WEEK FROM dateColumn). Thanks to Prashant Bhat for the patch!
@changelog_1033_li
@changelog_1039_li
#Fix for a bug where we would sometimes use the wrong unique constraint to validate foreign key constraints.
#Fix for a bug where we would sometimes use the wrong unique constraint to validate foreign key constraints.
@changelog_1034_li
@changelog_1040_li
#Support BOM at the beginning of files for the RUNSCRIPT command
#Support BOM at the beginning of files for the RUNSCRIPT command
@changelog_1035_li
@changelog_1041_li
#Fix in calling SET @X = IDENTITY() where it would return NULL incorrectly
#Fix in calling SET @X = IDENTITY() where it would return NULL incorrectly
@changelog_1036_li
@changelog_1042_li
#Fix ABBA deadlock between adding a constraint and the H2-Log-Writer thread.
#Fix ABBA deadlock between adding a constraint and the H2-Log-Writer thread.
@changelog_1037_li
@changelog_1043_li
#Optimize IN(...) queries where the values are constant and of the same type.
#Optimize IN(...) queries where the values are constant and of the same type.
@changelog_1038_li
@changelog_1044_li
#Restore tool: the parameter "quiet" was not used and is now removed.
#Restore tool: the parameter "quiet" was not used and is now removed.
@changelog_1039_li
@changelog_1045_li
#Fix ConcurrentModificationException when creating tables and executing SHOW TABLES in parallel. Reported by Viktor Voytovych.
#Fix ConcurrentModificationException when creating tables and executing SHOW TABLES in parallel. Reported by Viktor Voytovych.
@changelog_1040_li
@changelog_1046_li
#Serialization is now pluggable using the system property "h2.javaObjectSerializer". Thanks to Sergi Vladykin for the patch!
#Serialization is now pluggable using the system property "h2.javaObjectSerializer". Thanks to Sergi Vladykin for the patch!
@changelog_1041_h2
@changelog_1047_h2
#Version 1.3.169 (2012-09-09)
#Version 1.3.169 (2012-09-09)
@changelog_1042_li
@changelog_1048_li
#The default jar file is now compiled for Java 6.
#The default jar file is now compiled for Java 6.
@changelog_1043_li
@changelog_1049_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.
#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_1044_li
@changelog_1050_li
#A part of the documentation and the H2 Console has been changed to support the Apple retina display.
#A part of the documentation and the H2 Console has been changed to support the Apple retina display.
@changelog_1045_li
@changelog_1051_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 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_1046_li
@changelog_1052_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.
#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_1047_li
@changelog_1053_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.
#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_1048_li
@changelog_1054_li
#Issue 414: for some functions, the parameters were evaluated twice (for example "char(nextval(..))" ran "nextval(..)" twice).
#Issue 414: for some functions, the parameters were evaluated twice (for example "char(nextval(..))" ran "nextval(..)" twice).
@changelog_1049_li
@changelog_1055_li
#The ResultSetMetaData methods getSchemaName and getTableName could return null instead of "" (an empty string) as specified in the JDBC API.
#The ResultSetMetaData methods getSchemaName and getTableName could return null instead of "" (an empty string) as specified in the JDBC API.
@changelog_1050_li
@changelog_1056_li
#Added compatibility for "SET NAMES" query in MySQL compatibility mode.
#Added compatibility for "SET NAMES" query in MySQL compatibility mode.
@changelog_1051_h2
@changelog_1057_h2
#Version 1.3.168 (2012-07-13)
#Version 1.3.168 (2012-07-13)
@changelog_1052_li
@changelog_1058_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_1053_li
@changelog_1059_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_1054_li
@changelog_1060_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_1055_li
@changelog_1061_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_1056_li
@changelog_1062_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_1057_li
@changelog_1063_li
#Fulltext search: in-memory Lucene indexes are now supported.
#Fulltext search: in-memory Lucene indexes are now supported.
@changelog_1058_li
@changelog_1064_li
#Fulltext search: UUID primary keys are now supported.
#Fulltext search: UUID primary keys are now supported.
@changelog_1059_li
@changelog_1065_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_1060_li
@changelog_1066_li
#H2 Console: support the Midori browser (for Debian / Raspberry Pi)
#H2 Console: support the Midori browser (for Debian / Raspberry Pi)
@changelog_1061_li
@changelog_1067_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_1062_li
@changelog_1068_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_1063_li
@changelog_1069_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_1064_h2
@changelog_1070_h2
#Version 1.3.167 (2012-05-23)
#Version 1.3.167 (2012-05-23)
@changelog_1065_li
@changelog_1071_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_1066_li
@changelog_1072_li
#Lukas Eder has updated the jOOQ documentation.
#Lukas Eder has updated the jOOQ documentation.
@changelog_1067_li
@changelog_1073_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_1068_li
@changelog_1074_li
#MS SQL Server compatibility: ISNULL is now an alias for IFNULL.
#MS SQL Server compatibility: ISNULL is now an alias for IFNULL.
@changelog_1069_li
@changelog_1075_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_1070_li
@changelog_1076_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_1071_li
@changelog_1077_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_1072_li
@changelog_1078_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_1073_li
@changelog_1079_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_1074_li
@changelog_1080_li
#DatabaseEventListener now calls setProgress whenever a statement starts and ends.
#DatabaseEventListener now calls setProgress whenever a statement starts and ends.
@changelog_1075_li
@changelog_1081_li
#DatabaseEventListener now calls setProgress periodically while a statement is running.
#DatabaseEventListener now calls setProgress periodically while a statement is running.
@changelog_1076_li
@changelog_1082_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_1077_li
@changelog_1083_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_1078_li
@changelog_1084_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_1079_li
@changelog_1085_li
#TRUNC was added as an alias for TRUNCATE.
#TRUNC was added as an alias for TRUNCATE.
@changelog_1080_li
@changelog_1086_li
#Small optimisation for accessing result values by column name.
#Small optimisation for accessing result values by column name.
@changelog_1081_li
@changelog_1087_li
#Fix for bug in Statement.getMoreResults(int)
#Fix for bug in Statement.getMoreResults(int)
@changelog_1082_li
@changelog_1088_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_1083_h2
@changelog_1089_h2
#Version 1.3.166 (2012-04-08)
#Version 1.3.166 (2012-04-08)
@changelog_1084_li
@changelog_1090_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_1085_li
@changelog_1091_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_1086_li
@changelog_1092_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_1087_li
@changelog_1093_li
#Invalid connection settings are now detected.
#Invalid connection settings are now detected.
@changelog_1088_li
@changelog_1094_li
#Issue 387: WHERE condition getting pushed into sub-query with LIMIT.
#Issue 387: WHERE condition getting pushed into sub-query with LIMIT.
@changelog_1089_h2
@changelog_1095_h2
#Version 1.3.165 (2012-03-18)
#Version 1.3.165 (2012-03-18)
@changelog_1090_li
@changelog_1096_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_1091_li
@changelog_1097_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_1092_li
@changelog_1098_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_1093_li
@changelog_1099_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_1094_li
@changelog_1100_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_1095_li
@changelog_1101_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_1096_li
@changelog_1102_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_1097_li
@changelog_1103_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_1098_li
@changelog_1104_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_1099_li
@changelog_1105_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_1100_li
@changelog_1106_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_1101_li
@changelog_1107_li
#Issue 362: support LIMIT in UPDATE statements.
#Issue 362: support LIMIT in UPDATE statements.
@changelog_1102_li
@changelog_1108_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_1103_li
@changelog_1109_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_1104_li
@changelog_1110_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_1105_li
@changelog_1111_li
#PostgreSQL compatibility: LOG(x) is base 10 in the PostgreSQL mode.
#PostgreSQL compatibility: LOG(x) is base 10 in the PostgreSQL mode.
@changelog_1106_h2
@changelog_1112_h2
#Version 1.3.164 (2012-02-03)
#Version 1.3.164 (2012-02-03)
@changelog_1107_li
@changelog_1113_li
#New built-in function ARRAY_CONTAINS.
#New built-in function ARRAY_CONTAINS.
@changelog_1108_li
@changelog_1114_li
#Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
#Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
@changelog_1109_li
@changelog_1115_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_1110_li
@changelog_1116_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_1111_li
@changelog_1117_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_1112_li
@changelog_1118_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_1113_li
@changelog_1119_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_1114_li
@changelog_1120_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_1115_li
@changelog_1121_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_1116_li
@changelog_1122_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_1117_li
@changelog_1123_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_1118_li
@changelog_1124_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_1119_li
@changelog_1125_li
#SimpleResultSet: updating a result set is now supported.
#SimpleResultSet: updating a result set is now supported.
@changelog_1120_li
@changelog_1126_li
#Database URL: extra semicolons are not supported.
#Database URL: extra semicolons are not supported.
@changelog_1121_h2
@changelog_1127_h2
#Version 1.3.163 (2011-12-30)
#Version 1.3.163 (2011-12-30)
@changelog_1122_li
@changelog_1128_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_1123_li
@changelog_1129_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_1124_li
@changelog_1130_li
#XMLTEXT now supports an optional parameter to escape newlines.
#XMLTEXT now supports an optional parameter to escape newlines.
@changelog_1125_li
@changelog_1131_li
#XMLNODE now support an optional parameter to disable indentation.
#XMLNODE now support an optional parameter to disable indentation.
@changelog_1126_li
@changelog_1132_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_1127_li
@changelog_1133_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_1128_li
@changelog_1134_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_1129_li
@changelog_1135_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_1130_h2
@changelog_1136_h2
#Version 1.3.162 (2011-11-26)
#Version 1.3.162 (2011-11-26)
@changelog_1131_li
@changelog_1137_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_1132_li
@changelog_1138_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_1133_li
@changelog_1139_li
#Oracle compatibility: support for DECODE(...).
#Oracle compatibility: support for DECODE(...).
@changelog_1134_li
@changelog_1140_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_1135_li
@changelog_1141_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_1136_li
@changelog_1142_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_1137_li
@changelog_1143_li
#Issue 334: SimpleResultSet.getString now also works for Clob columns.
#Issue 334: SimpleResultSet.getString now also works for Clob columns.
@changelog_1138_li
@changelog_1144_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_1139_li
@changelog_1145_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_1140_li
@changelog_1146_li
#Server.createTcpServer, createPgServer, createWebServer: invalid arguments are now detected.
#Server.createTcpServer, createPgServer, createWebServer: invalid arguments are now detected.
@changelog_1141_li
@changelog_1147_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_1142_li
@changelog_1148_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_1143_li
@changelog_1149_li
#A NullPointerException could occur in TableView.isDeterministic for invalid views.
#A NullPointerException could occur in TableView.isDeterministic for invalid views.
@changelog_1144_li
@changelog_1150_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_1145_li
@changelog_1151_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_1146_li
@changelog_1152_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_1147_li
@changelog_1153_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_1148_h2
@changelog_1154_h2
#Version 1.3.161 (2011-10-28)
#Version 1.3.161 (2011-10-28)
@changelog_1149_li
@changelog_1155_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_1150_li
@changelog_1156_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_1151_li
@changelog_1157_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_1152_li
@changelog_1158_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_1153_li
@changelog_1159_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_1154_li
@changelog_1160_li
#Sequences with cache size smaller than 0 did not work correctly.
#Sequences with cache size smaller than 0 did not work correctly.
@changelog_1155_li
@changelog_1161_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_1156_li
@changelog_1162_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_1157_li
@changelog_1163_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_1158_li
@changelog_1164_li
#Issue 347: the RunScript and Shell tools now ignore empty statements.
#Issue 347: the RunScript and Shell tools now ignore empty statements.
@changelog_1159_li
@changelog_1165_li
#Issue 246: improved error message for data conversion problems.
#Issue 246: improved error message for data conversion problems.
@changelog_1160_li
@changelog_1166_li
#Issue 344: the build now supports a custom Maven repository location.
#Issue 344: the build now supports a custom Maven repository location.
@changelog_1161_li
@changelog_1167_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_1162_li
@changelog_1168_li
#SimpleResultSet now supports getColumnTypeName and getColumnClassName.
#SimpleResultSet now supports getColumnTypeName and getColumnClassName.
@changelog_1163_li
@changelog_1169_li
#SimpleResultSet now has minimal BLOB and CLOB support.
#SimpleResultSet now has minimal BLOB and CLOB support.
@changelog_1164_li
@changelog_1170_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_1165_li
@changelog_1171_li
#The Polish translation has been improved by Jarosław Kokociński.
#The Polish translation has been improved by Jarosław Kokociński.
@changelog_1166_li
@changelog_1172_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_1167_li
@changelog_1173_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_1168_li
@changelog_1174_li
#Improved compatibility with the Java 7 FileSystem abstraction.
#Improved compatibility with the Java 7 FileSystem abstraction.
@changelog_1169_h2
@changelog_1175_h2
#Version 1.3.160 (2011-09-11)
#Version 1.3.160 (2011-09-11)
@changelog_1170_li
@changelog_1176_li
#Computed columns could not refer to itself.
#Computed columns could not refer to itself.
@changelog_1171_li
@changelog_1177_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_1172_li
@changelog_1178_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_1173_li
@changelog_1179_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_1174_li
@changelog_1180_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_1175_li
@changelog_1181_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_1176_li
@changelog_1182_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_1177_li
@changelog_1183_li
#Issue 329: CASE expression: data type problem is not detected.
#Issue 329: CASE expression: data type problem is not detected.
@changelog_1178_li
@changelog_1184_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.
@@ -567,160 +567,166 @@ changelog_1021_li=Add a DISK_SPACE_USED system function. Fixes issue 270.
...
@@ -567,160 +567,166 @@ changelog_1021_li=Add a DISK_SPACE_USED system function. Fixes issue 270.
changelog_1022_li=Fix a compile-time ambiguity when compiling with JDK7, thanks to a patch from Lukas Eder.
changelog_1022_li=Fix a compile-time ambiguity when compiling with JDK7, thanks to a patch from Lukas Eder.
changelog_1023_li=Supporting dropping an index for Lucene full-text indexes.
changelog_1023_li=Supporting dropping an index for Lucene full-text indexes.
changelog_1024_li=Optimized performance for SELECT ... ORDER BY X LIMIT Y OFFSET Z queries for in-memory databases using partial sort (by Sergi Vladykin).
changelog_1024_li=Optimized performance for SELECT ... ORDER BY X LIMIT Y OFFSET Z queries for in-memory databases using partial sort (by Sergi Vladykin).
changelog_1025_h2=Version 1.3.170 (2012-11-30)
changelog_1025_li=Experimental off-heap memory storage engine "nioMemFS\:" and "nioMemLZF\:", suggestion from Mark Addleman.
changelog_1026_li=Issue 407\:The TriggerAdapter didn't work with CLOB and BLOB columns.
changelog_1026_li=Issue 438\: JdbcDatabaseMetaData.getSchemas() is no longer supported as of 1.3.169.
changelog_1027_li=PostgreSQL compatibility\:support for data types BIGSERIAL and SERIAL as an alias for AUTO_INCREMENT.
changelog_1027_li=MySQL compatibility\: support for ALTER TABLE tableName MODIFY [COLUMN] columnName columnDef. Patch from Ville Koskela.
changelog_1028_li=Issue 417\:H2 Console\:the web session timeout didn't work, resulting in a memory leak. This was only a problem if the H2 Console was run for a long time and many sessions were opened.
changelog_1028_li=Issue 404\: SHOW COLUMNS FROM tableName does not work with ALLOW_LITERALS\=NUMBERS.
changelog_1029_li=Issue 412\:Running the Server tool with just the option "-browser" will now log a warning.
changelog_1029_li=Throw an explicit error to make it clear we don't support the TRIGGER combination of SELECT and FOR EACH ROW.
changelog_1030_li=Issue 411\:CloseWatcher registration was not concurrency-safe.
changelog_1030_li=Issue 439\: Utils.sortTopN does not handle single-element arrays.
changelog_1031_li=MySQL compatibility\:support for CONCAT_WS. Thanks a lot to litailang for the patch\!
changelog_1031_h2=Version 1.3.170 (2012-11-30)
changelog_1032_li=PostgreSQL compatibility\:support for EXTRACT(WEEK FROM dateColumn). Thanks to Prashant Bhat for the patch\!
changelog_1032_li=Issue 407\: The TriggerAdapter didn't work with CLOB and BLOB columns.
changelog_1033_li=Fix for a bug where we would sometimes use the wrong unique constraint to validate foreign key constraints.
changelog_1033_li=PostgreSQL compatibility\: support for data types BIGSERIAL and SERIAL as an alias for AUTO_INCREMENT.
changelog_1034_li=Support BOM at the beginning of files for the RUNSCRIPT command
changelog_1034_li=Issue 417\: H2 Console\: the web session timeout didn't work, resulting in a memory leak. This was only a problem if the H2 Console was run for a long time and many sessions were opened.
changelog_1035_li=Fix in calling SET @X \=IDENTITY() where it would return NULL incorrectly
changelog_1035_li=Issue 412\: Running the Server tool with just the option "-browser" will now log a warning.
changelog_1036_li=Fix ABBA deadlock between adding a constraint and the H2-Log-Writer thread.
changelog_1036_li=Issue 411\:CloseWatcher registration was not concurrency-safe.
changelog_1037_li=Optimize IN(...) queries where the values are constant and of the same type.
changelog_1037_li=MySQL compatibility\:support for CONCAT_WS. Thanks a lot to litailang for the patch\!
changelog_1038_li=Restore tool\:the parameter "quiet" was not used and is now removed.
changelog_1038_li=PostgreSQL compatibility\:support for EXTRACT(WEEK FROM dateColumn). Thanks to Prashant Bhat for the patch\!
changelog_1039_li=Fix ConcurrentModificationException when creating tables and executing SHOW TABLES in parallel. Reported by Viktor Voytovych.
changelog_1039_li=Fix for a bug where we would sometimes use the wrong unique constraint to validate foreign key constraints.
changelog_1040_li=Serialization is now pluggable using the system property "h2.javaObjectSerializer". Thanks to Sergi Vladykin for the patch\!
changelog_1040_li=Support BOM at the beginning of files for the RUNSCRIPT command
changelog_1041_h2=Version 1.3.169 (2012-09-09)
changelog_1041_li=Fix in calling SET @X \=IDENTITY() where it would return NULL incorrectly
changelog_1042_li=The default jar file is now compiled for Java 6.
changelog_1042_li=Fix ABBA deadlock between adding a constraint and the H2-Log-Writer thread.
changelog_1043_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_1043_li=Optimize IN(...) queries where the values are constant and of the same type.
changelog_1044_li=A part of the documentation and the H2 Console has been changed to support the Apple retina display.
changelog_1044_li=Restore tool\:the parameter "quiet" was not used and is now removed.
changelog_1045_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_1045_li=Fix ConcurrentModificationException when creating tables and executing SHOW TABLES in parallel. Reported by Viktor Voytovych.
changelog_1046_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_1046_li=Serialization is now pluggable using the system property "h2.javaObjectSerializer". Thanks to Sergi Vladykin for the patch\!
changelog_1047_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_1047_h2=Version 1.3.169 (2012-09-09)
changelog_1048_li=Issue 414\:for some functions, the parameters were evaluated twice (for example "char(nextval(..))" ran "nextval(..)" twice).
changelog_1048_li=The default jar file is now compiled for Java 6.
changelog_1049_li=The ResultSetMetaData methods getSchemaName and getTableName could return null instead of "" (an empty string) as specified in the JDBC API.
changelog_1049_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_1050_li=Added compatibility for "SET NAMES" query in MySQL compatibility mode.
changelog_1050_li=A part of the documentation and the H2 Console has been changed to support the Apple retina display.
changelog_1051_h2=Version 1.3.168 (2012-07-13)
changelog_1051_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_1052_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_1052_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_1053_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_1053_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_1054_li=Dylan has translated the H2 Console tool to Korean. Thanks a lot\!
changelog_1054_li=Issue 414\:for some functions, the parameters were evaluated twice (for example "char(nextval(..))" ran "nextval(..)" twice).
changelog_1055_li=Executing the statement CREATE INDEX IF ALREADY EXISTS if the index already exists no longer fails for a read only database.
changelog_1055_li=The ResultSetMetaData methods getSchemaName and getTableName could return null instead of "" (an empty string) as specified in the JDBC API.
changelog_1056_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_1056_li=Added compatibility for "SET NAMES" query in MySQL compatibility mode.
changelog_1057_li=Fulltext search\:in-memory Lucene indexes are now supported.
changelog_1057_h2=Version 1.3.168 (2012-07-13)
changelog_1058_li=Fulltext search\:UUID primary keys are now supported.
changelog_1058_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_1059_li=Apache Tomcat 7.x will now longer log a warning when unloading the web application, if using a connection pool.
changelog_1059_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_1060_li=H2 Console\:support the Midori browser (for Debian / Raspberry Pi)
changelog_1060_li=Dylan has translated the H2 Console tool to Korean. Thanks a lot\!
changelog_1061_li=When opening a remote session, don't open a temporary file if the trace level is set to zero
changelog_1061_li=Executing the statement CREATE INDEX IF ALREADY EXISTS if the index already exists no longer fails for a read only database.
changelog_1062_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_1062_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_1063_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_1063_li=Fulltext search\:in-memory Lucene indexes are now supported.
changelog_1064_h2=Version 1.3.167 (2012-05-23)
changelog_1064_li=Fulltext search\:UUID primary keys are now supported.
changelog_1065_li=H2 Console\:when editing a row, an empty varchar column was replaced with a single space.
changelog_1065_li=Apache Tomcat 7.x will now longer log a warning when unloading the web application, if using a connection pool.
changelog_1066_li=Lukas Eder has updated the jOOQ documentation.
changelog_1066_li=H2 Console\:support the Midori browser (for Debian / Raspberry Pi)
changelog_1067_li=Some nested joins could not be executed, for example\:select * from (select * from (select * from a) a right join b b) c;
changelog_1067_li=When opening a remote session, don't open a temporary file if the trace level is set to zero
changelog_1068_li=MS SQL Server compatibility\:ISNULL is now an alias for IFNULL.
changelog_1068_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_1069_li=Terrence Huang has completed the translation of the H2 Console tool to Chinese. Thanks a lot\!
changelog_1069_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_1070_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_1070_h2=Version 1.3.167 (2012-05-23)
changelog_1071_li=In the trace file, the query execution time was incorrect in some cases, specially for the statement SET TRACE_LEVEL_FILE 2.
changelog_1071_li=H2 Console\:when editing a row, an empty varchar column was replaced with a single space.
changelog_1072_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_1072_li=Lukas Eder has updated the jOOQ documentation.
changelog_1073_li=Then reading from a resource using the prefix "classpath\:", the ContextClassLoader is now used if the resource can't be read otherwise.
changelog_1073_li=Some nested joins could not be executed, for example\:select * from (select * from (select * from a) a right join b b) c;
changelog_1074_li=DatabaseEventListener now calls setProgress whenever a statement starts and ends.
changelog_1074_li=MS SQL Server compatibility\:ISNULL is now an alias for IFNULL.
changelog_1075_li=DatabaseEventListener now calls setProgress periodically while a statement is running.
changelog_1075_li=Terrence Huang has completed the translation of the H2 Console tool to Chinese. Thanks a lot\!
changelog_1076_li=The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME.
changelog_1076_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_1077_li=Issue 378\: when using views, the wrong values were bound to a parameter in some cases.
changelog_1077_li=In the trace file, the query execution time was incorrect in some cases, specially for the statement SET TRACE_LEVEL_FILE 2.
changelog_1078_li=Terrence Huang has translated the error messages to Chinese. Thanks a lot\!
changelog_1078_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_1079_li=TRUNC was added as an alias for TRUNCATE.
changelog_1079_li=Then reading from a resource using the prefix "classpath\:", the ContextClassLoader is now used if the resource can't be read otherwise.
changelog_1080_li=Small optimisation for accessing result values by column name.
changelog_1080_li=DatabaseEventListener now calls setProgress whenever a statement starts and ends.
changelog_1081_li=Fix for bug in Statement.getMoreResults(int)
changelog_1081_li=DatabaseEventListener now calls setProgress periodically while a statement is running.
changelog_1082_li=The SCRIPT statements now supports filtering by schema and table. Thanks a lot to Jacob Qvortrup for providing the patch\!
changelog_1082_li=The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME.
changelog_1083_h2=Version 1.3.166 (2012-04-08)
changelog_1083_li=Issue 378\: when using views, the wrong values were bound to a parameter in some cases.
changelog_1084_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_1084_li=Terrence Huang has translated the error messages to Chinese. Thanks a lot\!
changelog_1085_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_1085_li=TRUNC was added as an alias for TRUNCATE.
changelog_1086_li=ConvertTraceFile\:the time in the trace file is now parsed as a long.
changelog_1086_li=Small optimisation for accessing result values by column name.
changelog_1087_li=Invalid connection settings are now detected.
changelog_1087_li=Fix for bug in Statement.getMoreResults(int)
changelog_1088_li=Issue 387\:WHERE condition getting pushed into sub-query with LIMIT.
changelog_1088_li=The SCRIPT statements now supports filtering by schema and table. Thanks a lot to Jacob Qvortrup for providing the patch\!
changelog_1089_h2=Version 1.3.165 (2012-03-18)
changelog_1089_h2=Version 1.3.166 (2012-04-08)
changelog_1090_li=Better string representation for decimal values (for example 0.00000000 instead of 0E-26).
changelog_1090_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_1091_li=Prepared statements could only be re-used if the same data types were used the second time they were executed.
changelog_1091_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_1092_li=In error messages about referential constraint violation, the values are now included.
changelog_1092_li=ConvertTraceFile\:the time in the trace file is now parsed as a long.
changelog_1093_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_1093_li=Invalid connection settings are now detected.
changelog_1094_li=MySQL compatibility\:SUBSTR with a negative start index now works like MySQL.
changelog_1094_li=Issue 387\:WHERE condition getting pushed into sub-query with LIMIT.
changelog_1095_li=When enabling autocommit, the transaction is now committed (as required by the JDBC API).
changelog_1095_h2=Version 1.3.165 (2012-03-18)
changelog_1096_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_1096_li=Better string representation for decimal values (for example 0.00000000 instead of 0E-26).
changelog_1097_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_1097_li=Prepared statements could only be re-used if the same data types were used the second time they were executed.
changelog_1098_li=ALTER TABLE ADD can now add more than one column at a time.
changelog_1098_li=In error messages about referential constraint violation, the values are now included.
changelog_1099_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_1099_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_1100_li=Issue 384\:the wrong kind of exception (NullPointerException) was thrown in a UNION query with an incorrect ORDER BY expression.
changelog_1100_li=MySQL compatibility\:SUBSTR with a negative start index now works like MySQL.
changelog_1101_li=Issue 362\:support LIMIT in UPDATE statements.
changelog_1101_li=When enabling autocommit, the transaction is now committed (as required by the JDBC API).
changelog_1102_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_1102_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_1103_li=CSV tool\:new feature to disable writing the column header (option writeColumnHeader).
changelog_1103_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_1104_li=CSV tool\:new feature to preserve the case sensitivity of column names (option caseSensitiveColumnNames).
changelog_1104_li=ALTER TABLE ADD can now add more than one column at a time.
changelog_1105_li=PostgreSQL compatibility\:LOG(x) is base 10 in the PostgreSQL mode.
changelog_1105_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_1106_h2=Version 1.3.164 (2012-02-03)
changelog_1106_li=Issue 384\:the wrong kind of exception (NullPointerException) was thrown in a UNION query with an incorrect ORDER BY expression.
changelog_1107_li=New built-in function ARRAY_CONTAINS.
changelog_1107_li=Issue 362\:support LIMIT in UPDATE statements.
changelog_1108_li=Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
changelog_1108_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_1109_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_1109_li=CSV tool\:new feature to disable writing the column header (option writeColumnHeader).
changelog_1110_li=TriggerAdapter\:in "before" triggers, values can be changed using the ResultSet.updateX methods.
changelog_1110_li=CSV tool\:new feature to preserve the case sensitivity of column names (option caseSensitiveColumnNames).
changelog_1111_li=Creating a table with column data type NULL now works (even if not very useful).
changelog_1111_li=PostgreSQL compatibility\:LOG(x) is base 10 in the PostgreSQL mode.
changelog_1112_li=ALTER TABLE ALTER COLUMN no longer copies the data for widening conversions (for example if only the precision was increased) unless necessary.
changelog_1112_h2=Version 1.3.164 (2012-02-03)
changelog_1113_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_1113_li=New built-in function ARRAY_CONTAINS.
changelog_1114_li=The script created by SCRIPT DROP did not always work if multiple views existed that depend on each other.
changelog_1114_li=Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
changelog_1115_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_1115_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_1116_li=The database file locking mechanism "FS" (;FILE_LOCK\=FS) did not work on Linux since version 1.3.161.
changelog_1116_li=TriggerAdapter\:in "before" triggers, values can be changed using the ResultSet.updateX methods.
changelog_1117_li=Sequences\:the functions NEXTVAL and CURRVAL did not work as expected when using quoted, mixed case sequence names.
changelog_1117_li=Creating a table with column data type NULL now works (even if not very useful).
changelog_1118_li=The constructor for Csv objects is now public, and Csv.getInstance() is now deprecated.
changelog_1118_li=ALTER TABLE ALTER COLUMN no longer copies the data for widening conversions (for example if only the precision was increased) unless necessary.
changelog_1119_li=SimpleResultSet\:updating a result set is now supported.
changelog_1119_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_1120_li=Database URL\:extra semicolons are not supported.
changelog_1120_li=The script created by SCRIPT DROP did not always work if multiple views existed that depend on each other.
changelog_1121_h2=Version 1.3.163 (2011-12-30)
changelog_1121_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_1122_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_1122_li=The database file locking mechanism "FS" (;FILE_LOCK\=FS) did not work on Linux since version 1.3.161.
changelog_1123_li=DatabaseEventListener.diskSpaceIsLow() is no longer supported because it can't be guaranteed that it always works correctly.
changelog_1123_li=Sequences\:the functions NEXTVAL and CURRVAL did not work as expected when using quoted, mixed case sequence names.
changelog_1124_li=XMLTEXT now supports an optional parameter to escape newlines.
changelog_1124_li=The constructor for Csv objects is now public, and Csv.getInstance() is now deprecated.
changelog_1125_li=XMLNODE now support an optional parameter to disable indentation.
changelog_1125_li=SimpleResultSet\:updating a result set is now supported.
changelog_1126_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_1126_li=Database URL\:extra semicolons are not supported.
changelog_1127_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_1127_h2=Version 1.3.163 (2011-12-30)
changelog_1128_li=The page size of a persistent database can now be queries using\:select * from information_schema.settings where name \='info.PAGE_SIZE'
changelog_1128_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_1129_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_1129_li=DatabaseEventListener.diskSpaceIsLow() is no longer supported because it can't be guaranteed that it always works correctly.
changelog_1130_h2=Version 1.3.162 (2011-11-26)
changelog_1130_li=XMLTEXT now supports an optional parameter to escape newlines.
changelog_1131_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_1131_li=XMLNODE now support an optional parameter to disable indentation.
changelog_1132_li=When using a VPN, starting a H2 server did not work (for some VPN software).
changelog_1132_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_1133_li=Oracle compatibility\:support for DECODE(...).
changelog_1133_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_1134_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_1134_li=The page size of a persistent database can now be queries using\:select * from information_schema.settings where name \='info.PAGE_SIZE'
changelog_1135_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_1135_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_1136_li=Read-only databases in a zip file did not work when using the -baseDir option.
changelog_1136_h2=Version 1.3.162 (2011-11-26)
changelog_1137_li=Issue 334\:SimpleResultSet.getString now also works for Clob columns.
changelog_1137_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_1138_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_1138_li=When using a VPN, starting a H2 server did not work (for some VPN software).
changelog_1139_li=Server\:in some (theoretical) cases, exceptions while closing the connection were ignored.
changelog_1139_li=Oracle compatibility\:support for DECODE(...).
changelog_1140_li=Server.createTcpServer, createPgServer, createWebServer\:invalid arguments are now detected.
changelog_1140_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_1141_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_1141_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_1142_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_1142_li=Read-only databases in a zip file did not work when using the -baseDir option.
changelog_1143_li=A NullPointerException could occur in TableView.isDeterministic for invalid views.
changelog_1143_li=Issue 334\:SimpleResultSet.getString now also works for Clob columns.
changelog_1144_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_1144_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_1145_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_1145_li=Server\:in some (theoretical) cases, exceptions while closing the connection were ignored.
changelog_1146_li=The optimization for "group by" was not working correctly if the group by column was aliased in the select list.
changelog_1146_li=Server.createTcpServer, createPgServer, createWebServer\:invalid arguments are now detected.
changelog_1147_li=Issue 326\:improved support for case sensitive (mixed case) identifiers without quotes when using DATABASE_TO_UPPER\=FALSE.
changelog_1147_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_1148_h2=Version 1.3.161 (2011-10-28)
changelog_1148_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_1149_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_1149_li=A NullPointerException could occur in TableView.isDeterministic for invalid views.
changelog_1150_li=TCP server\:when using the trace option ("-trace"), the trace output contained unnecessary stack traces when stopping the server.
changelog_1150_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_1151_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_1151_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_1152_li=Issue 350\:when using instead of triggers, executeUpdate for delete operations always returned 0.
changelog_1152_li=The optimization for "group by" was not working correctly if the group by column was aliased in the select list.
changelog_1153_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_1153_li=Issue 326\:improved support for case sensitive (mixed case) identifiers without quotes when using DATABASE_TO_UPPER\=FALSE.
changelog_1154_li=Sequences with cache size smaller than 0 did not work correctly.
changelog_1154_h2=Version 1.3.161 (2011-10-28)
changelog_1155_li=Issue 356\:for Blob objects, InputStream.skip() returned 0, causing EOFException in Blob.getBytes(.., ..).
changelog_1155_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_1156_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_1156_li=TCP server\:when using the trace option ("-trace"), the trace output contained unnecessary stack traces when stopping the server.
changelog_1157_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_1157_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_1158_li=Issue 347\:the RunScript and Shell tools now ignore empty statements.
changelog_1158_li=Issue 350\:when using instead of triggers, executeUpdate for delete operations always returned 0.
changelog_1159_li=Issue 246\:improved error message for data conversion problems.
changelog_1159_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_1160_li=Issue 344\:the build now supports a custom Maven repository location.
changelog_1160_li=Sequences with cache size smaller than 0 did not work correctly.
changelog_1161_li=Issue 334\:Java functions that return CLOB or BLOB objects could not be used as tables.
changelog_1161_li=Issue 356\:for Blob objects, InputStream.skip() returned 0, causing EOFException in Blob.getBytes(.., ..).
changelog_1162_li=SimpleResultSet now supports getColumnTypeName and getColumnClassName.
changelog_1162_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_1163_li=SimpleResultSet now has minimal BLOB and CLOB support.
changelog_1163_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_1164_li=Improved performance for large databases (many GB), and databases with a small page size.
changelog_1164_li=Issue 347\:the RunScript and Shell tools now ignore empty statements.
changelog_1165_li=The Polish translation has been improved by Jaros&\#322;aw Kokoci&\#324;ski.
changelog_1165_li=Issue 246\:improved error message for data conversion problems.
changelog_1166_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_1166_li=Issue 344\:the build now supports a custom Maven repository location.
changelog_1167_li=Improved compatibility for "fetch first / next row(s)". Thanks a lot to litailang for the patch\!
changelog_1167_li=Issue 334\:Java functions that return CLOB or BLOB objects could not be used as tables.
changelog_1168_li=Improved compatibility with the Java 7 FileSystem abstraction.
changelog_1168_li=SimpleResultSet now supports getColumnTypeName and getColumnClassName.
changelog_1169_h2=Version 1.3.160 (2011-09-11)
changelog_1169_li=SimpleResultSet now has minimal BLOB and CLOB support.
changelog_1170_li=Computed columns could not refer to itself.
changelog_1170_li=Improved performance for large databases (many GB), and databases with a small page size.
changelog_1171_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_1171_li=The Polish translation has been improved by Jaros&\#322;aw Kokoci&\#324;ski.
changelog_1172_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_1172_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_1173_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_1173_li=Improved compatibility for "fetch first / next row(s)". Thanks a lot to litailang for the patch\!
changelog_1174_li=Source code switching using //\#\#has been simplified. The Java 1.5 tag has been removed because is no longer needed.
changelog_1174_li=Improved compatibility with the Java 7 FileSystem abstraction.
changelog_1175_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_1175_h2=Version 1.3.160 (2011-09-11)
changelog_1176_li=Invalid tables names in 'order by' columns were not detected in some cases. Example\:select x from dual order by y.x
changelog_1176_li=Computed columns could not refer to itself.
changelog_1177_li=Issue 329\:CASE expression\:data type problem is not detected.
changelog_1177_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_1178_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_1178_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_1179_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_1180_li=Source code switching using //\#\#has been simplified. The Java 1.5 tag has been removed because is no longer needed.
changelog_1181_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_1182_li=Invalid tables names in 'order by' columns were not detected in some cases. Example\:select x from dual order by y.x
changelog_1183_li=Issue 329\:CASE expression\:data type problem is not detected.
changelog_1184_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.
