H2 Console: when editing a row, an empty varchar column was replaced with a single space.
@changelog_1003_li
@changelog_1003_li
Some nested joins could not be executed, for example: select * from (select * from (select * from a) a right join b b) c;
Lukas Eder has updated the jOOQ documentation.
@changelog_1004_li
@changelog_1004_li
MS SQL Server compatibility: ISNULL is now an alias for IFNULL.
Some nested joins could not be executed, for example: select * from (select * from (select * from a) a right join b b) c;
@changelog_1005_li
@changelog_1005_li
Terrence Huang has completed the translation of the H2 Console tool to Chinese. Thanks a lot!
MS SQL Server compatibility: ISNULL is now an alias for IFNULL.
@changelog_1006_li
@changelog_1006_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.
Terrence Huang has completed the translation of the H2 Console tool to Chinese. Thanks a lot!
@changelog_1007_li
@changelog_1007_li
In the trace file, the query execution time was incorrect in some cases, specially for the statement SET TRACE_LEVEL_FILE 2.
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_1008_li
@changelog_1008_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.
In the trace file, the query execution time was incorrect in some cases, specially for the statement SET TRACE_LEVEL_FILE 2.
@changelog_1009_li
@changelog_1009_li
Then reading from a resource using the prefix "classpath:", the ContextClassLoader is now used if the resource can't be read otherwise.
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_1010_li
@changelog_1010_li
DatabaseEventListener now calls setProgress whenever a statement starts and ends.
Then reading from a resource using the prefix "classpath:", the ContextClassLoader is now used if the resource can't be read otherwise.
@changelog_1011_li
@changelog_1011_li
DatabaseEventListener now calls setProgress periodically while a statement is running.
DatabaseEventListener now calls setProgress whenever a statement starts and ends.
@changelog_1012_li
@changelog_1012_li
The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME.
DatabaseEventListener now calls setProgress periodically while a statement is running.
@changelog_1013_li
@changelog_1013_li
Issue 378: when using views, the wrong values were bound to a parameter in some cases.
The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME.
@changelog_1014_li
@changelog_1014_li
Terrence Huang has translated the error messages to Chinese. Thanks a lot!
Issue 378: when using views, the wrong values were bound to a parameter in some cases.
@changelog_1015_li
@changelog_1015_li
TRUNC was added as an alias for TRUNCATE.
Terrence Huang has translated the error messages to Chinese. Thanks a lot!
@changelog_1016_li
@changelog_1016_li
Small optimisation for accessing result values by column name.
TRUNC was added as an alias for TRUNCATE.
@changelog_1017_li
@changelog_1017_li
Fix for bug in Statement#getMoreResults(int)
Small optimisation for accessing result values by column name.
@changelog_1018_li
@changelog_1018_li
Fix for bug in Statement#getMoreResults(int)
@changelog_1019_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_1019_h2
@changelog_1020_h2
Version 1.3.166 (2012-04-08)
Version 1.3.166 (2012-04-08)
@changelog_1020_li
@changelog_1021_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_1021_li
@changelog_1022_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_1022_li
@changelog_1023_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_1023_li
@changelog_1024_li
Invalid connection settings are now detected.
Invalid connection settings are now detected.
@changelog_1024_li
@changelog_1025_li
Issue 387: WHERE condition getting pushed into sub-query with LIMIT.
Issue 387: WHERE condition getting pushed into sub-query with LIMIT.
@changelog_1025_h2
@changelog_1026_h2
Version 1.3.165 (2012-03-18)
Version 1.3.165 (2012-03-18)
@changelog_1026_li
@changelog_1027_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_1027_li
@changelog_1028_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_1028_li
@changelog_1029_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_1029_li
@changelog_1030_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_1030_li
@changelog_1031_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_1031_li
@changelog_1032_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_1032_li
@changelog_1033_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_1033_li
@changelog_1034_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_1034_li
@changelog_1035_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_1035_li
@changelog_1036_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_1036_li
@changelog_1037_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_1037_li
@changelog_1038_li
Issue 362: support LIMIT in UPDATE statements.
Issue 362: support LIMIT in UPDATE statements.
@changelog_1038_li
@changelog_1039_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_1039_li
@changelog_1040_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_1040_li
@changelog_1041_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_1041_li
@changelog_1042_li
PostgreSQL compatibility: LOG(x) is base 10 in the PostgreSQL mode.
PostgreSQL compatibility: LOG(x) is base 10 in the PostgreSQL mode.
@changelog_1042_h2
@changelog_1043_h2
Version 1.3.164 (2012-02-03)
Version 1.3.164 (2012-02-03)
@changelog_1043_li
@changelog_1044_li
New built-in function ARRAY_CONTAINS.
New built-in function ARRAY_CONTAINS.
@changelog_1044_li
@changelog_1045_li
Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
@changelog_1045_li
@changelog_1046_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_1046_li
@changelog_1047_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_1047_li
@changelog_1048_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_1048_li
@changelog_1049_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_1049_li
@changelog_1050_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_1050_li
@changelog_1051_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_1051_li
@changelog_1052_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_1052_li
@changelog_1053_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_1053_li
@changelog_1054_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_1054_li
@changelog_1055_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_1055_li
@changelog_1056_li
SimpleResultSet: updating a result set is now supported.
SimpleResultSet: updating a result set is now supported.
@changelog_1056_li
@changelog_1057_li
Database URL: extra semicolons are not supported.
Database URL: extra semicolons are not supported.
@changelog_1057_h2
@changelog_1058_h2
Version 1.3.163 (2011-12-30)
Version 1.3.163 (2011-12-30)
@changelog_1058_li
@changelog_1059_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_1059_li
@changelog_1060_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_1060_li
@changelog_1061_li
XMLTEXT now supports an optional parameter to escape newlines.
XMLTEXT now supports an optional parameter to escape newlines.
@changelog_1061_li
@changelog_1062_li
XMLNODE now support an optional parameter to disable indentation.
XMLNODE now support an optional parameter to disable indentation.
@changelog_1062_li
@changelog_1063_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_1063_li
@changelog_1064_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_1064_li
@changelog_1065_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_1065_li
@changelog_1066_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_1066_h2
@changelog_1067_h2
Version 1.3.162 (2011-11-26)
Version 1.3.162 (2011-11-26)
@changelog_1067_li
@changelog_1068_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_1068_li
@changelog_1069_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_1069_li
@changelog_1070_li
Oracle compatibility: support for DECODE(...).
Oracle compatibility: support for DECODE(...).
@changelog_1070_li
@changelog_1071_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_1071_li
@changelog_1072_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_1072_li
@changelog_1073_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_1073_li
@changelog_1074_li
Issue 334: SimpleResultSet.getString now also works for Clob columns.
Issue 334: SimpleResultSet.getString now also works for Clob columns.
@changelog_1074_li
@changelog_1075_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_1075_li
@changelog_1076_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_1076_li
@changelog_1077_li
Server.createTcpServer, createPgServer, createWebServer: invalid arguments are now detected.
Server.createTcpServer, createPgServer, createWebServer: invalid arguments are now detected.
@changelog_1077_li
@changelog_1078_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_1078_li
@changelog_1079_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_1079_li
@changelog_1080_li
A NullPointerException could occur in TableView.isDeterministic for invalid views.
A NullPointerException could occur in TableView.isDeterministic for invalid views.
@changelog_1080_li
@changelog_1081_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_1081_li
@changelog_1082_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_1082_li
@changelog_1083_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_1083_li
@changelog_1084_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_1084_h2
@changelog_1085_h2
Version 1.3.161 (2011-10-28)
Version 1.3.161 (2011-10-28)
@changelog_1085_li
@changelog_1086_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_1086_li
@changelog_1087_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_1087_li
@changelog_1088_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_1088_li
@changelog_1089_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_1089_li
@changelog_1090_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_1090_li
@changelog_1091_li
Sequences with cache size smaller than 0 did not work correctly.
Sequences with cache size smaller than 0 did not work correctly.
@changelog_1091_li
@changelog_1092_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_1092_li
@changelog_1093_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_1093_li
@changelog_1094_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_1094_li
@changelog_1095_li
Issue 347: the RunScript and Shell tools now ignore empty statements.
Issue 347: the RunScript and Shell tools now ignore empty statements.
@changelog_1095_li
@changelog_1096_li
Issue 246: improved error message for data conversion problems.
Issue 246: improved error message for data conversion problems.
@changelog_1096_li
@changelog_1097_li
Issue 344: the build now supports a custom Maven repository location.
Issue 344: the build now supports a custom Maven repository location.
@changelog_1097_li
@changelog_1098_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_1098_li
@changelog_1099_li
SimpleResultSet now supports getColumnTypeName and getColumnClassName.
SimpleResultSet now supports getColumnTypeName and getColumnClassName.
@changelog_1099_li
@changelog_1100_li
SimpleResultSet now has minimal BLOB and CLOB support.
SimpleResultSet now has minimal BLOB and CLOB support.
@changelog_1100_li
@changelog_1101_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_1101_li
@changelog_1102_li
The Polish translation has been improved by Jarosław Kokociński.
The Polish translation has been improved by Jarosław Kokociński.
@changelog_1102_li
@changelog_1103_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_1103_li
@changelog_1104_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_1104_li
@changelog_1105_li
Improved compatibility with the Java 7 FileSystem abstraction.
Improved compatibility with the Java 7 FileSystem abstraction.
@changelog_1105_h2
@changelog_1106_h2
Version 1.3.160 (2011-09-11)
Version 1.3.160 (2011-09-11)
@changelog_1106_li
@changelog_1107_li
Computed columns could not refer to itself.
Computed columns could not refer to itself.
@changelog_1107_li
@changelog_1108_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_1108_li
@changelog_1109_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_1109_li
@changelog_1110_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_1110_li
@changelog_1111_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_1111_li
@changelog_1112_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_1112_li
@changelog_1113_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_1113_li
@changelog_1114_li
Issue 329: CASE expression: data type problem is not detected.
Issue 329: CASE expression: data type problem is not detected.
@changelog_1114_li
@changelog_1115_li
Issue 311: File lock mode serialized: selecting the next value from a sequence didn't work after a pause, because the database thought this is a read-only operation.
Issue 311: File lock mode serialized: selecting the next value from a sequence didn't work after a pause, because the database thought this is a read-only operation.
@changelog_1115_h2
@changelog_1116_h2
Version 1.3.159 (2011-08-13)
Version 1.3.159 (2011-08-13)
@changelog_1116_li
@changelog_1117_li
Creating a temporary table with the option 'transactional' will now also create the indexes in transactional mode, if the indexes are included in the 'create table' statement as follows: "create local temporary table temp(id int primary key, name varchar, constraint x index(name)) transactional".
Creating a temporary table with the option 'transactional' will now also create the indexes in transactional mode, if the indexes are included in the 'create table' statement as follows: "create local temporary table temp(id int primary key, name varchar, constraint x index(name)) transactional".
@changelog_1117_li
@changelog_1118_li
The database file size grows now 35%, but at most 256 MB at a time.
The database file size grows now 35%, but at most 256 MB at a time.
@changelog_1118_li
@changelog_1119_li
Improved error message on network configuration problems.
Improved error message on network configuration problems.
@changelog_1119_li
@changelog_1120_li
The build now support an offline build using ./build.sh offline. This will list the required dependencies if jar files are missing.
The build now support an offline build using ./build.sh offline. This will list the required dependencies if jar files are missing.
@changelog_1120_li
@changelog_1121_li
The BLOB / CLOB data was dropped a little bit before the table was dropped. This could cause "lob not found" errors when the process was killed while a table was dropped.
The BLOB / CLOB data was dropped a little bit before the table was dropped. This could cause "lob not found" errors when the process was killed while a table was dropped.
@changelog_1121_li
@changelog_1122_li
"group_concat(distinct ...)" did not work correctly in a view or subquery (the 'distinct' was lost). Example: select * from (select group_concat(distinct 1) from system_range(1, 3));
"group_concat(distinct ...)" did not work correctly in a view or subquery (the 'distinct' was lost). Example: select * from (select group_concat(distinct 1) from system_range(1, 3));
@changelog_1122_li
@changelog_1123_li
Database URLs can now be re-mapped to another URL using the system property "h2.urlMap", which points to a properties file with database URL mappings.
Database URLs can now be re-mapped to another URL using the system property "h2.urlMap", which points to a properties file with database URL mappings.
@changelog_1123_li
@changelog_1124_li
When using InputStream.skip, trying to read past the end of a BLOB failed with the exception "IO Exception: Missing lob entry: ..." [90028-...].
When using InputStream.skip, trying to read past the end of a BLOB failed with the exception "IO Exception: Missing lob entry: ..." [90028-...].
@changelog_1124_li
@changelog_1125_li
The in-memory file system "memFS:" now has limited support for directories.
The in-memory file system "memFS:" now has limited support for directories.
@changelog_1125_li
@changelog_1126_li
To test recovery, append ;RECOVER_TEST=64 to the database URL. This will simulate an application crash after each 64 writes to the database file. A log file named databaseName.h2.db.log is created that lists the operations. The recovery is tested using an in-memory file system, that means it may require a larger heap setting.
To test recovery, append ;RECOVER_TEST=64 to the database URL. This will simulate an application crash after each 64 writes to the database file. A log file named databaseName.h2.db.log is created that lists the operations. The recovery is tested using an in-memory file system, that means it may require a larger heap setting.
@changelog_1126_li
@changelog_1127_li
Converting a hex string to a byte array is now faster.
Converting a hex string to a byte array is now faster.
@changelog_1127_li
@changelog_1128_li
The SQL statement "shutdown defrag" could corrupt the database if the process was killed while the shutdown was in progress. The same problem could occur when the database setting "defrag_always" was used.
The SQL statement "shutdown defrag" could corrupt the database if the process was killed while the shutdown was in progress. The same problem could occur when the database setting "defrag_always" was used.
@changelog_1128_h2
@changelog_1129_h2
Version 1.3.158 (2011-07-17)
Version 1.3.158 (2011-07-17)
@changelog_1129_li
@changelog_1130_li
Fulltext search (native): after re-opening the connection once the fulltext index was created, a transaction rollback did not roll back the modifications in the index.
Fulltext search (native): after re-opening the connection once the fulltext index was created, a transaction rollback did not roll back the modifications in the index.
@changelog_1130_li
@changelog_1131_li
Support for ROW_NUMBER() OVER() as an alias for ROWNUM() for compatibility with PostgreSQL and Apache Derby.
Support for ROW_NUMBER() OVER() as an alias for ROWNUM() for compatibility with PostgreSQL and Apache Derby.
@changelog_1131_li
@changelog_1132_li
Issue 325: a deadlock in the fulltext search could occur if the connection that was used while initializing the fulltext search was later used to query the database. This was actually not only a problem for fulltext search, but also for other triggers that used the initializing connection later on.
Issue 325: a deadlock in the fulltext search could occur if the connection that was used while initializing the fulltext search was later used to query the database. This was actually not only a problem for fulltext search, but also for other triggers that used the initializing connection later on.
@changelog_1132_li
@changelog_1133_li
DATABASE_TO_UPPER: when set to false, all identifier names (table names, column names) are case sensitive (except aggregate, built-in functions, data types, and keywords). This is for improved compatibility with MySQL and PostgreSQL.
DATABASE_TO_UPPER: when set to false, all identifier names (table names, column names) are case sensitive (except aggregate, built-in functions, data types, and keywords). This is for improved compatibility with MySQL and PostgreSQL.
@changelog_1133_li
@changelog_1134_li
When upgrading from an older 1.3.x version to version 1.3.157, when using BLOB or CLOB data, the database could only be opened once.
When upgrading from an older 1.3.x version to version 1.3.157, when using BLOB or CLOB data, the database could only be opened once.
@changelog_1134_li
@changelog_1135_li
SUM on a boolean expression will now count the number of 'true' rows.
SUM on a boolean expression will now count the number of 'true' rows.
@changelog_1135_li
@changelog_1136_li
Simplified test cases using assertThrows(...).
Simplified test cases using assertThrows(...).
@changelog_1136_li
@changelog_1137_li
A Java function that returns a result set that was generated using the provided connection could cause an internal error in some cases. Now such result sets are copied early on.
A Java function that returns a result set that was generated using the provided connection could cause an internal error in some cases. Now such result sets are copied early on.
@changelog_1137_li
@changelog_1138_li
Data type RESULT_SET: information_schema.function_aliases returned type 0; now type -10 is returned (the same as Oracle: OracleTypes.CURSOR = -10).
Data type RESULT_SET: information_schema.function_aliases returned type 0; now type -10 is returned (the same as Oracle: OracleTypes.CURSOR = -10).
@changelog_1138_li
@changelog_1139_li
Data type RESULT_SET: tables with columns of type RESULT_SET could be created, but no data could be persisted in this column.
Data type RESULT_SET: tables with columns of type RESULT_SET could be created, but no data could be persisted in this column.
@changelog_1139_li
@changelog_1140_li
H2 Console: improved system tray icon for Mac OS X (transparent background).
H2 Console: improved system tray icon for Mac OS X (transparent background).
@changelog_1140_li
@changelog_1141_li
String.toUpperCase() was used a few places, which is problematic when using the Turkish locale. The method has been replaced with toUpperCase(Locale.ENGLISH) to solve such problems.
String.toUpperCase() was used a few places, which is problematic when using the Turkish locale. The method has been replaced with toUpperCase(Locale.ENGLISH) to solve such problems.
@changelog_1141_li
@changelog_1142_li
Shell tool: the built-in command "distinct" has been removed (use the SQL statements "show tables" / "show columns from tableName" instead). The result set formatting has been improved.
Shell tool: the built-in command "distinct" has been removed (use the SQL statements "show tables" / "show columns from tableName" instead). The result set formatting has been improved.
@changelog_1142_li
@changelog_1143_li
MERGE: if a unique key was violated (but not the primary key or the key columns of the merge itself), the wrong exception was thrown.
MERGE: if a unique key was violated (but not the primary key or the key columns of the merge itself), the wrong exception was thrown.
@changelog_1143_li
@changelog_1144_li
IBM DB2 and Apache Derby compatibility: support the pseudo-table SYSIBM.SYSDUMMY1.
IBM DB2 and Apache Derby compatibility: support the pseudo-table SYSIBM.SYSDUMMY1.
@changelog_1144_li
@changelog_1145_li
ROWNUM() did not work in combination with IN(..). The following query did not work as expected: select * from (select rownum r from test) where r in (1, 2).
ROWNUM() did not work in combination with IN(..). The following query did not work as expected: select * from (select rownum r from test) where r in (1, 2).
@changelog_1145_li
@changelog_1146_li
H2 Console autocomplete: the autocomplete feature didn't support quoted names.
H2 Console autocomplete: the autocomplete feature didn't support quoted names.
@changelog_1146_li
@changelog_1147_li
It is now longer allowed to create an index on a CLOB or BLOB column (except for in-memory databases or indexes), because recovery doesn't work on such columns. Fulltext indexes on such column are still supported of course.
It is now longer allowed to create an index on a CLOB or BLOB column (except for in-memory databases or indexes), because recovery doesn't work on such columns. Fulltext indexes on such column are still supported of course.
@changelog_1147_li
@changelog_1148_li
The PUBLIC schema could be renamed, which could result in a database that can't be opened normally. Now it can no longer be renamed. The schema INFORMATION_SCHEMA can also no longer be renamed.
The PUBLIC schema could be renamed, which could result in a database that can't be opened normally. Now it can no longer be renamed. The schema INFORMATION_SCHEMA can also no longer be renamed.
@changelog_1148_li
@changelog_1149_li
Server mode: the problem with server and client using different timezones with different daylight saving rules has been solved (this only applies when both the client and the server use this or a newer version).
Server mode: the problem with server and client using different timezones with different daylight saving rules has been solved (this only applies when both the client and the server use this or a newer version).
@changelog_1149_li
@changelog_1150_li
There is a new system property "h2.storeLocalTime" to avoid problems opening a database file in a timezone that has different daylight saving rules (see also below).
There is a new system property "h2.storeLocalTime" to avoid problems opening a database file in a timezone that has different daylight saving rules (see also below).
@changelog_1150_li
@changelog_1151_li
Date, time, and timestamp data type processing has been re-implemented. Time now supports nanoseconds resolution and now now supports a wider range (negative and large values), similar to PostgreSQL.
Date, time, and timestamp data type processing has been re-implemented. Time now supports nanoseconds resolution and now now supports a wider range (negative and large values), similar to PostgreSQL.
@changelog_1151_li
@changelog_1152_li
SQL statements with a non-breaking space were considered invalid.
SQL statements with a non-breaking space were considered invalid.
@changelog_1152_h2
@changelog_1153_h2
Version 1.3.157 (2011-06-25)
Version 1.3.157 (2011-06-25)
@changelog_1153_li
@changelog_1154_li
The syntax for CREATE TABLE ... AS SELECT ... has been changed: options such as NOT PERSISTENT are now before the query (AS SELECT), because otherwise they might be interpreted as a part of the query.
The syntax for CREATE TABLE ... AS SELECT ... has been changed: options such as NOT PERSISTENT are now before the query (AS SELECT), because otherwise they might be interpreted as a part of the query.
@changelog_1154_li
@changelog_1155_li
With version 1.3.156, the DB2 mode could not be used with CLOB and BLOB data.
With version 1.3.156, the DB2 mode could not be used with CLOB and BLOB data.
@changelog_1155_li
@changelog_1156_li
When upgrading from an older 1.3.x version to version 1.3.156, CLOB and BLOB data was lost in many cases.
When upgrading from an older 1.3.x version to version 1.3.156, CLOB and BLOB data was lost in many cases.
@changelog_1156_li
@changelog_1157_li
The optimization for COUNT(..) on columns that are not nullable was also used for COUNT(DISTINCT ..), which is incorrect.
The optimization for COUNT(..) on columns that are not nullable was also used for COUNT(DISTINCT ..), which is incorrect.
@changelog_1157_li
@changelog_1158_li
PgServer: non-admin users could not open a database.
PgServer: non-admin users could not open a database.
@changelog_1158_li
@changelog_1159_li
Non-admin users could not open a database using a mode (MODE=xxx) if the database was already open, even if the mode matched.
Non-admin users could not open a database using a mode (MODE=xxx) if the database was already open, even if the mode matched.
@changelog_1159_li
@changelog_1160_li
The SQL state of the following exceptions has been changed: From 90009, 90010, 90011 to 22007: "Cannot parse DATE/TIME/TIMESTAMP constant ...".
The SQL state of the following exceptions has been changed: From 90009, 90010, 90011 to 22007: "Cannot parse DATE/TIME/TIMESTAMP constant ...".
@changelog_1160_li
@changelog_1161_li
There is a problem when opening a database file in a timezone that has different daylight saving rules: the time part of dates where the daylight saving doesn't match will differ. This is not a problem within regions that use the same rules (such as, within USA, or within Europe), even if the timezone itself is different. As a workaround, export the database to a SQL script using the old timezone, and create a new database in the new timezone. The same problem occurs when accessing a database over TCP/IP if the client and server timezones use different rules, if an old server or client is used.
There is a problem when opening a database file in a timezone that has different daylight saving rules: the time part of dates where the daylight saving doesn't match will differ. This is not a problem within regions that use the same rules (such as, within USA, or within Europe), even if the timezone itself is different. As a workaround, export the database to a SQL script using the old timezone, and create a new database in the new timezone. The same problem occurs when accessing a database over TCP/IP if the client and server timezones use different rules, if an old server or client is used.
@changelog_1161_h2
@changelog_1162_h2
Version 1.3.156 (2011-06-17)
Version 1.3.156 (2011-06-17)
@changelog_1162_li
@changelog_1163_li
Issue 323: NullPointerException when using IN(...) with a function table.
Issue 323: NullPointerException when using IN(...) with a function table.
@changelog_1163_li
@changelog_1164_li
Clob.toString() and Blob.toString() now include the trace identifier.
Clob.toString() and Blob.toString() now include the trace identifier.
@changelog_1164_li
@changelog_1165_li
The SQL parser silently ignored characters such as '^' or '\'. Now a syntax error is thrown.
The SQL parser silently ignored characters such as '^' or '\'. Now a syntax error is thrown.
@changelog_1165_li
@changelog_1166_li
ROUND(..) now also works with just one parameter.
ROUND(..) now also works with just one parameter.
@changelog_1166_li
@changelog_1167_li
Access to system tables is now more restrictive for non-admin users (the tables can be still listed, but some of the data is not included).
Access to system tables is now more restrictive for non-admin users (the tables can be still listed, but some of the data is not included).
@changelog_1167_li
@changelog_1168_li
BLOB: InputStream.skip is now more efficient in embedded mode.
BLOB: InputStream.skip is now more efficient in embedded mode.
@changelog_1168_li
@changelog_1169_li
The default expression of a column may no longer reference the table, because a database with such a table couldn't be opened normally.
The default expression of a column may no longer reference the table, because a database with such a table couldn't be opened normally.
@changelog_1169_li
@changelog_1170_li
Referenced objects in check constraints could be dropped, which resulted in a database that can't be opened normally.
Referenced objects in check constraints could be dropped, which resulted in a database that can't be opened normally.
@changelog_1170_li
@changelog_1171_li
Improved Oracle compatibility for NVL2. Thanks again to litailang for the patch.
Improved Oracle compatibility for NVL2. Thanks again to litailang for the patch.
@changelog_1171_li
@changelog_1172_li
CSVREAD now supports the option 'preserveWhitespace'.
CSVREAD now supports the option 'preserveWhitespace'.
@changelog_1172_li
@changelog_1173_li
Recursive queries with many rows could throw an IndexOutOfBoundsException.
Recursive queries with many rows could throw an IndexOutOfBoundsException.
@changelog_1173_li
@changelog_1174_li
The auto-server mode can't be combined with an in-memory database. This invalid combination wasn't detected so far. Now trying to open a database in this way fails.
The auto-server mode can't be combined with an in-memory database. This invalid combination wasn't detected so far. Now trying to open a database in this way fails.
@changelog_1174_li
@changelog_1175_li
Improved performance for reading and writing date and time values.
Improved performance for reading and writing date and time values.
@changelog_1175_li
@changelog_1176_li
Java functions: array component types are now preserved, so that a ResultSet.getObject() will return Integer[] if the Java functions returns Integer[]. Thanks to Noel Grandin for the patch. Component types are transferred over the network, but not persisted in the database file as of now.
Java functions: array component types are now preserved, so that a ResultSet.getObject() will return Integer[] if the Java functions returns Integer[]. Thanks to Noel Grandin for the patch. Component types are transferred over the network, but not persisted in the database file as of now.
@changelog_1176_li
@changelog_1177_li
Recover tool: the script generated by the recover tool didn't work if fulltext search was used, because the triggers were created before the primary keys.
Recover tool: the script generated by the recover tool didn't work if fulltext search was used, because the triggers were created before the primary keys.
@changelog_1177_li
@changelog_1178_li
Issue 321: the database does not expect XA rollback without XA prepare (an exception was unnecessarily written into the .trace.db file).
Issue 321: the database does not expect XA rollback without XA prepare (an exception was unnecessarily written into the .trace.db file).
@changelog_1178_li
@changelog_1179_li
Read-only databases: some queries (such as distinct queries) tried to create temporary tables, which failed for read only databases.
Read-only databases: some queries (such as distinct queries) tried to create temporary tables, which failed for read only databases.
@changelog_1179_li
@changelog_1180_li
This database no longer uses finalize() except for temporary files. The system property "h2.runFinalize" is no longer supported. Unclosed connections are still detected, but the opening stack trace is now collected only if connections are not closed repeatedly (starting with the second unclosed connection). To detect unclosed connections, a PhantomReference is used.
This database no longer uses finalize() except for temporary files. The system property "h2.runFinalize" is no longer supported. Unclosed connections are still detected, but the opening stack trace is now collected only if connections are not closed repeatedly (starting with the second unclosed connection). To detect unclosed connections, a PhantomReference is used.
@changelog_1180_li
@changelog_1181_li
Issue 322: Left joins didn't work when used as subquery in the form clause.
Issue 322: Left joins didn't work when used as subquery in the form clause.
@changelog_1181_li
@changelog_1182_li
A prepared statement if type CALL that returned a result set could throw a NullPointerException if executed multiple times.
A prepared statement if type CALL that returned a result set could throw a NullPointerException if executed multiple times.
@changelog_1182_li
@changelog_1183_li
The following built-in functions were marked as deterministic and therefore not re-executed when using in a prepared statement: LOCK_TIMEOUT, LINK_SCHEMA, CANCEL_SESSION, FILE_READ.
The following built-in functions were marked as deterministic and therefore not re-executed when using in a prepared statement: LOCK_TIMEOUT, LINK_SCHEMA, CANCEL_SESSION, FILE_READ.
@changelog_1183_li
@changelog_1184_li
Count on a column that can not be null is now optimized to COUNT(*). Thanks a lot to Ross Judson for providing a patch and test case!
Count on a column that can not be null is now optimized to COUNT(*). Thanks a lot to Ross Judson for providing a patch and test case!
@changelog_1184_li
@changelog_1185_li
The following prepared statements are now cached as well: insert, update, delete, call, merge, and transactional commands.
The following prepared statements are now cached as well: insert, update, delete, call, merge, and transactional commands.
@changelog_1185_li
@changelog_1186_li
The built-in connection pool is now a bit faster.
The built-in connection pool is now a bit faster.
@changelog_1186_li
@changelog_1187_li
The scale was not set correctly in some cases when using CREATE TABLE AS SELECT if there was no explicit column definition.
The scale was not set correctly in some cases when using CREATE TABLE AS SELECT if there was no explicit column definition.
@changelog_1187_li
@changelog_1188_li
When trying to connect to a server using TCP/IP failed, it will retry at most until the timeout. Before, it was the timeout multiplied with the retry count.
When trying to connect to a server using TCP/IP failed, it will retry at most until the timeout. Before, it was the timeout multiplied with the retry count.
@changelog_1188_h2
@changelog_1189_h2
Version 1.3.155 (2011-05-27)
Version 1.3.155 (2011-05-27)
@changelog_1189_li
@changelog_1190_li
When altering a table with triggers, new triggers are created and initialized with a table name that ends with tableName_COPY_x_y. The plan is that this will not be required in future versions.
When altering a table with triggers, new triggers are created and initialized with a table name that ends with tableName_COPY_x_y. The plan is that this will not be required in future versions.
@changelog_1190_li
@changelog_1191_li
If some of the file system operations failed, System.gc() was called in a loop. Now it is called once at most.
If some of the file system operations failed, System.gc() was called in a loop. Now it is called once at most.
@changelog_1191_li
@changelog_1192_li
Triggers (including the fulltext search) could throw the exception 'Unexpected code path' in Session.log.
Triggers (including the fulltext search) could throw the exception 'Unexpected code path' in Session.log.
@changelog_1192_li
@changelog_1193_li
CURRENT_TIMESTAMP() and so on now return the same value within a transaction.
CURRENT_TIMESTAMP() and so on now return the same value within a transaction.
@changelog_1193_li
@changelog_1194_li
The statement CALL no longer converts an ARRAY return value to a list of values. Now an ARRAY is returned.
The statement CALL no longer converts an ARRAY return value to a list of values. Now an ARRAY is returned.
@changelog_1194_li
@changelog_1195_li
VALUES is now supported as a standalone command and as a table source: SELECT * FROM (VALUES(1, 'Hello'), (2, 'World')) AS V;
VALUES is now supported as a standalone command and as a table source: SELECT * FROM (VALUES(1, 'Hello'), (2, 'World')) AS V;
@changelog_1195_li
@changelog_1196_li
TIMESTAMPADD is now an alias for DATEADD. Most SQL_TSI_ constants are now supported for for TIMESTAMPADD and TIMESTAMPDIFF (all except SQL_TSI_QUARTER and SQL_TSI_FRAC_SECOND).
TIMESTAMPADD is now an alias for DATEADD. Most SQL_TSI_ constants are now supported for for TIMESTAMPADD and TIMESTAMPDIFF (all except SQL_TSI_QUARTER and SQL_TSI_FRAC_SECOND).
@changelog_1196_li
@changelog_1197_li
Issue 313: NullPointerException in select query with a subquery or view.
Issue 313: NullPointerException in select query with a subquery or view.
@changelog_1197_li
@changelog_1198_li
Native fulltext search: the characters '<', '>', and '\' are now also whitespace characters. Also, the list of whitespace characters can be changed using FullText.setWhitespaceChars(conn, ...)
Native fulltext search: the characters '<', '>', and '\' are now also whitespace characters. Also, the list of whitespace characters can be changed using FullText.setWhitespaceChars(conn, ...)
@changelog_1198_li
@changelog_1199_li
When reading from the classpath (for example read_file('classpath:logo.png')), now the content class loader is used if the resource can't be found otherwise.
When reading from the classpath (for example read_file('classpath:logo.png')), now the content class loader is used if the resource can't be found otherwise.
@changelog_1199_li
@changelog_1200_li
The statement "script drop" create a script that couldn't be executed if a table contained a reference to a user defined function.
The statement "script drop" create a script that couldn't be executed if a table contained a reference to a user defined function.
@changelog_1200_li
@changelog_1201_li
Opening a database with both multi-threaded mode and lock mode 0 (disable locking) was possible (but only once), even thought it does not work properly. Now it is no longer allowed.
Opening a database with both multi-threaded mode and lock mode 0 (disable locking) was possible (but only once), even thought it does not work properly. Now it is no longer allowed.
@changelog_1201_li
@changelog_1202_li
LOB objects are now deleted (and the empty space is reused) when the transaction is committed. So far, the space wasn't re-used until the connection was closed.
LOB objects are now deleted (and the empty space is reused) when the transaction is committed. So far, the space wasn't re-used until the connection was closed.
@changelog_1202_li
@changelog_1203_li
SCRIPT DROP did not use the cascade option for table, which would cause problems if a view was dropped before a table it depends on. Now the cascade option is used.
SCRIPT DROP did not use the cascade option for table, which would cause problems if a view was dropped before a table it depends on. Now the cascade option is used.
@changelog_1203_li
@changelog_1204_li
The query plan of queries with subqueries that contain nested joins was wrong. This could result in syntax exceptions for correct queries. Example: select 1 from (select 2 from ((test t1 inner join test t2 on t1.id=t2.id) inner join test t3 on t3.id=t1.id)) x;
The query plan of queries with subqueries that contain nested joins was wrong. This could result in syntax exceptions for correct queries. Example: select 1 from (select 2 from ((test t1 inner join test t2 on t1.id=t2.id) inner join test t3 on t3.id=t1.id)) x;
@changelog_1204_li
@changelog_1205_li
DatabaseEventListener.init was called with a null url when using the server mode.
DatabaseEventListener.init was called with a null url when using the server mode.
@changelog_1205_li
@changelog_1206_li
Support for the function LN (an alias for LOG).
Support for the function LN (an alias for LOG).
@changelog_1206_li
@changelog_1207_li
Support for the function CEIL (an alias for CEILING).
Support for the function CEIL (an alias for CEILING).
@changelog_1207_li
@changelog_1208_li
Issue 315: Access to LOBs could cause a Java level deadlock.
Issue 315: Access to LOBs could cause a Java level deadlock.
@changelog_1208_li
@changelog_1209_li
Support for the ICU4J collator.
Support for the ICU4J collator.
@changelog_1209_li
@changelog_1210_li
Improved Oracle compatibility: support for NVL2. Thanks to litailang for the patch!
Improved Oracle compatibility: support for NVL2. Thanks to litailang for the patch!
@changelog_1210_li
@changelog_1211_li
Improved PostgreSQL compatibility: support for RANDOM() in addition to RAND().
Improved PostgreSQL compatibility: support for RANDOM() in addition to RAND().
@changelog_1211_li
@changelog_1212_li
There was a classloader memory leak problem because a class contained a static references to an exception (including stack trace).
There was a classloader memory leak problem because a class contained a static references to an exception (including stack trace).
@changelog_1212_li
@changelog_1213_li
Split file system: truncating a file now deletes the parts in reverse order, so that the file list is consistent if the process is interrupted while truncating.
Split file system: truncating a file now deletes the parts in reverse order, so that the file list is consistent if the process is interrupted while truncating.
@changelog_1213_li
@changelog_1214_li
The H2 JDBC client can now be used in an unsigned Applet. The problem was that System.getProperty throws a SecurityException, which is now ignored.
The H2 JDBC client can now be used in an unsigned Applet. The problem was that System.getProperty throws a SecurityException, which is now ignored.
@changelog_1214_li
@changelog_1215_li
The condition "in(select ...)" did not work correctly if the subquery could not be converted to a "distinct" query, as in: "select * from dual where x in (select x from dual group by x order by max(x))". Now the subquery needs to be made distinct manually if this optimization is needed.
The condition "in(select ...)" did not work correctly if the subquery could not be converted to a "distinct" query, as in: "select * from dual where x in (select x from dual group by x order by max(x))". Now the subquery needs to be made distinct manually if this optimization is needed.
@changelog_1215_li
@changelog_1216_li
In the last release, the error code for "Wrong user name or password" was still 08004 instead of 28000, which resulted in the wrong error message.
In the last release, the error code for "Wrong user name or password" was still 08004 instead of 28000, which resulted in the wrong error message.
@changelog_1216_li
@changelog_1217_li
In some cases, creating a new table or altering an existing table threw the exception: Unique index or primary key violation: "PRIMARY KEY ON """".PAGE_INDEX".
In some cases, creating a new table or altering an existing table threw the exception: Unique index or primary key violation: "PRIMARY KEY ON """".PAGE_INDEX".
@changelog_1217_li
@changelog_1218_li
The Shell tool no longer supports the built-in command "show", because it is a legal SQL statement for H2 and MySQL. However, the "describe" command is still supported, and now lists all tables if called without parameter.
The Shell tool no longer supports the built-in command "show", because it is a legal SQL statement for H2 and MySQL. However, the "describe" command is still supported, and now lists all tables if called without parameter.
@changelog_1218_li
@changelog_1219_li
The sorted insert mode (as in "insert into ... direct sorted select") did not work for not-persisted tables in a persisted database. It threw a ClassCastException.
The sorted insert mode (as in "insert into ... direct sorted select") did not work for not-persisted tables in a persisted database. It threw a ClassCastException.
@changelog_1219_li
@changelog_1220_li
Issue 308: Statement.getGeneratedKeys() now returns an empty result set if no key was generated.
Issue 308: Statement.getGeneratedKeys() now returns an empty result set if no key was generated.
@changelog_1220_li
@changelog_1221_li
The h2small.jar (created with build jarSmall) included the Android API. This has been removed, shrinking the jar file by 21 KB.
The h2small.jar (created with build jarSmall) included the Android API. This has been removed, shrinking the jar file by 21 KB.
@changelog_1221_li
@changelog_1222_li
When creating a table, the precision must now be at least as large as the scale.
When creating a table, the precision must now be at least as large as the scale.
@changelog_1222_li
@changelog_1223_li
Support for Java 1.3 and Java 1.4 has been removed.
Support for Java 1.3 and Java 1.4 has been removed.
@changelog_1223_li
@changelog_1224_li
Improved error message for syntax error: the list of expected tokens was sometimes not set correctly.
Improved error message for syntax error: the list of expected tokens was sometimes not set correctly.
@changelog_1224_li
@changelog_1225_li
Database file growth can now be limited using the database setting PAGE_STORE_MAX_GROWTH. Slower growth may slow down operation, but speed up closing database.
Database file growth can now be limited using the database setting PAGE_STORE_MAX_GROWTH. Slower growth may slow down operation, but speed up closing database.
@changelog_1225_li
@changelog_1226_li
A read only database with writable linked tables could lead to a DATABASE_IS_READ_ONLY (90097) error. This is fixed now.
A read only database with writable linked tables could lead to a DATABASE_IS_READ_ONLY (90097) error. This is fixed now.
@changelog_1226_h2
@changelog_1227_h2
Version 1.3.154 (2011-04-04)
Version 1.3.154 (2011-04-04)
@changelog_1227_li
@changelog_1228_li
The SQL state of the following exceptions has been changed: From 90005 to 22001: "Value too long for column ...: ...". From 90039 to 22003: "The value is too large for the precision ..." is merged with "Numeric value out of range". From 90110 to 22003: "... out of range" is merged with "Numeric value out of range". From 90021 to 22018: "Data conversion error converting ...". From 90006 to 23502: "NULL not allowed for column ...". From 23003 to 23503: "Referential integrity constraint violation: ...". From 23001 to 23505: "Unique index or primary key violation: ...". From 23002 to 23506: "Referential integrity constraint violation: ...". From 90056 to 23507: "No default value is set for column ...". From 23000 to 23513: "Check constraint violation: ...". From 08004 to 28000: "Wrong user name or password". From 90051 to 57014: "Statement was canceled or the session timed out".
The SQL state of the following exceptions has been changed: From 90005 to 22001: "Value too long for column ...: ...". From 90039 to 22003: "The value is too large for the precision ..." is merged with "Numeric value out of range". From 90110 to 22003: "... out of range" is merged with "Numeric value out of range". From 90021 to 22018: "Data conversion error converting ...". From 90006 to 23502: "NULL not allowed for column ...". From 23003 to 23503: "Referential integrity constraint violation: ...". From 23001 to 23505: "Unique index or primary key violation: ...". From 23002 to 23506: "Referential integrity constraint violation: ...". From 90056 to 23507: "No default value is set for column ...". From 23000 to 23513: "Check constraint violation: ...". From 08004 to 28000: "Wrong user name or password". From 90051 to 57014: "Statement was canceled or the session timed out".
@changelog_1228_li
@changelog_1229_li
The H2 Console now detects unsupported command line options. (In the future, it will be combined with the Server tool.)
The H2 Console now detects unsupported command line options. (In the future, it will be combined with the Server tool.)
@changelog_1229_li
@changelog_1230_li
MySQL compatibility: SHOW COLUMN FOR schemaName.columnName.
MySQL compatibility: SHOW COLUMN FOR schemaName.columnName.
@changelog_1230_li
@changelog_1231_li
DatabaseMetaData.getCrossReference now also lists the name of the primary index (PK_NAME).
DatabaseMetaData.getCrossReference now also lists the name of the primary index (PK_NAME).
@changelog_1231_li
@changelog_1232_li
If the database contained many CLOB or BLOB values, then closing a connection was very slow. Reason: was that when closing a connection, the temporary CLOB and BLOB values for this connection were removed, but there was no index on this column. For existing databases with many CLOB and BLOB values, creating the index may take a few seconds. The index is added to existing databases automatically.
If the database contained many CLOB or BLOB values, then closing a connection was very slow. Reason: was that when closing a connection, the temporary CLOB and BLOB values for this connection were removed, but there was no index on this column. For existing databases with many CLOB and BLOB values, creating the index may take a few seconds. The index is added to existing databases automatically.
@changelog_1232_li
@changelog_1233_li
If a CLOB or BLOB was copied into the same table using INSERT INTO X ... SELECT ... FROM X, and then the original row was deleted, then the copied value was also deleted. This could also result in an ArrayIndexOutOfBoundsException on checkpoint or when closing the database.
If a CLOB or BLOB was copied into the same table using INSERT INTO X ... SELECT ... FROM X, and then the original row was deleted, then the copied value was also deleted. This could also result in an ArrayIndexOutOfBoundsException on checkpoint or when closing the database.
@changelog_1233_li
@changelog_1234_li
Improved performance (up to 10%) due to changed synchronization in the page store.
Improved performance (up to 10%) due to changed synchronization in the page store.
@changelog_1234_li
@changelog_1235_li
Reading a resource from the classpath didn't work if there was a leading slash (classpath:/org/...). Now resources can be loaded with or without leading slash.
Reading a resource from the classpath didn't work if there was a leading slash (classpath:/org/...). Now resources can be loaded with or without leading slash.
@changelog_1235_li
@changelog_1236_li
Support INSERT INTO TEST SET ID = 1, NAME = 'World' (MySQL compatibility).
Support INSERT INTO TEST SET ID = 1, NAME = 'World' (MySQL compatibility).
@changelog_1236_li
@changelog_1237_li
Issue 304: The condition [NOT] IN (SELECT ...) could throw the exception "Unexpected code path" if the subquery contained ORDER BY.
Issue 304: The condition [NOT] IN (SELECT ...) could throw the exception "Unexpected code path" if the subquery contained ORDER BY.
@changelog_1237_li
@changelog_1238_li
ALTER TABLE ALTER ADD / REMOVE /ALTER COLUMN dropped some dependent objects (access rights, triggers) of views that depend on the modified table.
ALTER TABLE ALTER ADD / REMOVE /ALTER COLUMN dropped some dependent objects (access rights, triggers) of views that depend on the modified table.
@changelog_1238_li
@changelog_1239_li
CREATE OR REPLACE VIEW dropped some dependent objects (access rights, triggers) if the view already existed before.
CREATE OR REPLACE VIEW dropped some dependent objects (access rights, triggers) if the view already existed before.
@changelog_1239_li
@changelog_1240_li
New aggregate function HISTOGRAM to calculate the histogram. The plan is to use this function is only used internally when running ANALYZE to generate the histogram that is then used by the query optimizer.
New aggregate function HISTOGRAM to calculate the histogram. The plan is to use this function is only used internally when running ANALYZE to generate the histogram that is then used by the query optimizer.
@changelog_1240_li
@changelog_1241_li
New system function TRUNCATE_VALUE to truncate a value to the required precision. This is the same as for CAST, but without changing the data type, and support for truncating decimal values. (The main use case for this function is to build a histogram of the truncated values). Now BINARY, BLOB, and CLOB can be truncated / cast efficiently as well.
New system function TRUNCATE_VALUE to truncate a value to the required precision. This is the same as for CAST, but without changing the data type, and support for truncating decimal values. (The main use case for this function is to build a histogram of the truncated values). Now BINARY, BLOB, and CLOB can be truncated / cast efficiently as well.
@changelog_1241_li
@changelog_1242_li
The precision of an ARRAY value is now the sum of the precision of all elements, and result set values have the precision Integer.MAX_VALUE.
The precision of an ARRAY value is now the sum of the precision of all elements, and result set values have the precision Integer.MAX_VALUE.
@changelog_1242_li
@changelog_1243_li
CAST(x AS VARCHAR_IGNORECASE(y) / CHAR(y)) returned a VARCHAR if the new precision was lower than the old precision.
CAST(x AS VARCHAR_IGNORECASE(y) / CHAR(y)) returned a VARCHAR if the new precision was lower than the old precision.
@changelog_1243_li
@changelog_1244_li
SHUTDOWN DEFRAG didn't defragment the database completely if there was a unique hash index for a memory table.
SHUTDOWN DEFRAG didn't defragment the database completely if there was a unique hash index for a memory table.
@changelog_1244_li
@changelog_1245_li
There were some smaller changes in the encrypting file system (work in progress).
There were some smaller changes in the encrypting file system (work in progress).
@changelog_1245_li
@changelog_1246_li
Some time and timezone functions didn't support years before 1.
Some time and timezone functions didn't support years before 1.
#H2 Console: when editing a row, an empty varchar column was replaced with a single space.
@changelog_1003_li
@changelog_1003_li
#Some nested joins could not be executed, for example: select * from (select * from (select * from a) a right join b b) c;
#Lukas Eder has updated the jOOQ documentation.
@changelog_1004_li
@changelog_1004_li
#MS SQL Server compatibility: ISNULL is now an alias for IFNULL.
#Some nested joins could not be executed, for example: select * from (select * from (select * from a) a right join b b) c;
@changelog_1005_li
@changelog_1005_li
#Terrence Huang has completed the translation of the H2 Console tool to Chinese. Thanks a lot!
#MS SQL Server compatibility: ISNULL is now an alias for IFNULL.
@changelog_1006_li
@changelog_1006_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.
#Terrence Huang has completed the translation of the H2 Console tool to Chinese. Thanks a lot!
@changelog_1007_li
@changelog_1007_li
#In the trace file, the query execution time was incorrect in some cases, specially for the statement SET TRACE_LEVEL_FILE 2.
#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_1008_li
@changelog_1008_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.
#In the trace file, the query execution time was incorrect in some cases, specially for the statement SET TRACE_LEVEL_FILE 2.
@changelog_1009_li
@changelog_1009_li
#Then reading from a resource using the prefix "classpath:", the ContextClassLoader is now used if the resource can't be read otherwise.
#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_1010_li
@changelog_1010_li
#DatabaseEventListener now calls setProgress whenever a statement starts and ends.
#Then reading from a resource using the prefix "classpath:", the ContextClassLoader is now used if the resource can't be read otherwise.
@changelog_1011_li
@changelog_1011_li
#DatabaseEventListener now calls setProgress periodically while a statement is running.
#DatabaseEventListener now calls setProgress whenever a statement starts and ends.
@changelog_1012_li
@changelog_1012_li
#The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME.
#DatabaseEventListener now calls setProgress periodically while a statement is running.
@changelog_1013_li
@changelog_1013_li
#Issue 378: when using views, the wrong values were bound to a parameter in some cases.
#The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME.
@changelog_1014_li
@changelog_1014_li
#Terrence Huang has translated the error messages to Chinese. Thanks a lot!
#Issue 378: when using views, the wrong values were bound to a parameter in some cases.
@changelog_1015_li
@changelog_1015_li
#TRUNC was added as an alias for TRUNCATE.
#Terrence Huang has translated the error messages to Chinese. Thanks a lot!
@changelog_1016_li
@changelog_1016_li
#Small optimisation for accessing result values by column name.
#TRUNC was added as an alias for TRUNCATE.
@changelog_1017_li
@changelog_1017_li
#Fix for bug in Statement#getMoreResults(int)
#Small optimisation for accessing result values by column name.
@changelog_1018_li
@changelog_1018_li
#Fix for bug in Statement#getMoreResults(int)
@changelog_1019_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_1019_h2
@changelog_1020_h2
#Version 1.3.166 (2012-04-08)
#Version 1.3.166 (2012-04-08)
@changelog_1020_li
@changelog_1021_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_1021_li
@changelog_1022_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_1022_li
@changelog_1023_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_1023_li
@changelog_1024_li
#Invalid connection settings are now detected.
#Invalid connection settings are now detected.
@changelog_1024_li
@changelog_1025_li
#Issue 387: WHERE condition getting pushed into sub-query with LIMIT.
#Issue 387: WHERE condition getting pushed into sub-query with LIMIT.
@changelog_1025_h2
@changelog_1026_h2
#Version 1.3.165 (2012-03-18)
#Version 1.3.165 (2012-03-18)
@changelog_1026_li
@changelog_1027_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_1027_li
@changelog_1028_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_1028_li
@changelog_1029_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_1029_li
@changelog_1030_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_1030_li
@changelog_1031_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_1031_li
@changelog_1032_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_1032_li
@changelog_1033_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_1033_li
@changelog_1034_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_1034_li
@changelog_1035_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_1035_li
@changelog_1036_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_1036_li
@changelog_1037_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_1037_li
@changelog_1038_li
#Issue 362: support LIMIT in UPDATE statements.
#Issue 362: support LIMIT in UPDATE statements.
@changelog_1038_li
@changelog_1039_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_1039_li
@changelog_1040_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_1040_li
@changelog_1041_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_1041_li
@changelog_1042_li
#PostgreSQL compatibility: LOG(x) is base 10 in the PostgreSQL mode.
#PostgreSQL compatibility: LOG(x) is base 10 in the PostgreSQL mode.
@changelog_1042_h2
@changelog_1043_h2
#Version 1.3.164 (2012-02-03)
#Version 1.3.164 (2012-02-03)
@changelog_1043_li
@changelog_1044_li
#New built-in function ARRAY_CONTAINS.
#New built-in function ARRAY_CONTAINS.
@changelog_1044_li
@changelog_1045_li
#Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
#Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
@changelog_1045_li
@changelog_1046_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_1046_li
@changelog_1047_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_1047_li
@changelog_1048_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_1048_li
@changelog_1049_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_1049_li
@changelog_1050_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_1050_li
@changelog_1051_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_1051_li
@changelog_1052_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_1052_li
@changelog_1053_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_1053_li
@changelog_1054_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_1054_li
@changelog_1055_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_1055_li
@changelog_1056_li
#SimpleResultSet: updating a result set is now supported.
#SimpleResultSet: updating a result set is now supported.
@changelog_1056_li
@changelog_1057_li
#Database URL: extra semicolons are not supported.
#Database URL: extra semicolons are not supported.
@changelog_1057_h2
@changelog_1058_h2
#Version 1.3.163 (2011-12-30)
#Version 1.3.163 (2011-12-30)
@changelog_1058_li
@changelog_1059_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_1059_li
@changelog_1060_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_1060_li
@changelog_1061_li
#XMLTEXT now supports an optional parameter to escape newlines.
#XMLTEXT now supports an optional parameter to escape newlines.
@changelog_1061_li
@changelog_1062_li
#XMLNODE now support an optional parameter to disable indentation.
#XMLNODE now support an optional parameter to disable indentation.
@changelog_1062_li
@changelog_1063_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_1063_li
@changelog_1064_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_1064_li
@changelog_1065_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_1065_li
@changelog_1066_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_1066_h2
@changelog_1067_h2
#Version 1.3.162 (2011-11-26)
#Version 1.3.162 (2011-11-26)
@changelog_1067_li
@changelog_1068_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_1068_li
@changelog_1069_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_1069_li
@changelog_1070_li
#Oracle compatibility: support for DECODE(...).
#Oracle compatibility: support for DECODE(...).
@changelog_1070_li
@changelog_1071_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_1071_li
@changelog_1072_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_1072_li
@changelog_1073_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_1073_li
@changelog_1074_li
#Issue 334: SimpleResultSet.getString now also works for Clob columns.
#Issue 334: SimpleResultSet.getString now also works for Clob columns.
@changelog_1074_li
@changelog_1075_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_1075_li
@changelog_1076_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_1076_li
@changelog_1077_li
#Server.createTcpServer, createPgServer, createWebServer: invalid arguments are now detected.
#Server.createTcpServer, createPgServer, createWebServer: invalid arguments are now detected.
@changelog_1077_li
@changelog_1078_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_1078_li
@changelog_1079_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_1079_li
@changelog_1080_li
#A NullPointerException could occur in TableView.isDeterministic for invalid views.
#A NullPointerException could occur in TableView.isDeterministic for invalid views.
@changelog_1080_li
@changelog_1081_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_1081_li
@changelog_1082_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_1082_li
@changelog_1083_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_1083_li
@changelog_1084_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_1084_h2
@changelog_1085_h2
#Version 1.3.161 (2011-10-28)
#Version 1.3.161 (2011-10-28)
@changelog_1085_li
@changelog_1086_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_1086_li
@changelog_1087_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_1087_li
@changelog_1088_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_1088_li
@changelog_1089_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_1089_li
@changelog_1090_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_1090_li
@changelog_1091_li
#Sequences with cache size smaller than 0 did not work correctly.
#Sequences with cache size smaller than 0 did not work correctly.
@changelog_1091_li
@changelog_1092_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_1092_li
@changelog_1093_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_1093_li
@changelog_1094_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_1094_li
@changelog_1095_li
#Issue 347: the RunScript and Shell tools now ignore empty statements.
#Issue 347: the RunScript and Shell tools now ignore empty statements.
@changelog_1095_li
@changelog_1096_li
#Issue 246: improved error message for data conversion problems.
#Issue 246: improved error message for data conversion problems.
@changelog_1096_li
@changelog_1097_li
#Issue 344: the build now supports a custom Maven repository location.
#Issue 344: the build now supports a custom Maven repository location.
@changelog_1097_li
@changelog_1098_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_1098_li
@changelog_1099_li
#SimpleResultSet now supports getColumnTypeName and getColumnClassName.
#SimpleResultSet now supports getColumnTypeName and getColumnClassName.
@changelog_1099_li
@changelog_1100_li
#SimpleResultSet now has minimal BLOB and CLOB support.
#SimpleResultSet now has minimal BLOB and CLOB support.
@changelog_1100_li
@changelog_1101_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_1101_li
@changelog_1102_li
#The Polish translation has been improved by Jarosław Kokociński.
#The Polish translation has been improved by Jarosław Kokociński.
@changelog_1102_li
@changelog_1103_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_1103_li
@changelog_1104_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_1104_li
@changelog_1105_li
#Improved compatibility with the Java 7 FileSystem abstraction.
#Improved compatibility with the Java 7 FileSystem abstraction.
@changelog_1105_h2
@changelog_1106_h2
#Version 1.3.160 (2011-09-11)
#Version 1.3.160 (2011-09-11)
@changelog_1106_li
@changelog_1107_li
#Computed columns could not refer to itself.
#Computed columns could not refer to itself.
@changelog_1107_li
@changelog_1108_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_1108_li
@changelog_1109_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_1109_li
@changelog_1110_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_1110_li
@changelog_1111_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_1111_li
@changelog_1112_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_1112_li
@changelog_1113_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_1113_li
@changelog_1114_li
#Issue 329: CASE expression: data type problem is not detected.
#Issue 329: CASE expression: data type problem is not detected.
@changelog_1114_li
@changelog_1115_li
#Issue 311: File lock mode serialized: selecting the next value from a sequence didn't work after a pause, because the database thought this is a read-only operation.
#Issue 311: File lock mode serialized: selecting the next value from a sequence didn't work after a pause, because the database thought this is a read-only operation.
@changelog_1115_h2
@changelog_1116_h2
#Version 1.3.159 (2011-08-13)
#Version 1.3.159 (2011-08-13)
@changelog_1116_li
@changelog_1117_li
#Creating a temporary table with the option 'transactional' will now also create the indexes in transactional mode, if the indexes are included in the 'create table' statement as follows: "create local temporary table temp(id int primary key, name varchar, constraint x index(name)) transactional".
#Creating a temporary table with the option 'transactional' will now also create the indexes in transactional mode, if the indexes are included in the 'create table' statement as follows: "create local temporary table temp(id int primary key, name varchar, constraint x index(name)) transactional".
@changelog_1117_li
@changelog_1118_li
#The database file size grows now 35%, but at most 256 MB at a time.
#The database file size grows now 35%, but at most 256 MB at a time.
@changelog_1118_li
@changelog_1119_li
#Improved error message on network configuration problems.
#Improved error message on network configuration problems.
@changelog_1119_li
@changelog_1120_li
#The build now support an offline build using ./build.sh offline. This will list the required dependencies if jar files are missing.
#The build now support an offline build using ./build.sh offline. This will list the required dependencies if jar files are missing.
@changelog_1120_li
@changelog_1121_li
#The BLOB / CLOB data was dropped a little bit before the table was dropped. This could cause "lob not found" errors when the process was killed while a table was dropped.
#The BLOB / CLOB data was dropped a little bit before the table was dropped. This could cause "lob not found" errors when the process was killed while a table was dropped.
@changelog_1121_li
@changelog_1122_li
#"group_concat(distinct ...)" did not work correctly in a view or subquery (the 'distinct' was lost). Example: select * from (select group_concat(distinct 1) from system_range(1, 3));
#"group_concat(distinct ...)" did not work correctly in a view or subquery (the 'distinct' was lost). Example: select * from (select group_concat(distinct 1) from system_range(1, 3));
@changelog_1122_li
@changelog_1123_li
#Database URLs can now be re-mapped to another URL using the system property "h2.urlMap", which points to a properties file with database URL mappings.
#Database URLs can now be re-mapped to another URL using the system property "h2.urlMap", which points to a properties file with database URL mappings.
@changelog_1123_li
@changelog_1124_li
#When using InputStream.skip, trying to read past the end of a BLOB failed with the exception "IO Exception: Missing lob entry: ..." [90028-...].
#When using InputStream.skip, trying to read past the end of a BLOB failed with the exception "IO Exception: Missing lob entry: ..." [90028-...].
@changelog_1124_li
@changelog_1125_li
#The in-memory file system "memFS:" now has limited support for directories.
#The in-memory file system "memFS:" now has limited support for directories.
@changelog_1125_li
@changelog_1126_li
#To test recovery, append ;RECOVER_TEST=64 to the database URL. This will simulate an application crash after each 64 writes to the database file. A log file named databaseName.h2.db.log is created that lists the operations. The recovery is tested using an in-memory file system, that means it may require a larger heap setting.
#To test recovery, append ;RECOVER_TEST=64 to the database URL. This will simulate an application crash after each 64 writes to the database file. A log file named databaseName.h2.db.log is created that lists the operations. The recovery is tested using an in-memory file system, that means it may require a larger heap setting.
@changelog_1126_li
@changelog_1127_li
#Converting a hex string to a byte array is now faster.
#Converting a hex string to a byte array is now faster.
@changelog_1127_li
@changelog_1128_li
#The SQL statement "shutdown defrag" could corrupt the database if the process was killed while the shutdown was in progress. The same problem could occur when the database setting "defrag_always" was used.
#The SQL statement "shutdown defrag" could corrupt the database if the process was killed while the shutdown was in progress. The same problem could occur when the database setting "defrag_always" was used.
@changelog_1128_h2
@changelog_1129_h2
#Version 1.3.158 (2011-07-17)
#Version 1.3.158 (2011-07-17)
@changelog_1129_li
@changelog_1130_li
#Fulltext search (native): after re-opening the connection once the fulltext index was created, a transaction rollback did not roll back the modifications in the index.
#Fulltext search (native): after re-opening the connection once the fulltext index was created, a transaction rollback did not roll back the modifications in the index.
@changelog_1130_li
@changelog_1131_li
#Support for ROW_NUMBER() OVER() as an alias for ROWNUM() for compatibility with PostgreSQL and Apache Derby.
#Support for ROW_NUMBER() OVER() as an alias for ROWNUM() for compatibility with PostgreSQL and Apache Derby.
@changelog_1131_li
@changelog_1132_li
#Issue 325: a deadlock in the fulltext search could occur if the connection that was used while initializing the fulltext search was later used to query the database. This was actually not only a problem for fulltext search, but also for other triggers that used the initializing connection later on.
#Issue 325: a deadlock in the fulltext search could occur if the connection that was used while initializing the fulltext search was later used to query the database. This was actually not only a problem for fulltext search, but also for other triggers that used the initializing connection later on.
@changelog_1132_li
@changelog_1133_li
#DATABASE_TO_UPPER: when set to false, all identifier names (table names, column names) are case sensitive (except aggregate, built-in functions, data types, and keywords). This is for improved compatibility with MySQL and PostgreSQL.
#DATABASE_TO_UPPER: when set to false, all identifier names (table names, column names) are case sensitive (except aggregate, built-in functions, data types, and keywords). This is for improved compatibility with MySQL and PostgreSQL.
@changelog_1133_li
@changelog_1134_li
#When upgrading from an older 1.3.x version to version 1.3.157, when using BLOB or CLOB data, the database could only be opened once.
#When upgrading from an older 1.3.x version to version 1.3.157, when using BLOB or CLOB data, the database could only be opened once.
@changelog_1134_li
@changelog_1135_li
#SUM on a boolean expression will now count the number of 'true' rows.
#SUM on a boolean expression will now count the number of 'true' rows.
@changelog_1135_li
@changelog_1136_li
#Simplified test cases using assertThrows(...).
#Simplified test cases using assertThrows(...).
@changelog_1136_li
@changelog_1137_li
#A Java function that returns a result set that was generated using the provided connection could cause an internal error in some cases. Now such result sets are copied early on.
#A Java function that returns a result set that was generated using the provided connection could cause an internal error in some cases. Now such result sets are copied early on.
@changelog_1137_li
@changelog_1138_li
#Data type RESULT_SET: information_schema.function_aliases returned type 0; now type -10 is returned (the same as Oracle: OracleTypes.CURSOR = -10).
#Data type RESULT_SET: information_schema.function_aliases returned type 0; now type -10 is returned (the same as Oracle: OracleTypes.CURSOR = -10).
@changelog_1138_li
@changelog_1139_li
#Data type RESULT_SET: tables with columns of type RESULT_SET could be created, but no data could be persisted in this column.
#Data type RESULT_SET: tables with columns of type RESULT_SET could be created, but no data could be persisted in this column.
@changelog_1139_li
@changelog_1140_li
#H2 Console: improved system tray icon for Mac OS X (transparent background).
#H2 Console: improved system tray icon for Mac OS X (transparent background).
@changelog_1140_li
@changelog_1141_li
#String.toUpperCase() was used a few places, which is problematic when using the Turkish locale. The method has been replaced with toUpperCase(Locale.ENGLISH) to solve such problems.
#String.toUpperCase() was used a few places, which is problematic when using the Turkish locale. The method has been replaced with toUpperCase(Locale.ENGLISH) to solve such problems.
@changelog_1141_li
@changelog_1142_li
#Shell tool: the built-in command "distinct" has been removed (use the SQL statements "show tables" / "show columns from tableName" instead). The result set formatting has been improved.
#Shell tool: the built-in command "distinct" has been removed (use the SQL statements "show tables" / "show columns from tableName" instead). The result set formatting has been improved.
@changelog_1142_li
@changelog_1143_li
#MERGE: if a unique key was violated (but not the primary key or the key columns of the merge itself), the wrong exception was thrown.
#MERGE: if a unique key was violated (but not the primary key or the key columns of the merge itself), the wrong exception was thrown.
@changelog_1143_li
@changelog_1144_li
#IBM DB2 and Apache Derby compatibility: support the pseudo-table SYSIBM.SYSDUMMY1.
#IBM DB2 and Apache Derby compatibility: support the pseudo-table SYSIBM.SYSDUMMY1.
@changelog_1144_li
@changelog_1145_li
#ROWNUM() did not work in combination with IN(..). The following query did not work as expected: select * from (select rownum r from test) where r in (1, 2).
#ROWNUM() did not work in combination with IN(..). The following query did not work as expected: select * from (select rownum r from test) where r in (1, 2).
@changelog_1145_li
@changelog_1146_li
#H2 Console autocomplete: the autocomplete feature didn't support quoted names.
#H2 Console autocomplete: the autocomplete feature didn't support quoted names.
@changelog_1146_li
@changelog_1147_li
#It is now longer allowed to create an index on a CLOB or BLOB column (except for in-memory databases or indexes), because recovery doesn't work on such columns. Fulltext indexes on such column are still supported of course.
#It is now longer allowed to create an index on a CLOB or BLOB column (except for in-memory databases or indexes), because recovery doesn't work on such columns. Fulltext indexes on such column are still supported of course.
@changelog_1147_li
@changelog_1148_li
#The PUBLIC schema could be renamed, which could result in a database that can't be opened normally. Now it can no longer be renamed. The schema INFORMATION_SCHEMA can also no longer be renamed.
#The PUBLIC schema could be renamed, which could result in a database that can't be opened normally. Now it can no longer be renamed. The schema INFORMATION_SCHEMA can also no longer be renamed.
@changelog_1148_li
@changelog_1149_li
#Server mode: the problem with server and client using different timezones with different daylight saving rules has been solved (this only applies when both the client and the server use this or a newer version).
#Server mode: the problem with server and client using different timezones with different daylight saving rules has been solved (this only applies when both the client and the server use this or a newer version).
@changelog_1149_li
@changelog_1150_li
#There is a new system property "h2.storeLocalTime" to avoid problems opening a database file in a timezone that has different daylight saving rules (see also below).
#There is a new system property "h2.storeLocalTime" to avoid problems opening a database file in a timezone that has different daylight saving rules (see also below).
@changelog_1150_li
@changelog_1151_li
#Date, time, and timestamp data type processing has been re-implemented. Time now supports nanoseconds resolution and now now supports a wider range (negative and large values), similar to PostgreSQL.
#Date, time, and timestamp data type processing has been re-implemented. Time now supports nanoseconds resolution and now now supports a wider range (negative and large values), similar to PostgreSQL.
@changelog_1151_li
@changelog_1152_li
#SQL statements with a non-breaking space were considered invalid.
#SQL statements with a non-breaking space were considered invalid.
@changelog_1152_h2
@changelog_1153_h2
#Version 1.3.157 (2011-06-25)
#Version 1.3.157 (2011-06-25)
@changelog_1153_li
@changelog_1154_li
#The syntax for CREATE TABLE ... AS SELECT ... has been changed: options such as NOT PERSISTENT are now before the query (AS SELECT), because otherwise they might be interpreted as a part of the query.
#The syntax for CREATE TABLE ... AS SELECT ... has been changed: options such as NOT PERSISTENT are now before the query (AS SELECT), because otherwise they might be interpreted as a part of the query.
@changelog_1154_li
@changelog_1155_li
#With version 1.3.156, the DB2 mode could not be used with CLOB and BLOB data.
#With version 1.3.156, the DB2 mode could not be used with CLOB and BLOB data.
@changelog_1155_li
@changelog_1156_li
#When upgrading from an older 1.3.x version to version 1.3.156, CLOB and BLOB data was lost in many cases.
#When upgrading from an older 1.3.x version to version 1.3.156, CLOB and BLOB data was lost in many cases.
@changelog_1156_li
@changelog_1157_li
#The optimization for COUNT(..) on columns that are not nullable was also used for COUNT(DISTINCT ..), which is incorrect.
#The optimization for COUNT(..) on columns that are not nullable was also used for COUNT(DISTINCT ..), which is incorrect.
@changelog_1157_li
@changelog_1158_li
#PgServer: non-admin users could not open a database.
#PgServer: non-admin users could not open a database.
@changelog_1158_li
@changelog_1159_li
#Non-admin users could not open a database using a mode (MODE=xxx) if the database was already open, even if the mode matched.
#Non-admin users could not open a database using a mode (MODE=xxx) if the database was already open, even if the mode matched.
@changelog_1159_li
@changelog_1160_li
#The SQL state of the following exceptions has been changed: From 90009, 90010, 90011 to 22007: "Cannot parse DATE/TIME/TIMESTAMP constant ...".
#The SQL state of the following exceptions has been changed: From 90009, 90010, 90011 to 22007: "Cannot parse DATE/TIME/TIMESTAMP constant ...".
@changelog_1160_li
@changelog_1161_li
#There is a problem when opening a database file in a timezone that has different daylight saving rules: the time part of dates where the daylight saving doesn't match will differ. This is not a problem within regions that use the same rules (such as, within USA, or within Europe), even if the timezone itself is different. As a workaround, export the database to a SQL script using the old timezone, and create a new database in the new timezone. The same problem occurs when accessing a database over TCP/IP if the client and server timezones use different rules, if an old server or client is used.
#There is a problem when opening a database file in a timezone that has different daylight saving rules: the time part of dates where the daylight saving doesn't match will differ. This is not a problem within regions that use the same rules (such as, within USA, or within Europe), even if the timezone itself is different. As a workaround, export the database to a SQL script using the old timezone, and create a new database in the new timezone. The same problem occurs when accessing a database over TCP/IP if the client and server timezones use different rules, if an old server or client is used.
@changelog_1161_h2
@changelog_1162_h2
#Version 1.3.156 (2011-06-17)
#Version 1.3.156 (2011-06-17)
@changelog_1162_li
@changelog_1163_li
#Issue 323: NullPointerException when using IN(...) with a function table.
#Issue 323: NullPointerException when using IN(...) with a function table.
@changelog_1163_li
@changelog_1164_li
#Clob.toString() and Blob.toString() now include the trace identifier.
#Clob.toString() and Blob.toString() now include the trace identifier.
@changelog_1164_li
@changelog_1165_li
#The SQL parser silently ignored characters such as '^' or '\'. Now a syntax error is thrown.
#The SQL parser silently ignored characters such as '^' or '\'. Now a syntax error is thrown.
@changelog_1165_li
@changelog_1166_li
#ROUND(..) now also works with just one parameter.
#ROUND(..) now also works with just one parameter.
@changelog_1166_li
@changelog_1167_li
#Access to system tables is now more restrictive for non-admin users (the tables can be still listed, but some of the data is not included).
#Access to system tables is now more restrictive for non-admin users (the tables can be still listed, but some of the data is not included).
@changelog_1167_li
@changelog_1168_li
#BLOB: InputStream.skip is now more efficient in embedded mode.
#BLOB: InputStream.skip is now more efficient in embedded mode.
@changelog_1168_li
@changelog_1169_li
#The default expression of a column may no longer reference the table, because a database with such a table couldn't be opened normally.
#The default expression of a column may no longer reference the table, because a database with such a table couldn't be opened normally.
@changelog_1169_li
@changelog_1170_li
#Referenced objects in check constraints could be dropped, which resulted in a database that can't be opened normally.
#Referenced objects in check constraints could be dropped, which resulted in a database that can't be opened normally.
@changelog_1170_li
@changelog_1171_li
#Improved Oracle compatibility for NVL2. Thanks again to litailang for the patch.
#Improved Oracle compatibility for NVL2. Thanks again to litailang for the patch.
@changelog_1171_li
@changelog_1172_li
#CSVREAD now supports the option 'preserveWhitespace'.
#CSVREAD now supports the option 'preserveWhitespace'.
@changelog_1172_li
@changelog_1173_li
#Recursive queries with many rows could throw an IndexOutOfBoundsException.
#Recursive queries with many rows could throw an IndexOutOfBoundsException.
@changelog_1173_li
@changelog_1174_li
#The auto-server mode can't be combined with an in-memory database. This invalid combination wasn't detected so far. Now trying to open a database in this way fails.
#The auto-server mode can't be combined with an in-memory database. This invalid combination wasn't detected so far. Now trying to open a database in this way fails.
@changelog_1174_li
@changelog_1175_li
#Improved performance for reading and writing date and time values.
#Improved performance for reading and writing date and time values.
@changelog_1175_li
@changelog_1176_li
#Java functions: array component types are now preserved, so that a ResultSet.getObject() will return Integer[] if the Java functions returns Integer[]. Thanks to Noel Grandin for the patch. Component types are transferred over the network, but not persisted in the database file as of now.
#Java functions: array component types are now preserved, so that a ResultSet.getObject() will return Integer[] if the Java functions returns Integer[]. Thanks to Noel Grandin for the patch. Component types are transferred over the network, but not persisted in the database file as of now.
@changelog_1176_li
@changelog_1177_li
#Recover tool: the script generated by the recover tool didn't work if fulltext search was used, because the triggers were created before the primary keys.
#Recover tool: the script generated by the recover tool didn't work if fulltext search was used, because the triggers were created before the primary keys.
@changelog_1177_li
@changelog_1178_li
#Issue 321: the database does not expect XA rollback without XA prepare (an exception was unnecessarily written into the .trace.db file).
#Issue 321: the database does not expect XA rollback without XA prepare (an exception was unnecessarily written into the .trace.db file).
@changelog_1178_li
@changelog_1179_li
#Read-only databases: some queries (such as distinct queries) tried to create temporary tables, which failed for read only databases.
#Read-only databases: some queries (such as distinct queries) tried to create temporary tables, which failed for read only databases.
@changelog_1179_li
@changelog_1180_li
#This database no longer uses finalize() except for temporary files. The system property "h2.runFinalize" is no longer supported. Unclosed connections are still detected, but the opening stack trace is now collected only if connections are not closed repeatedly (starting with the second unclosed connection). To detect unclosed connections, a PhantomReference is used.
#This database no longer uses finalize() except for temporary files. The system property "h2.runFinalize" is no longer supported. Unclosed connections are still detected, but the opening stack trace is now collected only if connections are not closed repeatedly (starting with the second unclosed connection). To detect unclosed connections, a PhantomReference is used.
@changelog_1180_li
@changelog_1181_li
#Issue 322: Left joins didn't work when used as subquery in the form clause.
#Issue 322: Left joins didn't work when used as subquery in the form clause.
@changelog_1181_li
@changelog_1182_li
#A prepared statement if type CALL that returned a result set could throw a NullPointerException if executed multiple times.
#A prepared statement if type CALL that returned a result set could throw a NullPointerException if executed multiple times.
@changelog_1182_li
@changelog_1183_li
#The following built-in functions were marked as deterministic and therefore not re-executed when using in a prepared statement: LOCK_TIMEOUT, LINK_SCHEMA, CANCEL_SESSION, FILE_READ.
#The following built-in functions were marked as deterministic and therefore not re-executed when using in a prepared statement: LOCK_TIMEOUT, LINK_SCHEMA, CANCEL_SESSION, FILE_READ.
@changelog_1183_li
@changelog_1184_li
#Count on a column that can not be null is now optimized to COUNT(*). Thanks a lot to Ross Judson for providing a patch and test case!
#Count on a column that can not be null is now optimized to COUNT(*). Thanks a lot to Ross Judson for providing a patch and test case!
@changelog_1184_li
@changelog_1185_li
#The following prepared statements are now cached as well: insert, update, delete, call, merge, and transactional commands.
#The following prepared statements are now cached as well: insert, update, delete, call, merge, and transactional commands.
@changelog_1185_li
@changelog_1186_li
#The built-in connection pool is now a bit faster.
#The built-in connection pool is now a bit faster.
@changelog_1186_li
@changelog_1187_li
#The scale was not set correctly in some cases when using CREATE TABLE AS SELECT if there was no explicit column definition.
#The scale was not set correctly in some cases when using CREATE TABLE AS SELECT if there was no explicit column definition.
@changelog_1187_li
@changelog_1188_li
#When trying to connect to a server using TCP/IP failed, it will retry at most until the timeout. Before, it was the timeout multiplied with the retry count.
#When trying to connect to a server using TCP/IP failed, it will retry at most until the timeout. Before, it was the timeout multiplied with the retry count.
@changelog_1188_h2
@changelog_1189_h2
#Version 1.3.155 (2011-05-27)
#Version 1.3.155 (2011-05-27)
@changelog_1189_li
@changelog_1190_li
#When altering a table with triggers, new triggers are created and initialized with a table name that ends with tableName_COPY_x_y. The plan is that this will not be required in future versions.
#When altering a table with triggers, new triggers are created and initialized with a table name that ends with tableName_COPY_x_y. The plan is that this will not be required in future versions.
@changelog_1190_li
@changelog_1191_li
#If some of the file system operations failed, System.gc() was called in a loop. Now it is called once at most.
#If some of the file system operations failed, System.gc() was called in a loop. Now it is called once at most.
@changelog_1191_li
@changelog_1192_li
#Triggers (including the fulltext search) could throw the exception 'Unexpected code path' in Session.log.
#Triggers (including the fulltext search) could throw the exception 'Unexpected code path' in Session.log.
@changelog_1192_li
@changelog_1193_li
#CURRENT_TIMESTAMP() and so on now return the same value within a transaction.
#CURRENT_TIMESTAMP() and so on now return the same value within a transaction.
@changelog_1193_li
@changelog_1194_li
#The statement CALL no longer converts an ARRAY return value to a list of values. Now an ARRAY is returned.
#The statement CALL no longer converts an ARRAY return value to a list of values. Now an ARRAY is returned.
@changelog_1194_li
@changelog_1195_li
#VALUES is now supported as a standalone command and as a table source: SELECT * FROM (VALUES(1, 'Hello'), (2, 'World')) AS V;
#VALUES is now supported as a standalone command and as a table source: SELECT * FROM (VALUES(1, 'Hello'), (2, 'World')) AS V;
@changelog_1195_li
@changelog_1196_li
#TIMESTAMPADD is now an alias for DATEADD. Most SQL_TSI_ constants are now supported for for TIMESTAMPADD and TIMESTAMPDIFF (all except SQL_TSI_QUARTER and SQL_TSI_FRAC_SECOND).
#TIMESTAMPADD is now an alias for DATEADD. Most SQL_TSI_ constants are now supported for for TIMESTAMPADD and TIMESTAMPDIFF (all except SQL_TSI_QUARTER and SQL_TSI_FRAC_SECOND).
@changelog_1196_li
@changelog_1197_li
#Issue 313: NullPointerException in select query with a subquery or view.
#Issue 313: NullPointerException in select query with a subquery or view.
@changelog_1197_li
@changelog_1198_li
#Native fulltext search: the characters '<', '>', and '\' are now also whitespace characters. Also, the list of whitespace characters can be changed using FullText.setWhitespaceChars(conn, ...)
#Native fulltext search: the characters '<', '>', and '\' are now also whitespace characters. Also, the list of whitespace characters can be changed using FullText.setWhitespaceChars(conn, ...)
@changelog_1198_li
@changelog_1199_li
#When reading from the classpath (for example read_file('classpath:logo.png')), now the content class loader is used if the resource can't be found otherwise.
#When reading from the classpath (for example read_file('classpath:logo.png')), now the content class loader is used if the resource can't be found otherwise.
@changelog_1199_li
@changelog_1200_li
#The statement "script drop" create a script that couldn't be executed if a table contained a reference to a user defined function.
#The statement "script drop" create a script that couldn't be executed if a table contained a reference to a user defined function.
@changelog_1200_li
@changelog_1201_li
#Opening a database with both multi-threaded mode and lock mode 0 (disable locking) was possible (but only once), even thought it does not work properly. Now it is no longer allowed.
#Opening a database with both multi-threaded mode and lock mode 0 (disable locking) was possible (but only once), even thought it does not work properly. Now it is no longer allowed.
@changelog_1201_li
@changelog_1202_li
#LOB objects are now deleted (and the empty space is reused) when the transaction is committed. So far, the space wasn't re-used until the connection was closed.
#LOB objects are now deleted (and the empty space is reused) when the transaction is committed. So far, the space wasn't re-used until the connection was closed.
@changelog_1202_li
@changelog_1203_li
#SCRIPT DROP did not use the cascade option for table, which would cause problems if a view was dropped before a table it depends on. Now the cascade option is used.
#SCRIPT DROP did not use the cascade option for table, which would cause problems if a view was dropped before a table it depends on. Now the cascade option is used.
@changelog_1203_li
@changelog_1204_li
#The query plan of queries with subqueries that contain nested joins was wrong. This could result in syntax exceptions for correct queries. Example: select 1 from (select 2 from ((test t1 inner join test t2 on t1.id=t2.id) inner join test t3 on t3.id=t1.id)) x;
#The query plan of queries with subqueries that contain nested joins was wrong. This could result in syntax exceptions for correct queries. Example: select 1 from (select 2 from ((test t1 inner join test t2 on t1.id=t2.id) inner join test t3 on t3.id=t1.id)) x;
@changelog_1204_li
@changelog_1205_li
#DatabaseEventListener.init was called with a null url when using the server mode.
#DatabaseEventListener.init was called with a null url when using the server mode.
@changelog_1205_li
@changelog_1206_li
#Support for the function LN (an alias for LOG).
#Support for the function LN (an alias for LOG).
@changelog_1206_li
@changelog_1207_li
#Support for the function CEIL (an alias for CEILING).
#Support for the function CEIL (an alias for CEILING).
@changelog_1207_li
@changelog_1208_li
#Issue 315: Access to LOBs could cause a Java level deadlock.
#Issue 315: Access to LOBs could cause a Java level deadlock.
@changelog_1208_li
@changelog_1209_li
#Support for the ICU4J collator.
#Support for the ICU4J collator.
@changelog_1209_li
@changelog_1210_li
#Improved Oracle compatibility: support for NVL2. Thanks to litailang for the patch!
#Improved Oracle compatibility: support for NVL2. Thanks to litailang for the patch!
@changelog_1210_li
@changelog_1211_li
#Improved PostgreSQL compatibility: support for RANDOM() in addition to RAND().
#Improved PostgreSQL compatibility: support for RANDOM() in addition to RAND().
@changelog_1211_li
@changelog_1212_li
#There was a classloader memory leak problem because a class contained a static references to an exception (including stack trace).
#There was a classloader memory leak problem because a class contained a static references to an exception (including stack trace).
@changelog_1212_li
@changelog_1213_li
#Split file system: truncating a file now deletes the parts in reverse order, so that the file list is consistent if the process is interrupted while truncating.
#Split file system: truncating a file now deletes the parts in reverse order, so that the file list is consistent if the process is interrupted while truncating.
@changelog_1213_li
@changelog_1214_li
#The H2 JDBC client can now be used in an unsigned Applet. The problem was that System.getProperty throws a SecurityException, which is now ignored.
#The H2 JDBC client can now be used in an unsigned Applet. The problem was that System.getProperty throws a SecurityException, which is now ignored.
@changelog_1214_li
@changelog_1215_li
#The condition "in(select ...)" did not work correctly if the subquery could not be converted to a "distinct" query, as in: "select * from dual where x in (select x from dual group by x order by max(x))". Now the subquery needs to be made distinct manually if this optimization is needed.
#The condition "in(select ...)" did not work correctly if the subquery could not be converted to a "distinct" query, as in: "select * from dual where x in (select x from dual group by x order by max(x))". Now the subquery needs to be made distinct manually if this optimization is needed.
@changelog_1215_li
@changelog_1216_li
#In the last release, the error code for "Wrong user name or password" was still 08004 instead of 28000, which resulted in the wrong error message.
#In the last release, the error code for "Wrong user name or password" was still 08004 instead of 28000, which resulted in the wrong error message.
@changelog_1216_li
@changelog_1217_li
#In some cases, creating a new table or altering an existing table threw the exception: Unique index or primary key violation: "PRIMARY KEY ON """".PAGE_INDEX".
#In some cases, creating a new table or altering an existing table threw the exception: Unique index or primary key violation: "PRIMARY KEY ON """".PAGE_INDEX".
@changelog_1217_li
@changelog_1218_li
#The Shell tool no longer supports the built-in command "show", because it is a legal SQL statement for H2 and MySQL. However, the "describe" command is still supported, and now lists all tables if called without parameter.
#The Shell tool no longer supports the built-in command "show", because it is a legal SQL statement for H2 and MySQL. However, the "describe" command is still supported, and now lists all tables if called without parameter.
@changelog_1218_li
@changelog_1219_li
#The sorted insert mode (as in "insert into ... direct sorted select") did not work for not-persisted tables in a persisted database. It threw a ClassCastException.
#The sorted insert mode (as in "insert into ... direct sorted select") did not work for not-persisted tables in a persisted database. It threw a ClassCastException.
@changelog_1219_li
@changelog_1220_li
#Issue 308: Statement.getGeneratedKeys() now returns an empty result set if no key was generated.
#Issue 308: Statement.getGeneratedKeys() now returns an empty result set if no key was generated.
@changelog_1220_li
@changelog_1221_li
#The h2small.jar (created with build jarSmall) included the Android API. This has been removed, shrinking the jar file by 21 KB.
#The h2small.jar (created with build jarSmall) included the Android API. This has been removed, shrinking the jar file by 21 KB.
@changelog_1221_li
@changelog_1222_li
#When creating a table, the precision must now be at least as large as the scale.
#When creating a table, the precision must now be at least as large as the scale.
@changelog_1222_li
@changelog_1223_li
#Support for Java 1.3 and Java 1.4 has been removed.
#Support for Java 1.3 and Java 1.4 has been removed.
@changelog_1223_li
@changelog_1224_li
#Improved error message for syntax error: the list of expected tokens was sometimes not set correctly.
#Improved error message for syntax error: the list of expected tokens was sometimes not set correctly.
@changelog_1224_li
@changelog_1225_li
#Database file growth can now be limited using the database setting PAGE_STORE_MAX_GROWTH. Slower growth may slow down operation, but speed up closing database.
#Database file growth can now be limited using the database setting PAGE_STORE_MAX_GROWTH. Slower growth may slow down operation, but speed up closing database.
@changelog_1225_li
@changelog_1226_li
#A read only database with writable linked tables could lead to a DATABASE_IS_READ_ONLY (90097) error. This is fixed now.
#A read only database with writable linked tables could lead to a DATABASE_IS_READ_ONLY (90097) error. This is fixed now.
@changelog_1226_h2
@changelog_1227_h2
#Version 1.3.154 (2011-04-04)
#Version 1.3.154 (2011-04-04)
@changelog_1227_li
@changelog_1228_li
#The SQL state of the following exceptions has been changed: From 90005 to 22001: "Value too long for column ...: ...". From 90039 to 22003: "The value is too large for the precision ..." is merged with "Numeric value out of range". From 90110 to 22003: "... out of range" is merged with "Numeric value out of range". From 90021 to 22018: "Data conversion error converting ...". From 90006 to 23502: "NULL not allowed for column ...". From 23003 to 23503: "Referential integrity constraint violation: ...". From 23001 to 23505: "Unique index or primary key violation: ...". From 23002 to 23506: "Referential integrity constraint violation: ...". From 90056 to 23507: "No default value is set for column ...". From 23000 to 23513: "Check constraint violation: ...". From 08004 to 28000: "Wrong user name or password". From 90051 to 57014: "Statement was canceled or the session timed out".
#The SQL state of the following exceptions has been changed: From 90005 to 22001: "Value too long for column ...: ...". From 90039 to 22003: "The value is too large for the precision ..." is merged with "Numeric value out of range". From 90110 to 22003: "... out of range" is merged with "Numeric value out of range". From 90021 to 22018: "Data conversion error converting ...". From 90006 to 23502: "NULL not allowed for column ...". From 23003 to 23503: "Referential integrity constraint violation: ...". From 23001 to 23505: "Unique index or primary key violation: ...". From 23002 to 23506: "Referential integrity constraint violation: ...". From 90056 to 23507: "No default value is set for column ...". From 23000 to 23513: "Check constraint violation: ...". From 08004 to 28000: "Wrong user name or password". From 90051 to 57014: "Statement was canceled or the session timed out".
@changelog_1228_li
@changelog_1229_li
#The H2 Console now detects unsupported command line options. (In the future, it will be combined with the Server tool.)
#The H2 Console now detects unsupported command line options. (In the future, it will be combined with the Server tool.)
@changelog_1229_li
@changelog_1230_li
#MySQL compatibility: SHOW COLUMN FOR schemaName.columnName.
#MySQL compatibility: SHOW COLUMN FOR schemaName.columnName.
@changelog_1230_li
@changelog_1231_li
#DatabaseMetaData.getCrossReference now also lists the name of the primary index (PK_NAME).
#DatabaseMetaData.getCrossReference now also lists the name of the primary index (PK_NAME).
@changelog_1231_li
@changelog_1232_li
#If the database contained many CLOB or BLOB values, then closing a connection was very slow. Reason: was that when closing a connection, the temporary CLOB and BLOB values for this connection were removed, but there was no index on this column. For existing databases with many CLOB and BLOB values, creating the index may take a few seconds. The index is added to existing databases automatically.
#If the database contained many CLOB or BLOB values, then closing a connection was very slow. Reason: was that when closing a connection, the temporary CLOB and BLOB values for this connection were removed, but there was no index on this column. For existing databases with many CLOB and BLOB values, creating the index may take a few seconds. The index is added to existing databases automatically.
@changelog_1232_li
@changelog_1233_li
#If a CLOB or BLOB was copied into the same table using INSERT INTO X ... SELECT ... FROM X, and then the original row was deleted, then the copied value was also deleted. This could also result in an ArrayIndexOutOfBoundsException on checkpoint or when closing the database.
#If a CLOB or BLOB was copied into the same table using INSERT INTO X ... SELECT ... FROM X, and then the original row was deleted, then the copied value was also deleted. This could also result in an ArrayIndexOutOfBoundsException on checkpoint or when closing the database.
@changelog_1233_li
@changelog_1234_li
#Improved performance (up to 10%) due to changed synchronization in the page store.
#Improved performance (up to 10%) due to changed synchronization in the page store.
@changelog_1234_li
@changelog_1235_li
#Reading a resource from the classpath didn't work if there was a leading slash (classpath:/org/...). Now resources can be loaded with or without leading slash.
#Reading a resource from the classpath didn't work if there was a leading slash (classpath:/org/...). Now resources can be loaded with or without leading slash.
@changelog_1235_li
@changelog_1236_li
#Support INSERT INTO TEST SET ID = 1, NAME = 'World' (MySQL compatibility).
#Support INSERT INTO TEST SET ID = 1, NAME = 'World' (MySQL compatibility).
@changelog_1236_li
@changelog_1237_li
#Issue 304: The condition [NOT] IN (SELECT ...) could throw the exception "Unexpected code path" if the subquery contained ORDER BY.
#Issue 304: The condition [NOT] IN (SELECT ...) could throw the exception "Unexpected code path" if the subquery contained ORDER BY.
@changelog_1237_li
@changelog_1238_li
#ALTER TABLE ALTER ADD / REMOVE /ALTER COLUMN dropped some dependent objects (access rights, triggers) of views that depend on the modified table.
#ALTER TABLE ALTER ADD / REMOVE /ALTER COLUMN dropped some dependent objects (access rights, triggers) of views that depend on the modified table.
@changelog_1238_li
@changelog_1239_li
#CREATE OR REPLACE VIEW dropped some dependent objects (access rights, triggers) if the view already existed before.
#CREATE OR REPLACE VIEW dropped some dependent objects (access rights, triggers) if the view already existed before.
@changelog_1239_li
@changelog_1240_li
#New aggregate function HISTOGRAM to calculate the histogram. The plan is to use this function is only used internally when running ANALYZE to generate the histogram that is then used by the query optimizer.
#New aggregate function HISTOGRAM to calculate the histogram. The plan is to use this function is only used internally when running ANALYZE to generate the histogram that is then used by the query optimizer.
@changelog_1240_li
@changelog_1241_li
#New system function TRUNCATE_VALUE to truncate a value to the required precision. This is the same as for CAST, but without changing the data type, and support for truncating decimal values. (The main use case for this function is to build a histogram of the truncated values). Now BINARY, BLOB, and CLOB can be truncated / cast efficiently as well.
#New system function TRUNCATE_VALUE to truncate a value to the required precision. This is the same as for CAST, but without changing the data type, and support for truncating decimal values. (The main use case for this function is to build a histogram of the truncated values). Now BINARY, BLOB, and CLOB can be truncated / cast efficiently as well.
@changelog_1241_li
@changelog_1242_li
#The precision of an ARRAY value is now the sum of the precision of all elements, and result set values have the precision Integer.MAX_VALUE.
#The precision of an ARRAY value is now the sum of the precision of all elements, and result set values have the precision Integer.MAX_VALUE.
@changelog_1242_li
@changelog_1243_li
#CAST(x AS VARCHAR_IGNORECASE(y) / CHAR(y)) returned a VARCHAR if the new precision was lower than the old precision.
#CAST(x AS VARCHAR_IGNORECASE(y) / CHAR(y)) returned a VARCHAR if the new precision was lower than the old precision.
@changelog_1243_li
@changelog_1244_li
#SHUTDOWN DEFRAG didn't defragment the database completely if there was a unique hash index for a memory table.
#SHUTDOWN DEFRAG didn't defragment the database completely if there was a unique hash index for a memory table.
@changelog_1244_li
@changelog_1245_li
#There were some smaller changes in the encrypting file system (work in progress).
#There were some smaller changes in the encrypting file system (work in progress).
@changelog_1245_li
@changelog_1246_li
#Some time and timezone functions didn't support years before 1.
#Some time and timezone functions didn't support years before 1.
@@ -543,250 +543,251 @@ build_1111_li=The rail images (one straight, four junctions, two turns) are gene
...
@@ -543,250 +543,251 @@ build_1111_li=The rail images (one straight, four junctions, two turns) are gene
build_1112_p=\ To generate railroad diagrams for other grammars, see the package <code>org.h2.jcr</code>. This package is used to generate the SQL-2 railroad diagrams for the JCR 2.0 specification.
build_1112_p=\ To generate railroad diagrams for other grammars, see the package <code>org.h2.jcr</code>. This package is used to generate the SQL-2 railroad diagrams for the JCR 2.0 specification.
changelog_1000_h1=Change Log
changelog_1000_h1=Change Log
changelog_1001_h2=Next Version (unreleased)
changelog_1001_h2=Next Version (unreleased)
changelog_1002_li=Lukas Eder has updated the jOOQ documentation.
changelog_1002_li=H2 Console\:when editing a row, an empty varchar column was replaced with a single space.
changelog_1003_li=Some nested joins could not be executed, for example\:select * from (select * from (select * from a) a right join b b) c;
changelog_1003_li=Lukas Eder has updated the jOOQ documentation.
changelog_1004_li=MS SQL Server compatibility\:ISNULL is now an alias for IFNULL.
changelog_1004_li=Some nested joins could not be executed, for example\:select * from (select * from (select * from a) a right join b b) c;
changelog_1005_li=Terrence Huang has completed the translation of the H2 Console tool to Chinese. Thanks a lot\!
changelog_1005_li=MS SQL Server compatibility\:ISNULL is now an alias for IFNULL.
changelog_1006_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_1006_li=Terrence Huang has completed the translation of the H2 Console tool to Chinese. Thanks a lot\!
changelog_1007_li=In the trace file, the query execution time was incorrect in some cases, specially for the statement SET TRACE_LEVEL_FILE 2.
changelog_1007_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_1008_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_1008_li=In the trace file, the query execution time was incorrect in some cases, specially for the statement SET TRACE_LEVEL_FILE 2.
changelog_1009_li=Then reading from a resource using the prefix "classpath\:", the ContextClassLoader is now used if the resource can't be read otherwise.
changelog_1009_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_1010_li=DatabaseEventListener now calls setProgress whenever a statement starts and ends.
changelog_1010_li=Then reading from a resource using the prefix "classpath\:", the ContextClassLoader is now used if the resource can't be read otherwise.
changelog_1011_li=DatabaseEventListener now calls setProgress periodically while a statement is running.
changelog_1011_li=DatabaseEventListener now calls setProgress whenever a statement starts and ends.
changelog_1012_li=The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME.
changelog_1012_li=DatabaseEventListener now calls setProgress periodically while a statement is running.
changelog_1013_li=Issue 378\: when using views, the wrong values were bound to a parameter in some cases.
changelog_1013_li=The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME.
changelog_1014_li=Terrence Huang has translated the error messages to Chinese. Thanks a lot\!
changelog_1014_li=Issue 378\: when using views, the wrong values were bound to a parameter in some cases.
changelog_1015_li=TRUNC was added as an alias for TRUNCATE.
changelog_1015_li=Terrence Huang has translated the error messages to Chinese. Thanks a lot\!
changelog_1016_li=Small optimisation for accessing result values by column name.
changelog_1016_li=TRUNC was added as an alias for TRUNCATE.
changelog_1017_li=Fix for bug in Statement\#getMoreResults(int)
changelog_1017_li=Small optimisation for accessing result values by column name.
changelog_1018_li=The SCRIPT statements now supports filtering by schema and table. Thanks a lot to Jacob Qvortrup for providing the patch\!
changelog_1018_li=Fix for bug in Statement\#getMoreResults(int)
changelog_1019_h2=Version 1.3.166 (2012-04-08)
changelog_1019_li=The SCRIPT statements now supports filtering by schema and table. Thanks a lot to Jacob Qvortrup for providing the patch\!
changelog_1020_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_1020_h2=Version 1.3.166 (2012-04-08)
changelog_1021_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_1021_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_1022_li=ConvertTraceFile\:the time in the trace file is now parsed as a long.
changelog_1022_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_1023_li=Invalid connection settings are now detected.
changelog_1023_li=ConvertTraceFile\:the time in the trace file is now parsed as a long.
changelog_1024_li=Issue 387\:WHERE condition getting pushed into sub-query with LIMIT.
changelog_1024_li=Invalid connection settings are now detected.
changelog_1025_h2=Version 1.3.165 (2012-03-18)
changelog_1025_li=Issue 387\:WHERE condition getting pushed into sub-query with LIMIT.
changelog_1026_li=Better string representation for decimal values (for example 0.00000000 instead of 0E-26).
changelog_1026_h2=Version 1.3.165 (2012-03-18)
changelog_1027_li=Prepared statements could only be re-used if the same data types were used the second time they were executed.
changelog_1027_li=Better string representation for decimal values (for example 0.00000000 instead of 0E-26).
changelog_1028_li=In error messages about referential constraint violation, the values are now included.
changelog_1028_li=Prepared statements could only be re-used if the same data types were used the second time they were executed.
changelog_1029_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_1029_li=In error messages about referential constraint violation, the values are now included.
changelog_1030_li=MySQL compatibility\:SUBSTR with a negative start index now works like MySQL.
changelog_1030_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_1031_li=When enabling autocommit, the transaction is now committed (as required by the JDBC API).
changelog_1031_li=MySQL compatibility\:SUBSTR with a negative start index now works like MySQL.
changelog_1032_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_1032_li=When enabling autocommit, the transaction is now committed (as required by the JDBC API).
changelog_1033_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_1033_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_1034_li=ALTER TABLE ADD can now add more than one column at a time.
changelog_1034_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_1035_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_1035_li=ALTER TABLE ADD can now add more than one column at a time.
changelog_1036_li=Issue 384\:the wrong kind of exception (NullPointerException) was thrown in a UNION query with an incorrect ORDER BY expression.
changelog_1036_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_1037_li=Issue 362\:support LIMIT in UPDATE statements.
changelog_1037_li=Issue 384\:the wrong kind of exception (NullPointerException) was thrown in a UNION query with an incorrect ORDER BY expression.
changelog_1038_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_1038_li=Issue 362\:support LIMIT in UPDATE statements.
changelog_1039_li=CSV tool\:new feature to disable writing the column header (option writeColumnHeader).
changelog_1039_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_1040_li=CSV tool\:new feature to preserve the case sensitivity of column names (option caseSensitiveColumnNames).
changelog_1040_li=CSV tool\:new feature to disable writing the column header (option writeColumnHeader).
changelog_1041_li=PostgreSQL compatibility\:LOG(x) is base 10 in the PostgreSQL mode.
changelog_1041_li=CSV tool\:new feature to preserve the case sensitivity of column names (option caseSensitiveColumnNames).
changelog_1042_h2=Version 1.3.164 (2012-02-03)
changelog_1042_li=PostgreSQL compatibility\:LOG(x) is base 10 in the PostgreSQL mode.
changelog_1043_li=New built-in function ARRAY_CONTAINS.
changelog_1043_h2=Version 1.3.164 (2012-02-03)
changelog_1044_li=Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
changelog_1044_li=New built-in function ARRAY_CONTAINS.
changelog_1045_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_1045_li=Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
changelog_1046_li=TriggerAdapter\:in "before" triggers, values can be changed using the ResultSet.updateX methods.
changelog_1046_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_1047_li=Creating a table with column data type NULL now works (even if not very useful).
changelog_1047_li=TriggerAdapter\:in "before" triggers, values can be changed using the ResultSet.updateX methods.
changelog_1048_li=ALTER TABLE ALTER COLUMN no longer copies the data for widening conversions (for example if only the precision was increased) unless necessary.
changelog_1048_li=Creating a table with column data type NULL now works (even if not very useful).
changelog_1049_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_1049_li=ALTER TABLE ALTER COLUMN no longer copies the data for widening conversions (for example if only the precision was increased) unless necessary.
changelog_1050_li=The script created by SCRIPT DROP did not always work if multiple views existed that depend on each other.
changelog_1050_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_1051_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_1051_li=The script created by SCRIPT DROP did not always work if multiple views existed that depend on each other.
changelog_1052_li=The database file locking mechanism "FS" (;FILE_LOCK\=FS) did not work on Linux since version 1.3.161.
changelog_1052_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_1053_li=Sequences\:the functions NEXTVAL and CURRVAL did not work as expected when using quoted, mixed case sequence names.
changelog_1053_li=The database file locking mechanism "FS" (;FILE_LOCK\=FS) did not work on Linux since version 1.3.161.
changelog_1054_li=The constructor for Csv objects is now public, and Csv.getInstance() is now deprecated.
changelog_1054_li=Sequences\:the functions NEXTVAL and CURRVAL did not work as expected when using quoted, mixed case sequence names.
changelog_1055_li=SimpleResultSet\:updating a result set is now supported.
changelog_1055_li=The constructor for Csv objects is now public, and Csv.getInstance() is now deprecated.
changelog_1056_li=Database URL\:extra semicolons are not supported.
changelog_1056_li=SimpleResultSet\:updating a result set is now supported.
changelog_1057_h2=Version 1.3.163 (2011-12-30)
changelog_1057_li=Database URL\:extra semicolons are not supported.
changelog_1058_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_1058_h2=Version 1.3.163 (2011-12-30)
changelog_1059_li=DatabaseEventListener.diskSpaceIsLow() is no longer supported because it can't be guaranteed that it always works correctly.
changelog_1059_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_1060_li=XMLTEXT now supports an optional parameter to escape newlines.
changelog_1060_li=DatabaseEventListener.diskSpaceIsLow() is no longer supported because it can't be guaranteed that it always works correctly.
changelog_1061_li=XMLNODE now support an optional parameter to disable indentation.
changelog_1061_li=XMLTEXT now supports an optional parameter to escape newlines.
changelog_1062_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_1062_li=XMLNODE now support an optional parameter to disable indentation.
changelog_1063_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_1063_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_1064_li=The page size of a persistent database can now be queries using\:select * from information_schema.settings where name \='info.PAGE_SIZE'
changelog_1064_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_1065_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_1065_li=The page size of a persistent database can now be queries using\:select * from information_schema.settings where name \='info.PAGE_SIZE'
changelog_1066_h2=Version 1.3.162 (2011-11-26)
changelog_1066_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_1067_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_1067_h2=Version 1.3.162 (2011-11-26)
changelog_1068_li=When using a VPN, starting a H2 server did not work (for some VPN software).
changelog_1068_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_1069_li=Oracle compatibility\:support for DECODE(...).
changelog_1069_li=When using a VPN, starting a H2 server did not work (for some VPN software).
changelog_1070_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_1070_li=Oracle compatibility\:support for DECODE(...).
changelog_1071_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_1071_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_1072_li=Read-only databases in a zip file did not work when using the -baseDir option.
changelog_1072_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_1073_li=Issue 334\:SimpleResultSet.getString now also works for Clob columns.
changelog_1073_li=Read-only databases in a zip file did not work when using the -baseDir option.
changelog_1074_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_1074_li=Issue 334\:SimpleResultSet.getString now also works for Clob columns.
changelog_1075_li=Server\:in some (theoretical) cases, exceptions while closing the connection were ignored.
changelog_1075_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_1076_li=Server.createTcpServer, createPgServer, createWebServer\:invalid arguments are now detected.
changelog_1076_li=Server\:in some (theoretical) cases, exceptions while closing the connection were ignored.
changelog_1077_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_1077_li=Server.createTcpServer, createPgServer, createWebServer\:invalid arguments are now detected.
changelog_1078_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_1078_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_1079_li=A NullPointerException could occur in TableView.isDeterministic for invalid views.
changelog_1079_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_1080_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_1080_li=A NullPointerException could occur in TableView.isDeterministic for invalid views.
changelog_1081_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_1081_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_1082_li=The optimization for "group by" was not working correctly if the group by column was aliased in the select list.
changelog_1082_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_1083_li=Issue 326\:improved support for case sensitive (mixed case) identifiers without quotes when using DATABASE_TO_UPPER\=FALSE.
changelog_1083_li=The optimization for "group by" was not working correctly if the group by column was aliased in the select list.
changelog_1084_h2=Version 1.3.161 (2011-10-28)
changelog_1084_li=Issue 326\:improved support for case sensitive (mixed case) identifiers without quotes when using DATABASE_TO_UPPER\=FALSE.
changelog_1085_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_1085_h2=Version 1.3.161 (2011-10-28)
changelog_1086_li=TCP server\:when using the trace option ("-trace"), the trace output contained unnecessary stack traces when stopping the server.
changelog_1086_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_1087_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_1087_li=TCP server\:when using the trace option ("-trace"), the trace output contained unnecessary stack traces when stopping the server.
changelog_1088_li=Issue 350\:when using instead of triggers, executeUpdate for delete operations always returned 0.
changelog_1088_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_1089_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_1089_li=Issue 350\:when using instead of triggers, executeUpdate for delete operations always returned 0.
changelog_1090_li=Sequences with cache size smaller than 0 did not work correctly.
changelog_1090_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_1091_li=Issue 356\:for Blob objects, InputStream.skip() returned 0, causing EOFException in Blob.getBytes(.., ..).
changelog_1091_li=Sequences with cache size smaller than 0 did not work correctly.
changelog_1092_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_1092_li=Issue 356\:for Blob objects, InputStream.skip() returned 0, causing EOFException in Blob.getBytes(.., ..).
changelog_1093_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_1093_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_1094_li=Issue 347\:the RunScript and Shell tools now ignore empty statements.
changelog_1094_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_1095_li=Issue 246\:improved error message for data conversion problems.
changelog_1095_li=Issue 347\:the RunScript and Shell tools now ignore empty statements.
changelog_1096_li=Issue 344\:the build now supports a custom Maven repository location.
changelog_1096_li=Issue 246\:improved error message for data conversion problems.
changelog_1097_li=Issue 334\:Java functions that return CLOB or BLOB objects could not be used as tables.
changelog_1097_li=Issue 344\:the build now supports a custom Maven repository location.
changelog_1098_li=SimpleResultSet now supports getColumnTypeName and getColumnClassName.
changelog_1098_li=Issue 334\:Java functions that return CLOB or BLOB objects could not be used as tables.
changelog_1099_li=SimpleResultSet now has minimal BLOB and CLOB support.
changelog_1099_li=SimpleResultSet now supports getColumnTypeName and getColumnClassName.
changelog_1100_li=Improved performance for large databases (many GB), and databases with a small page size.
changelog_1100_li=SimpleResultSet now has minimal BLOB and CLOB support.
changelog_1101_li=The Polish translation has been improved by Jaros&\#322;aw Kokoci&\#324;ski.
changelog_1101_li=Improved performance for large databases (many GB), and databases with a small page size.
changelog_1102_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_1102_li=The Polish translation has been improved by Jaros&\#322;aw Kokoci&\#324;ski.
changelog_1103_li=Improved compatibility for "fetch first / next row(s)". Thanks a lot to litailang for the patch\!
changelog_1103_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_1104_li=Improved compatibility with the Java 7 FileSystem abstraction.
changelog_1104_li=Improved compatibility for "fetch first / next row(s)". Thanks a lot to litailang for the patch\!
changelog_1105_h2=Version 1.3.160 (2011-09-11)
changelog_1105_li=Improved compatibility with the Java 7 FileSystem abstraction.
changelog_1106_li=Computed columns could not refer to itself.
changelog_1106_h2=Version 1.3.160 (2011-09-11)
changelog_1107_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_1107_li=Computed columns could not refer to itself.
changelog_1108_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_1108_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_1109_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_1109_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_1110_li=Source code switching using //\#\#has been simplified. The Java 1.5 tag has been removed because is no longer needed.
changelog_1110_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_1111_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_1111_li=Source code switching using //\#\#has been simplified. The Java 1.5 tag has been removed because is no longer needed.
changelog_1112_li=Invalid tables names in 'order by' columns were not detected in some cases. Example\:select x from dual order by y.x
changelog_1112_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_1113_li=Issue 329\:CASE expression\:data type problem is not detected.
changelog_1113_li=Invalid tables names in 'order by' columns were not detected in some cases. Example\:select x from dual order by y.x
changelog_1114_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_1114_li=Issue 329\:CASE expression\:data type problem is not detected.
changelog_1115_h2=Version 1.3.159 (2011-08-13)
changelog_1115_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_1116_li=Creating a temporary table with the option 'transactional' will now also create the indexes in transactional mode, if the indexes are included in the 'create table' statement as follows\:"create local temporary table temp(id int primary key, name varchar, constraint x index(name)) transactional".
changelog_1116_h2=Version 1.3.159 (2011-08-13)
changelog_1117_li=The database file size grows now 35%, but at most 256 MB at a time.
changelog_1117_li=Creating a temporary table with the option 'transactional' will now also create the indexes in transactional mode, if the indexes are included in the 'create table' statement as follows\:"create local temporary table temp(id int primary key, name varchar, constraint x index(name)) transactional".
changelog_1118_li=Improved error message on network configuration problems.
changelog_1118_li=The database file size grows now 35%, but at most 256 MB at a time.
changelog_1119_li=The build now support an offline build using ./build.sh offline. This will list the required dependencies if jar files are missing.
changelog_1119_li=Improved error message on network configuration problems.
changelog_1120_li=The BLOB / CLOB data was dropped a little bit before the table was dropped. This could cause "lob not found" errors when the process was killed while a table was dropped.
changelog_1120_li=The build now support an offline build using ./build.sh offline. This will list the required dependencies if jar files are missing.
changelog_1121_li="group_concat(distinct ...)"did not work correctly in a view or subquery (the 'distinct' was lost). Example\:select * from (select group_concat(distinct 1) from system_range(1, 3));
changelog_1121_li=The BLOB / CLOB data was dropped a little bit before the table was dropped. This could cause "lob not found" errors when the process was killed while a table was dropped.
changelog_1122_li=Database URLs can now be re-mapped to another URL using the system property "h2.urlMap", which points to a properties file with database URL mappings.
changelog_1122_li="group_concat(distinct ...)"did not work correctly in a view or subquery (the 'distinct' was lost). Example\:select * from (select group_concat(distinct 1) from system_range(1, 3));
changelog_1123_li=When using InputStream.skip, trying to read past the end of a BLOB failed with the exception "IO Exception\:Missing lob entry\:..." [90028-...].
changelog_1123_li=Database URLs can now be re-mapped to another URL using the system property "h2.urlMap", which points to a properties file with database URL mappings.
changelog_1124_li=The in-memory file system "memFS\:" now has limited support for directories.
changelog_1124_li=When using InputStream.skip, trying to read past the end of a BLOB failed with the exception "IO Exception\:Missing lob entry\:..." [90028-...].
changelog_1125_li=To test recovery, append ;RECOVER_TEST\=64 to the database URL. This will simulate an application crash after each 64 writes to the database file. A log file named databaseName.h2.db.log is created that lists the operations. The recovery is tested using an in-memory file system, that means it may require a larger heap setting.
changelog_1125_li=The in-memory file system "memFS\:" now has limited support for directories.
changelog_1126_li=Converting a hex string to a byte array is now faster.
changelog_1126_li=To test recovery, append ;RECOVER_TEST\=64 to the database URL. This will simulate an application crash after each 64 writes to the database file. A log file named databaseName.h2.db.log is created that lists the operations. The recovery is tested using an in-memory file system, that means it may require a larger heap setting.
changelog_1127_li=The SQL statement "shutdown defrag" could corrupt the database if the process was killed while the shutdown was in progress. The same problem could occur when the database setting "defrag_always" was used.
changelog_1127_li=Converting a hex string to a byte array is now faster.
changelog_1128_h2=Version 1.3.158 (2011-07-17)
changelog_1128_li=The SQL statement "shutdown defrag" could corrupt the database if the process was killed while the shutdown was in progress. The same problem could occur when the database setting "defrag_always" was used.
changelog_1129_li=Fulltext search (native)\:after re-opening the connection once the fulltext index was created, a transaction rollback did not roll back the modifications in the index.
changelog_1129_h2=Version 1.3.158 (2011-07-17)
changelog_1130_li=Support for ROW_NUMBER() OVER() as an alias for ROWNUM() for compatibility with PostgreSQL and Apache Derby.
changelog_1130_li=Fulltext search (native)\:after re-opening the connection once the fulltext index was created, a transaction rollback did not roll back the modifications in the index.
changelog_1131_li=Issue 325\:a deadlock in the fulltext search could occur if the connection that was used while initializing the fulltext search was later used to query the database. This was actually not only a problem for fulltext search, but also for other triggers that used the initializing connection later on.
changelog_1131_li=Support for ROW_NUMBER() OVER() as an alias for ROWNUM() for compatibility with PostgreSQL and Apache Derby.
changelog_1132_li=DATABASE_TO_UPPER\:when set to false, all identifier names (table names, column names) are case sensitive (except aggregate, built-in functions, data types, and keywords). This is for improved compatibility with MySQL and PostgreSQL.
changelog_1132_li=Issue 325\:a deadlock in the fulltext search could occur if the connection that was used while initializing the fulltext search was later used to query the database. This was actually not only a problem for fulltext search, but also for other triggers that used the initializing connection later on.
changelog_1133_li=When upgrading from an older 1.3.x version to version 1.3.157, when using BLOB or CLOB data, the database could only be opened once.
changelog_1133_li=DATABASE_TO_UPPER\:when set to false, all identifier names (table names, column names) are case sensitive (except aggregate, built-in functions, data types, and keywords). This is for improved compatibility with MySQL and PostgreSQL.
changelog_1134_li=SUM on a boolean expression will now count the number of 'true' rows.
changelog_1134_li=When upgrading from an older 1.3.x version to version 1.3.157, when using BLOB or CLOB data, the database could only be opened once.
changelog_1135_li=Simplified test cases using assertThrows(...).
changelog_1135_li=SUM on a boolean expression will now count the number of 'true' rows.
changelog_1136_li=A Java function that returns a result set that was generated using the provided connection could cause an internal error in some cases. Now such result sets are copied early on.
changelog_1136_li=Simplified test cases using assertThrows(...).
changelog_1137_li=Data type RESULT_SET\:information_schema.function_aliases returned type 0; now type -10 is returned (the same as Oracle\:OracleTypes.CURSOR \=-10).
changelog_1137_li=A Java function that returns a result set that was generated using the provided connection could cause an internal error in some cases. Now such result sets are copied early on.
changelog_1138_li=Data type RESULT_SET\:tables with columns of type RESULT_SET could be created, but no data could be persisted in this column.
changelog_1138_li=Data type RESULT_SET\:information_schema.function_aliases returned type 0; now type -10 is returned (the same as Oracle\:OracleTypes.CURSOR \=-10).
changelog_1139_li=H2 Console\:improved system tray icon for Mac OS X (transparent background).
changelog_1139_li=Data type RESULT_SET\:tables with columns of type RESULT_SET could be created, but no data could be persisted in this column.
changelog_1140_li=String.toUpperCase() was used a few places, which is problematic when using the Turkish locale. The method has been replaced with toUpperCase(Locale.ENGLISH) to solve such problems.
changelog_1140_li=H2 Console\:improved system tray icon for Mac OS X (transparent background).
changelog_1141_li=Shell tool\:the built-in command "distinct" has been removed (use the SQL statements "show tables" / "show columns from tableName" instead). The result set formatting has been improved.
changelog_1141_li=String.toUpperCase() was used a few places, which is problematic when using the Turkish locale. The method has been replaced with toUpperCase(Locale.ENGLISH) to solve such problems.
changelog_1142_li=MERGE\:if a unique key was violated (but not the primary key or the key columns of the merge itself), the wrong exception was thrown.
changelog_1142_li=Shell tool\:the built-in command "distinct" has been removed (use the SQL statements "show tables" / "show columns from tableName" instead). The result set formatting has been improved.
changelog_1143_li=IBM DB2 and Apache Derby compatibility\:support the pseudo-table SYSIBM.SYSDUMMY1.
changelog_1143_li=MERGE\:if a unique key was violated (but not the primary key or the key columns of the merge itself), the wrong exception was thrown.
changelog_1144_li=ROWNUM() did not work in combination with IN(..). The following query did not work as expected\:select * from (select rownum r from test) where r in (1, 2).
changelog_1144_li=IBM DB2 and Apache Derby compatibility\:support the pseudo-table SYSIBM.SYSDUMMY1.
changelog_1145_li=H2 Console autocomplete\:the autocomplete feature didn't support quoted names.
changelog_1145_li=ROWNUM() did not work in combination with IN(..). The following query did not work as expected\:select * from (select rownum r from test) where r in (1, 2).
changelog_1146_li=It is now longer allowed to create an index on a CLOB or BLOB column (except for in-memory databases or indexes), because recovery doesn't work on such columns. Fulltext indexes on such column are still supported of course.
changelog_1146_li=H2 Console autocomplete\:the autocomplete feature didn't support quoted names.
changelog_1147_li=The PUBLIC schema could be renamed, which could result in a database that can't be opened normally. Now it can no longer be renamed. The schema INFORMATION_SCHEMA can also no longer be renamed.
changelog_1147_li=It is now longer allowed to create an index on a CLOB or BLOB column (except for in-memory databases or indexes), because recovery doesn't work on such columns. Fulltext indexes on such column are still supported of course.
changelog_1148_li=Server mode\:the problem with server and client using different timezones with different daylight saving rules has been solved (this only applies when both the client and the server use this or a newer version).
changelog_1148_li=The PUBLIC schema could be renamed, which could result in a database that can't be opened normally. Now it can no longer be renamed. The schema INFORMATION_SCHEMA can also no longer be renamed.
changelog_1149_li=There is a new system property "h2.storeLocalTime" to avoid problems opening a database file in a timezone that has different daylight saving rules (see also below).
changelog_1149_li=Server mode\:the problem with server and client using different timezones with different daylight saving rules has been solved (this only applies when both the client and the server use this or a newer version).
changelog_1150_li=Date, time, and timestamp data type processing has been re-implemented. Time now supports nanoseconds resolution and now now supports a wider range (negative and large values), similar to PostgreSQL.
changelog_1150_li=There is a new system property "h2.storeLocalTime" to avoid problems opening a database file in a timezone that has different daylight saving rules (see also below).
changelog_1151_li=SQL statements with a non-breaking space were considered invalid.
changelog_1151_li=Date, time, and timestamp data type processing has been re-implemented. Time now supports nanoseconds resolution and now now supports a wider range (negative and large values), similar to PostgreSQL.
changelog_1152_h2=Version 1.3.157 (2011-06-25)
changelog_1152_li=SQL statements with a non-breaking space were considered invalid.
changelog_1153_li=The syntax for CREATE TABLE ... AS SELECT ... has been changed\:options such as NOT PERSISTENT are now before the query (AS SELECT), because otherwise they might be interpreted as a part of the query.
changelog_1153_h2=Version 1.3.157 (2011-06-25)
changelog_1154_li=With version 1.3.156, the DB2 mode could not be used with CLOB and BLOB data.
changelog_1154_li=The syntax for CREATE TABLE ... AS SELECT ... has been changed\:options such as NOT PERSISTENT are now before the query (AS SELECT), because otherwise they might be interpreted as a part of the query.
changelog_1155_li=When upgrading from an older 1.3.x version to version 1.3.156, CLOB and BLOB data was lost in many cases.
changelog_1155_li=With version 1.3.156, the DB2 mode could not be used with CLOB and BLOB data.
changelog_1156_li=The optimization for COUNT(..) on columns that are not nullable was also used for COUNT(DISTINCT ..), which is incorrect.
changelog_1156_li=When upgrading from an older 1.3.x version to version 1.3.156, CLOB and BLOB data was lost in many cases.
changelog_1157_li=PgServer\:non-admin users could not open a database.
changelog_1157_li=The optimization for COUNT(..) on columns that are not nullable was also used for COUNT(DISTINCT ..), which is incorrect.
changelog_1158_li=Non-admin users could not open a database using a mode (MODE\=xxx) if the database was already open, even if the mode matched.
changelog_1158_li=PgServer\:non-admin users could not open a database.
changelog_1159_li=The SQL state of the following exceptions has been changed\:From 90009, 90010, 90011 to 22007\:"Cannot parse DATE/TIME/TIMESTAMP constant ...".
changelog_1159_li=Non-admin users could not open a database using a mode (MODE\=xxx) if the database was already open, even if the mode matched.
changelog_1160_li=There is a problem when opening a database file in a timezone that has different daylight saving rules\:the time part of dates where the daylight saving doesn't match will differ. This is not a problem within regions that use the same rules (such as, within USA, or within Europe), even if the timezone itself is different. As a workaround, export the database to a SQL script using the old timezone, and create a new database in the new timezone. The same problem occurs when accessing a database over TCP/IP if the client and server timezones use different rules, if an old server or client is used.
changelog_1160_li=The SQL state of the following exceptions has been changed\:From 90009, 90010, 90011 to 22007\:"Cannot parse DATE/TIME/TIMESTAMP constant ...".
changelog_1161_h2=Version 1.3.156 (2011-06-17)
changelog_1161_li=There is a problem when opening a database file in a timezone that has different daylight saving rules\:the time part of dates where the daylight saving doesn't match will differ. This is not a problem within regions that use the same rules (such as, within USA, or within Europe), even if the timezone itself is different. As a workaround, export the database to a SQL script using the old timezone, and create a new database in the new timezone. The same problem occurs when accessing a database over TCP/IP if the client and server timezones use different rules, if an old server or client is used.
changelog_1162_li=Issue 323\:NullPointerException when using IN(...) with a function table.
changelog_1162_h2=Version 1.3.156 (2011-06-17)
changelog_1163_li=Clob.toString() and Blob.toString() now include the trace identifier.
changelog_1163_li=Issue 323\:NullPointerException when using IN(...) with a function table.
changelog_1164_li=The SQL parser silently ignored characters such as '^' or '\\'. Now a syntax error is thrown.
changelog_1164_li=Clob.toString() and Blob.toString() now include the trace identifier.
changelog_1165_li=ROUND(..) now also works with just one parameter.
changelog_1165_li=The SQL parser silently ignored characters such as '^' or '\\'. Now a syntax error is thrown.
changelog_1166_li=Access to system tables is now more restrictive for non-admin users (the tables can be still listed, but some of the data is not included).
changelog_1166_li=ROUND(..) now also works with just one parameter.
changelog_1167_li=BLOB\:InputStream.skip is now more efficient in embedded mode.
changelog_1167_li=Access to system tables is now more restrictive for non-admin users (the tables can be still listed, but some of the data is not included).
changelog_1168_li=The default expression of a column may no longer reference the table, because a database with such a table couldn't be opened normally.
changelog_1168_li=BLOB\:InputStream.skip is now more efficient in embedded mode.
changelog_1169_li=Referenced objects in check constraints could be dropped, which resulted in a database that can't be opened normally.
changelog_1169_li=The default expression of a column may no longer reference the table, because a database with such a table couldn't be opened normally.
changelog_1170_li=Improved Oracle compatibility for NVL2. Thanks again to litailang for the patch.
changelog_1170_li=Referenced objects in check constraints could be dropped, which resulted in a database that can't be opened normally.
changelog_1171_li=CSVREAD now supports the option 'preserveWhitespace'.
changelog_1171_li=Improved Oracle compatibility for NVL2. Thanks again to litailang for the patch.
changelog_1172_li=Recursive queries with many rows could throw an IndexOutOfBoundsException.
changelog_1172_li=CSVREAD now supports the option 'preserveWhitespace'.
changelog_1173_li=The auto-server mode can't be combined with an in-memory database. This invalid combination wasn't detected so far. Now trying to open a database in this way fails.
changelog_1173_li=Recursive queries with many rows could throw an IndexOutOfBoundsException.
changelog_1174_li=Improved performance for reading and writing date and time values.
changelog_1174_li=The auto-server mode can't be combined with an in-memory database. This invalid combination wasn't detected so far. Now trying to open a database in this way fails.
changelog_1175_li=Java functions\:array component types are now preserved, so that a ResultSet.getObject() will return Integer[] if the Java functions returns Integer[]. Thanks to Noel Grandin for the patch. Component types are transferred over the network, but not persisted in the database file as of now.
changelog_1175_li=Improved performance for reading and writing date and time values.
changelog_1176_li=Recover tool\:the script generated by the recover tool didn't work if fulltext search was used, because the triggers were created before the primary keys.
changelog_1176_li=Java functions\:array component types are now preserved, so that a ResultSet.getObject() will return Integer[] if the Java functions returns Integer[]. Thanks to Noel Grandin for the patch. Component types are transferred over the network, but not persisted in the database file as of now.
changelog_1177_li=Issue 321\:the database does not expect XA rollback without XA prepare (an exception was unnecessarily written into the .trace.db file).
changelog_1177_li=Recover tool\:the script generated by the recover tool didn't work if fulltext search was used, because the triggers were created before the primary keys.
changelog_1178_li=Read-only databases\:some queries (such as distinct queries) tried to create temporary tables, which failed for read only databases.
changelog_1178_li=Issue 321\:the database does not expect XA rollback without XA prepare (an exception was unnecessarily written into the .trace.db file).
changelog_1179_li=This database no longer uses finalize() except for temporary files. The system property "h2.runFinalize" is no longer supported. Unclosed connections are still detected, but the opening stack trace is now collected only if connections are not closed repeatedly (starting with the second unclosed connection). To detect unclosed connections, a PhantomReference is used.
changelog_1179_li=Read-only databases\:some queries (such as distinct queries) tried to create temporary tables, which failed for read only databases.
changelog_1180_li=Issue 322\:Left joins didn't work when used as subquery in the form clause.
changelog_1180_li=This database no longer uses finalize() except for temporary files. The system property "h2.runFinalize" is no longer supported. Unclosed connections are still detected, but the opening stack trace is now collected only if connections are not closed repeatedly (starting with the second unclosed connection). To detect unclosed connections, a PhantomReference is used.
changelog_1181_li=A prepared statement if type CALL that returned a result set could throw a NullPointerException if executed multiple times.
changelog_1181_li=Issue 322\:Left joins didn't work when used as subquery in the form clause.
changelog_1182_li=The following built-in functions were marked as deterministic and therefore not re-executed when using in a prepared statement\:LOCK_TIMEOUT, LINK_SCHEMA, CANCEL_SESSION, FILE_READ.
changelog_1182_li=A prepared statement if type CALL that returned a result set could throw a NullPointerException if executed multiple times.
changelog_1183_li=Count on a column that can not be null is now optimized to COUNT(*). Thanks a lot to Ross Judson for providing a patch and test case\!
changelog_1183_li=The following built-in functions were marked as deterministic and therefore not re-executed when using in a prepared statement\:LOCK_TIMEOUT, LINK_SCHEMA, CANCEL_SESSION, FILE_READ.
changelog_1184_li=The following prepared statements are now cached as well\:insert, update, delete, call, merge, and transactional commands.
changelog_1184_li=Count on a column that can not be null is now optimized to COUNT(*). Thanks a lot to Ross Judson for providing a patch and test case\!
changelog_1185_li=The built-in connection pool is now a bit faster.
changelog_1185_li=The following prepared statements are now cached as well\:insert, update, delete, call, merge, and transactional commands.
changelog_1186_li=The scale was not set correctly in some cases when using CREATE TABLE AS SELECT if there was no explicit column definition.
changelog_1186_li=The built-in connection pool is now a bit faster.
changelog_1187_li=When trying to connect to a server using TCP/IP failed, it will retry at most until the timeout. Before, it was the timeout multiplied with the retry count.
changelog_1187_li=The scale was not set correctly in some cases when using CREATE TABLE AS SELECT if there was no explicit column definition.
changelog_1188_h2=Version 1.3.155 (2011-05-27)
changelog_1188_li=When trying to connect to a server using TCP/IP failed, it will retry at most until the timeout. Before, it was the timeout multiplied with the retry count.
changelog_1189_li=When altering a table with triggers, new triggers are created and initialized with a table name that ends with tableName_COPY_x_y. The plan is that this will not be required in future versions.
changelog_1189_h2=Version 1.3.155 (2011-05-27)
changelog_1190_li=If some of the file system operations failed, System.gc() was called in a loop. Now it is called once at most.
changelog_1190_li=When altering a table with triggers, new triggers are created and initialized with a table name that ends with tableName_COPY_x_y. The plan is that this will not be required in future versions.
changelog_1191_li=Triggers (including the fulltext search) could throw the exception 'Unexpected code path' in Session.log.
changelog_1191_li=If some of the file system operations failed, System.gc() was called in a loop. Now it is called once at most.
changelog_1192_li=CURRENT_TIMESTAMP() and so on now return the same value within a transaction.
changelog_1192_li=Triggers (including the fulltext search) could throw the exception 'Unexpected code path' in Session.log.
changelog_1193_li=The statement CALL no longer converts an ARRAY return value to a list of values. Now an ARRAY is returned.
changelog_1193_li=CURRENT_TIMESTAMP() and so on now return the same value within a transaction.
changelog_1194_li=VALUES is now supported as a standalone command and as a table source\:SELECT * FROM (VALUES(1, 'Hello'), (2, 'World')) AS V;
changelog_1194_li=The statement CALL no longer converts an ARRAY return value to a list of values. Now an ARRAY is returned.
changelog_1195_li=TIMESTAMPADD is now an alias for DATEADD. Most SQL_TSI_ constants are now supported for for TIMESTAMPADD and TIMESTAMPDIFF (all except SQL_TSI_QUARTER and SQL_TSI_FRAC_SECOND).
changelog_1195_li=VALUES is now supported as a standalone command and as a table source\:SELECT * FROM (VALUES(1, 'Hello'), (2, 'World')) AS V;
changelog_1196_li=Issue 313\:NullPointerException in select query with a subquery or view.
changelog_1196_li=TIMESTAMPADD is now an alias for DATEADD. Most SQL_TSI_ constants are now supported for for TIMESTAMPADD and TIMESTAMPDIFF (all except SQL_TSI_QUARTER and SQL_TSI_FRAC_SECOND).
changelog_1197_li=Native fulltext search\:the characters '<', '>', and '\\' are now also whitespace characters. Also, the list of whitespace characters can be changed using FullText.setWhitespaceChars(conn, ...)
changelog_1197_li=Issue 313\:NullPointerException in select query with a subquery or view.
changelog_1198_li=When reading from the classpath (for example read_file('classpath\:logo.png')), now the content class loader is used if the resource can't be found otherwise.
changelog_1198_li=Native fulltext search\:the characters '<', '>', and '\\' are now also whitespace characters. Also, the list of whitespace characters can be changed using FullText.setWhitespaceChars(conn, ...)
changelog_1199_li=The statement "script drop" create a script that couldn't be executed if a table contained a reference to a user defined function.
changelog_1199_li=When reading from the classpath (for example read_file('classpath\:logo.png')), now the content class loader is used if the resource can't be found otherwise.
changelog_1200_li=Opening a database with both multi-threaded mode and lock mode 0 (disable locking) was possible (but only once), even thought it does not work properly. Now it is no longer allowed.
changelog_1200_li=The statement "script drop" create a script that couldn't be executed if a table contained a reference to a user defined function.
changelog_1201_li=LOB objects are now deleted (and the empty space is reused) when the transaction is committed. So far, the space wasn't re-used until the connection was closed.
changelog_1201_li=Opening a database with both multi-threaded mode and lock mode 0 (disable locking) was possible (but only once), even thought it does not work properly. Now it is no longer allowed.
changelog_1202_li=SCRIPT DROP did not use the cascade option for table, which would cause problems if a view was dropped before a table it depends on. Now the cascade option is used.
changelog_1202_li=LOB objects are now deleted (and the empty space is reused) when the transaction is committed. So far, the space wasn't re-used until the connection was closed.
changelog_1203_li=The query plan of queries with subqueries that contain nested joins was wrong. This could result in syntax exceptions for correct queries. Example\:select 1 from (select 2 from ((test t1 inner join test t2 on t1.id\=t2.id) inner join test t3 on t3.id\=t1.id)) x;
changelog_1203_li=SCRIPT DROP did not use the cascade option for table, which would cause problems if a view was dropped before a table it depends on. Now the cascade option is used.
changelog_1204_li=DatabaseEventListener.init was called with a null url when using the server mode.
changelog_1204_li=The query plan of queries with subqueries that contain nested joins was wrong. This could result in syntax exceptions for correct queries. Example\:select 1 from (select 2 from ((test t1 inner join test t2 on t1.id\=t2.id) inner join test t3 on t3.id\=t1.id)) x;
changelog_1205_li=Support for the function LN (an alias for LOG).
changelog_1205_li=DatabaseEventListener.init was called with a null url when using the server mode.
changelog_1206_li=Support for the function CEIL (an alias for CEILING).
changelog_1206_li=Support for the function LN (an alias for LOG).
changelog_1207_li=Issue 315\:Access to LOBs could cause a Java level deadlock.
changelog_1207_li=Support for the function CEIL (an alias for CEILING).
changelog_1208_li=Support for the ICU4J collator.
changelog_1208_li=Issue 315\:Access to LOBs could cause a Java level deadlock.
changelog_1209_li=Improved Oracle compatibility\:support for NVL2. Thanks to litailang for the patch\!
changelog_1209_li=Support for the ICU4J collator.
changelog_1210_li=Improved PostgreSQL compatibility\:support for RANDOM() in addition to RAND().
changelog_1210_li=Improved Oracle compatibility\:support for NVL2. Thanks to litailang for the patch\!
changelog_1211_li=There was a classloader memory leak problem because a class contained a static references to an exception (including stack trace).
changelog_1211_li=Improved PostgreSQL compatibility\:support for RANDOM() in addition to RAND().
changelog_1212_li=Split file system\:truncating a file now deletes the parts in reverse order, so that the file list is consistent if the process is interrupted while truncating.
changelog_1212_li=There was a classloader memory leak problem because a class contained a static references to an exception (including stack trace).
changelog_1213_li=The H2 JDBC client can now be used in an unsigned Applet. The problem was that System.getProperty throws a SecurityException, which is now ignored.
changelog_1213_li=Split file system\:truncating a file now deletes the parts in reverse order, so that the file list is consistent if the process is interrupted while truncating.
changelog_1214_li=The condition "in(select ...)" did not work correctly if the subquery could not be converted to a "distinct" query, as in\:"select * from dual where x in (select x from dual group by x order by max(x))". Now the subquery needs to be made distinct manually if this optimization is needed.
changelog_1214_li=The H2 JDBC client can now be used in an unsigned Applet. The problem was that System.getProperty throws a SecurityException, which is now ignored.
changelog_1215_li=In the last release, the error code for "Wrong user name or password" was still 08004 instead of 28000, which resulted in the wrong error message.
changelog_1215_li=The condition "in(select ...)" did not work correctly if the subquery could not be converted to a "distinct" query, as in\:"select * from dual where x in (select x from dual group by x order by max(x))". Now the subquery needs to be made distinct manually if this optimization is needed.
changelog_1216_li=In some cases, creating a new table or altering an existing table threw the exception\:Unique index or primary key violation\:"PRIMARY KEY ON """".PAGE_INDEX".
changelog_1216_li=In the last release, the error code for "Wrong user name or password" was still 08004 instead of 28000, which resulted in the wrong error message.
changelog_1217_li=The Shell tool no longer supports the built-in command "show", because it is a legal SQL statement for H2 and MySQL. However, the "describe" command is still supported, and now lists all tables if called without parameter.
changelog_1217_li=In some cases, creating a new table or altering an existing table threw the exception\:Unique index or primary key violation\:"PRIMARY KEY ON """".PAGE_INDEX".
changelog_1218_li=The sorted insert mode (as in "insert into ... direct sorted select") did not work for not-persisted tables in a persisted database. It threw a ClassCastException.
changelog_1218_li=The Shell tool no longer supports the built-in command "show", because it is a legal SQL statement for H2 and MySQL. However, the "describe" command is still supported, and now lists all tables if called without parameter.
changelog_1219_li=Issue 308\:Statement.getGeneratedKeys() now returns an empty result set if no key was generated.
changelog_1219_li=The sorted insert mode (as in "insert into ... direct sorted select") did not work for not-persisted tables in a persisted database. It threw a ClassCastException.
changelog_1220_li=The h2small.jar (created with build jarSmall) included the Android API. This has been removed, shrinking the jar file by 21 KB.
changelog_1220_li=Issue 308\:Statement.getGeneratedKeys() now returns an empty result set if no key was generated.
changelog_1221_li=When creating a table, the precision must now be at least as large as the scale.
changelog_1221_li=The h2small.jar (created with build jarSmall) included the Android API. This has been removed, shrinking the jar file by 21 KB.
changelog_1222_li=Support for Java 1.3 and Java 1.4 has been removed.
changelog_1222_li=When creating a table, the precision must now be at least as large as the scale.
changelog_1223_li=Improved error message for syntax error\:the list of expected tokens was sometimes not set correctly.
changelog_1223_li=Support for Java 1.3 and Java 1.4 has been removed.
changelog_1224_li=Database file growth can now be limited using the database setting PAGE_STORE_MAX_GROWTH. Slower growth may slow down operation, but speed up closing database.
changelog_1224_li=Improved error message for syntax error\:the list of expected tokens was sometimes not set correctly.
changelog_1225_li=A read only database with writable linked tables could lead to a DATABASE_IS_READ_ONLY (90097) error. This is fixed now.
changelog_1225_li=Database file growth can now be limited using the database setting PAGE_STORE_MAX_GROWTH. Slower growth may slow down operation, but speed up closing database.
changelog_1226_h2=Version 1.3.154 (2011-04-04)
changelog_1226_li=A read only database with writable linked tables could lead to a DATABASE_IS_READ_ONLY (90097) error. This is fixed now.
changelog_1227_li=The SQL state of the following exceptions has been changed\:From 90005 to 22001\:"Value too long for column ...\: ...". From 90039 to 22003\:"The value is too large for the precision ..."is merged with "Numeric value out of range". From 90110 to 22003\:"... out of range"is merged with "Numeric value out of range". From 90021 to 22018\:"Data conversion error converting ...". From 90006 to 23502\:"NULL not allowed for column ...". From 23003 to 23503\:"Referential integrity constraint violation\: ...". From 23001 to 23505\:"Unique index or primary key violation\: ...". From 23002 to 23506\:"Referential integrity constraint violation\: ...". From 90056 to 23507\:"No default value is set for column ...". From 23000 to 23513\:"Check constraint violation\: ...". From 08004 to 28000\:"Wrong user name or password". From 90051 to 57014\:"Statement was canceled or the session timed out".
changelog_1227_h2=Version 1.3.154 (2011-04-04)
changelog_1228_li=The H2 Console now detects unsupported command line options. (In the future, it will be combined with the Server tool.)
changelog_1228_li=The SQL state of the following exceptions has been changed\:From 90005 to 22001\:"Value too long for column ...\: ...". From 90039 to 22003\:"The value is too large for the precision ..."is merged with "Numeric value out of range". From 90110 to 22003\:"... out of range"is merged with "Numeric value out of range". From 90021 to 22018\:"Data conversion error converting ...". From 90006 to 23502\:"NULL not allowed for column ...". From 23003 to 23503\:"Referential integrity constraint violation\: ...". From 23001 to 23505\:"Unique index or primary key violation\: ...". From 23002 to 23506\:"Referential integrity constraint violation\: ...". From 90056 to 23507\:"No default value is set for column ...". From 23000 to 23513\:"Check constraint violation\: ...". From 08004 to 28000\:"Wrong user name or password". From 90051 to 57014\:"Statement was canceled or the session timed out".
changelog_1229_li=MySQL compatibility\:SHOW COLUMN FOR schemaName.columnName.
changelog_1229_li=The H2 Console now detects unsupported command line options. (In the future, it will be combined with the Server tool.)
changelog_1230_li=DatabaseMetaData.getCrossReference now also lists the name of the primary index (PK_NAME).
changelog_1230_li=MySQL compatibility\:SHOW COLUMN FOR schemaName.columnName.
changelog_1231_li=If the database contained many CLOB or BLOB values, then closing a connection was very slow. Reason\:was that when closing a connection, the temporary CLOB and BLOB values for this connection were removed, but there was no index on this column. For existing databases with many CLOB and BLOB values, creating the index may take a few seconds. The index is added to existing databases automatically.
changelog_1231_li=DatabaseMetaData.getCrossReference now also lists the name of the primary index (PK_NAME).
changelog_1232_li=If a CLOB or BLOB was copied into the same table using INSERT INTO X ... SELECT ... FROM X, and then the original row was deleted, then the copied value was also deleted. This could also result in an ArrayIndexOutOfBoundsException on checkpoint or when closing the database.
changelog_1232_li=If the database contained many CLOB or BLOB values, then closing a connection was very slow. Reason\:was that when closing a connection, the temporary CLOB and BLOB values for this connection were removed, but there was no index on this column. For existing databases with many CLOB and BLOB values, creating the index may take a few seconds. The index is added to existing databases automatically.
changelog_1233_li=Improved performance (up to 10%) due to changed synchronization in the page store.
changelog_1233_li=If a CLOB or BLOB was copied into the same table using INSERT INTO X ... SELECT ... FROM X, and then the original row was deleted, then the copied value was also deleted. This could also result in an ArrayIndexOutOfBoundsException on checkpoint or when closing the database.
changelog_1234_li=Reading a resource from the classpath didn't work if there was a leading slash (classpath\:/org/...). Now resources can be loaded with or without leading slash.
changelog_1234_li=Improved performance (up to 10%) due to changed synchronization in the page store.
changelog_1235_li=Support INSERT INTO TEST SET ID \=1, NAME \='World'(MySQL compatibility).
changelog_1235_li=Reading a resource from the classpath didn't work if there was a leading slash (classpath\:/org/...). Now resources can be loaded with or without leading slash.
changelog_1236_li=Issue 304\:The condition [NOT] IN (SELECT ...) could throw the exception "Unexpected code path" if the subquery contained ORDER BY.
changelog_1236_li=Support INSERT INTO TEST SET ID \=1, NAME \='World'(MySQL compatibility).
changelog_1237_li=ALTER TABLE ALTER ADD / REMOVE /ALTER COLUMN dropped some dependent objects (access rights, triggers) of views that depend on the modified table.
changelog_1237_li=Issue 304\:The condition [NOT] IN (SELECT ...) could throw the exception "Unexpected code path" if the subquery contained ORDER BY.
changelog_1238_li=CREATE OR REPLACE VIEW dropped some dependent objects (access rights, triggers) if the view already existed before.
changelog_1238_li=ALTER TABLE ALTER ADD / REMOVE /ALTER COLUMN dropped some dependent objects (access rights, triggers) of views that depend on the modified table.
changelog_1239_li=New aggregate function HISTOGRAM to calculate the histogram. The plan is to use this function is only used internally when running ANALYZE to generate the histogram that is then used by the query optimizer.
changelog_1239_li=CREATE OR REPLACE VIEW dropped some dependent objects (access rights, triggers) if the view already existed before.
changelog_1240_li=New system function TRUNCATE_VALUE to truncate a value to the required precision. This is the same as for CAST, but without changing the data type, and support for truncating decimal values. (The main use case for this function is to build a histogram of the truncated values). Now BINARY, BLOB, and CLOB can be truncated / cast efficiently as well.
changelog_1240_li=New aggregate function HISTOGRAM to calculate the histogram. The plan is to use this function is only used internally when running ANALYZE to generate the histogram that is then used by the query optimizer.
changelog_1241_li=The precision of an ARRAY value is now the sum of the precision of all elements, and result set values have the precision Integer.MAX_VALUE.
changelog_1241_li=New system function TRUNCATE_VALUE to truncate a value to the required precision. This is the same as for CAST, but without changing the data type, and support for truncating decimal values. (The main use case for this function is to build a histogram of the truncated values). Now BINARY, BLOB, and CLOB can be truncated / cast efficiently as well.
changelog_1242_li=CAST(x AS VARCHAR_IGNORECASE(y) / CHAR(y)) returned a VARCHAR if the new precision was lower than the old precision.
changelog_1242_li=The precision of an ARRAY value is now the sum of the precision of all elements, and result set values have the precision Integer.MAX_VALUE.
changelog_1243_li=SHUTDOWN DEFRAG didn't defragment the database completely if there was a unique hash index for a memory table.
changelog_1243_li=CAST(x AS VARCHAR_IGNORECASE(y) / CHAR(y)) returned a VARCHAR if the new precision was lower than the old precision.
changelog_1244_li=There were some smaller changes in the encrypting file system (work in progress).
changelog_1244_li=SHUTDOWN DEFRAG didn't defragment the database completely if there was a unique hash index for a memory table.
changelog_1245_li=Some time and timezone functions didn't support years before 1.
changelog_1245_li=There were some smaller changes in the encrypting file system (work in progress).
changelog_1246_li=Some time and timezone functions didn't support years before 1.
