@@ -281,13 +281,13 @@ Multi-Version Concurrency Control (MVCC)
...
@@ -281,13 +281,13 @@ Multi-Version Concurrency Control (MVCC)
To use the MVCC feature, append <code>;MVCC=TRUE</code> to the database URL:
To use the MVCC feature, append <code>;MVCC=TRUE</code> to the database URL:
@advanced_1094_p
@advanced_1094_p
MVCC is disabled by default. The MVCC feature is not fully tested yet. The limitations of the MVCC mode are: it can not be used at the same time as <code>MULTI_THREADED=TRUE</code>; the complete undo log (the list of uncommitted changes) must fit in memory when using multi-version concurrency. The setting <code>MAX_MEMORY_UNDO</code> has no effect. It is not possible to enable or disable this setting while the database is already open. The setting must be specified in the first connection (the one that opens the database).
The setting must be specified in the first connection (the one that opens the database). It is not possible to enable or disable this setting while the database is already open.
@advanced_1095_p
@advanced_1095_p
If MVCC is enabled, changing the lock mode (<code>LOCK_MODE</code>) has no effect.
If MVCC is enabled, changing the lock mode (<code>LOCK_MODE</code>) has no effect.
@advanced_1096_h2
@advanced_1096_div
Clustering / High Availability
The MVCC mode is enabled by default in version 1.4.x, with the default MVStore storage engine. MVCC is disabled by default when using the PageStore storage engine (which is the default in version 1.3.x). The following applies when using the PageStore storage engine: The MVCC feature is not fully tested yet. The limitations of the MVCC mode are: with the PageStore storage engine, it can not be used at the same time as <code>MULTI_THREADED=TRUE</code>; the complete undo log (the list of uncommitted changes) must fit in memory when using multi-version concurrency. The setting <code>MAX_MEMORY_UNDO</code> has no effect. Clustering / High Availability
@advanced_1097_p
@advanced_1097_p
This database supports a simple clustering / high availability mechanism. The architecture is: two database servers run on two different computers, and on both computers is a copy of the same database. If both servers run, each database operation is executed on both computers. If one server fails (power, hardware or network failure), the other server can still continue to work. From this point on, the operations will be executed only on one server until the other server is back up.
This database supports a simple clustering / high availability mechanism. The architecture is: two database servers run on two different computers, and on both computers is a copy of the same database. If both servers run, each database operation is executed on both computers. If one server fails (power, hardware or network failure), the other server can still continue to work. From this point on, the operations will be executed only on one server until the other server is back up.
...
@@ -1889,561 +1889,630 @@ Change Log
...
@@ -1889,561 +1889,630 @@ Change Log
Next Version (unreleased)
Next Version (unreleased)
@changelog_1002_li
@changelog_1002_li
-
MVStore: concurrent changes to the same row could result in the exception "The transaction log might be corrupt for key ...". This could only be reproduced with 3 or more threads.
@changelog_1003_h2
@changelog_1003_li
Version 1.4.186 Beta (2015-03-02)
Results with CLOB or BLOB data are no longer reused.
@changelog_1004_li
@changelog_1004_li
The Servlet API 3.0.1 is now used, instead of 2.4.
References to BLOB and CLOB objects now have a timeout. The configuration setting is LOB_TIMEOUT (default 5 minutes). This should avoid growing the database file if there are many queries that return BLOB or CLOB objects, and the database is not closed for a longer time.
@changelog_1005_li
@changelog_1005_li
MVStore: old chunks no longer removed in append-only mode.
MVStore: when committing a session that removed LOB values, changes were flushed unnecessarily.
@changelog_1006_li
@changelog_1006_li
MVStore: the cache for page references could grow far too big, resulting in out of memory in some cases.
Issue 610: possible integer overflow in WriteBuffer.grow().
@changelog_1007_li
@changelog_1007_li
MVStore: orphaned lob objects were not correctly removed in some cases, making the database grow unnecessarily.
Issue 609: the spatial index did not support NULL (ClassCastException).
@changelog_1008_li
@changelog_1008_li
MVStore: the maximum cache size was artificially limited to 2 GB (due to an integer overflow).
MVStore: in some cases, CLOB/BLOB data blocks were removed incorrectly when opening a database.
@changelog_1009_li
@changelog_1009_li
MVStore / TransactionStore: concurrent updates could result in a "Too many open transactions" exception.
MVStore: updates that affected many rows were were slow in some cases if there was a secondary index.
@changelog_1010_li
@changelog_1010_li
StringUtils.toUpperEnglish now has a small cache. This should speed up reading from a ResultSet when using the column name.
Using "runscript" with autocommit disabled could result in a lock timeout on the internal table "SYS".
@changelog_1011_li
@changelog_1011_li
MVStore: up to 65535 open transactions are now supported. Previously, the limit was at most 65535 transactions between the oldest open and the newest open transaction (which was quite a strange limit).
Issue 603: there was a memory leak when using H2 in a web application. Apache Tomcat logged an error message: "The web application ... created a ThreadLocal with key of type [org.h2.util.DateTimeUtils$1]".
@changelog_1012_li
@changelog_1012_li
The default limit for in-place LOB objects was changed from 128 to 256 bytes. This is because each read creates a reference to a LOB, and maintaining the references is a big overhead. With the higher limit, less references are needed.
When using the MVStore, running a SQL script generate by the Recover tool from a PageStore file failed with a strange error message (NullPointerException), now a clear error message is shown.
@changelog_1013_li
@changelog_1013_li
Tables without columns didn't work. (The use case for such tables is testing.)
Issue 605: with version 1.4.186, opening a database could result in an endless loop in LobStorageMap.init.
@changelog_1014_li
@changelog_1014_li
The LIRS cache now resizes the table automatically in all cases and no longer needs the averageMemory configuration.
Queries that use the same table alias multiple times now work. Before, the select expression list was expanded incorrectly. Example: "select * from a as x, b as x".
@changelog_1015_li
@changelog_1015_li
Creating a linked table from an MVStore database to a non-MVStore database created a second (non-MVStore) database file.
The MySQL compatibility feature "insert ... on duplicate key update" did not work with a non-default schema.
@changelog_1016_li
@changelog_1016_li
In version 1.4.184, a bug was introduced that broke queries that have both joins and wildcards, for example: select * from dual join(select x from dual) on 1=1
Issue 599: the condition "in(x, y)" could not be used in the select list when using "group by".
@changelog_1017_li
@changelog_1017_li
Issue 598: parser fails on timestamp "24:00:00.1234" - prevent the creation of out-of-range time values.
The LIRS cache could grow larger than the allocated memory.
@changelog_1018_li
@changelog_1018_li
Allow declaring triggers as source code (like functions). Patch by Sylvain Cuaz.
A new file system implementation that re-opens the file if it was closed due to the application calling Thread.interrupt(). File name prefix "retry:". Please note it is strongly recommended to avoid calling Thread.interrupt; this is a problem for various libraries, including Apache Lucene.
@changelog_1019_li
@changelog_1019_li
Make the planner use indexes for sorting when doing a GROUP BY where all of the GROUP BY columns are not mentioned in the select. Patch by Frederico (zepfred).
MVStore: use RandomAccessFile file system if the file name starts with "file:".
@changelog_1020_li
@changelog_1020_li
PostgreSQL compatibility: generate_series (as an alias for system_range). Patch by litailang.
Allow DATEADD to take a long value for count when manipulating milliseconds.
@changelog_1021_li
@changelog_1021_li
When using MV_STORE=TRUE and the SET CACHE_SIZE setting, the cache size was incorrectly set, so that it was effectively 1024 times smaller than it should be.
@changelog_1022_li
Concurrent CREATE TABLE... IF NOT EXISTS in the presence of MULTI_THREAD=TRUE could throw an exception.
@changelog_1023_li
Fix bug in MVStore when creating lots of temporary tables, where we could run out of transaction IDs.
@changelog_1024_li
Add support for PostgreSQL STRING_AGG function. Patch by Fred Aquiles.
@changelog_1025_li
Fix bug in "jdbc:h2:nioMemFS" isRoot() function
@changelog_1026_h2
Version 1.4.186 Beta (2015-03-02)
@changelog_1027_li
The Servlet API 3.0.1 is now used, instead of 2.4.
@changelog_1028_li
MVStore: old chunks no longer removed in append-only mode.
@changelog_1029_li
MVStore: the cache for page references could grow far too big, resulting in out of memory in some cases.
@changelog_1030_li
MVStore: orphaned lob objects were not correctly removed in some cases, making the database grow unnecessarily.
@changelog_1031_li
MVStore: the maximum cache size was artificially limited to 2 GB (due to an integer overflow).
@changelog_1032_li
MVStore / TransactionStore: concurrent updates could result in a "Too many open transactions" exception.
@changelog_1033_li
StringUtils.toUpperEnglish now has a small cache. This should speed up reading from a ResultSet when using the column name.
@changelog_1034_li
MVStore: up to 65535 open transactions are now supported. Previously, the limit was at most 65535 transactions between the oldest open and the newest open transaction (which was quite a strange limit).
@changelog_1035_li
The default limit for in-place LOB objects was changed from 128 to 256 bytes. This is because each read creates a reference to a LOB, and maintaining the references is a big overhead. With the higher limit, less references are needed.
@changelog_1036_li
Tables without columns didn't work. (The use case for such tables is testing.)
@changelog_1037_li
The LIRS cache now resizes the table automatically in all cases and no longer needs the averageMemory configuration.
@changelog_1038_li
Creating a linked table from an MVStore database to a non-MVStore database created a second (non-MVStore) database file.
@changelog_1039_li
In version 1.4.184, a bug was introduced that broke queries that have both joins and wildcards, for example: select * from dual join(select x from dual) on 1=1
@changelog_1040_li
Issue 598: parser fails on timestamp "24:00:00.1234" - prevent the creation of out-of-range time values.
@changelog_1041_li
Allow declaring triggers as source code (like functions). Patch by Sylvain Cuaz.
@changelog_1042_li
Make the planner use indexes for sorting when doing a GROUP BY where all of the GROUP BY columns are not mentioned in the select. Patch by Frederico (zepfred).
@changelog_1043_li
PostgreSQL compatibility: generate_series (as an alias for system_range). Patch by litailang.
@changelog_1044_li
Fix missing "column" type in right-hand parameter in ConditionIn. Patch by Arnaud Thimel.
Fix missing "column" type in right-hand parameter in ConditionIn. Patch by Arnaud Thimel.
@changelog_1022_h2
@changelog_1045_h2
Version 1.4.185 Beta (2015-01-16)
Version 1.4.185 Beta (2015-01-16)
@changelog_1023_li
@changelog_1046_li
In version 1.4.184, "group by" ignored the table name, and could pick a select column by mistake. Example: select 0 as x from system_range(1, 2) d group by d.x;
In version 1.4.184, "group by" ignored the table name, and could pick a select column by mistake. Example: select 0 as x from system_range(1, 2) d group by d.x;
@changelog_1024_li
@changelog_1047_li
New connection setting "REUSE_SPACE" (default: true). If disabled, all changes are appended to the database file, and existing content is never overwritten. This allows to rollback to a previous state of the database by truncating the database file.
New connection setting "REUSE_SPACE" (default: true). If disabled, all changes are appended to the database file, and existing content is never overwritten. This allows to rollback to a previous state of the database by truncating the database file.
@changelog_1025_li
@changelog_1048_li
Issue 587: MVStore: concurrent compaction and store operations could result in an IllegalStateException.
Issue 587: MVStore: concurrent compaction and store operations could result in an IllegalStateException.
@changelog_1026_li
@changelog_1049_li
Issue 594: Profiler.copyInThread does not work properly.
Issue 594: Profiler.copyInThread does not work properly.
@changelog_1027_li
@changelog_1050_li
Script tool: Now, SCRIPT ... TO is always used (for higher speed and lower disk space usage).
Script tool: Now, SCRIPT ... TO is always used (for higher speed and lower disk space usage).
@changelog_1028_li
@changelog_1051_li
Script tool: Fix parsing of BLOCKSIZE parameter, original patch by Ken Jorissen.
Script tool: Fix parsing of BLOCKSIZE parameter, original patch by Ken Jorissen.
@changelog_1029_li
@changelog_1052_li
Fix bug in PageStore#commit method - when the ignoreBigLog flag was set, the logic that cleared the flag could never be reached, resulting in performance degradation. Reported by Alexander Nesterov.
Fix bug in PageStore#commit method - when the ignoreBigLog flag was set, the logic that cleared the flag could never be reached, resulting in performance degradation. Reported by Alexander Nesterov.
@changelog_1030_li
@changelog_1053_li
Issue 552: Implement BIT_AND and BIT_OR aggregate functions.
Issue 552: Implement BIT_AND and BIT_OR aggregate functions.
@changelog_1031_h2
@changelog_1054_h2
Version 1.4.184 Beta (2014-12-19)
Version 1.4.184 Beta (2014-12-19)
@changelog_1032_li
@changelog_1055_li
In version 1.3.183, indexes were not used if the table contains columns with a default value generated by a sequence. This includes tables with identity and auto-increment columns. This bug was introduced by supporting "rownum" in views and derived tables.
In version 1.3.183, indexes were not used if the table contains columns with a default value generated by a sequence. This includes tables with identity and auto-increment columns. This bug was introduced by supporting "rownum" in views and derived tables.
@changelog_1033_li
@changelog_1056_li
MVStore: imported BLOB and CLOB data sometimes disappeared. This was caused by a bug in the ObjectDataType comparison.
MVStore: imported BLOB and CLOB data sometimes disappeared. This was caused by a bug in the ObjectDataType comparison.
@changelog_1034_li
@changelog_1057_li
Reading from a StreamStore now throws an IOException if the underlying data doesn't exist.
Reading from a StreamStore now throws an IOException if the underlying data doesn't exist.
@changelog_1035_li
@changelog_1058_li
MVStore: if there is an exception while saving, the store is now in all cases immediately closed.
MVStore: if there is an exception while saving, the store is now in all cases immediately closed.
@changelog_1036_li
@changelog_1059_li
MVStore: the dump tool could go into an endless loop for some files.
MVStore: the dump tool could go into an endless loop for some files.
@changelog_1037_li
@changelog_1060_li
MVStore: recovery for a database with many CLOB or BLOB entries is now much faster.
MVStore: recovery for a database with many CLOB or BLOB entries is now much faster.
@changelog_1038_li
@changelog_1061_li
Group by with a quoted select column name alias didn't work. Example: select 1 "a" from dual group by "a"
Group by with a quoted select column name alias didn't work. Example: select 1 "a" from dual group by "a"
@changelog_1039_li
@changelog_1062_li
Auto-server mode: the host name is now stored in the .lock.db file.
Auto-server mode: the host name is now stored in the .lock.db file.
@changelog_1040_h2
@changelog_1063_h2
Version 1.4.183 Beta (2014-12-13)
Version 1.4.183 Beta (2014-12-13)
@changelog_1041_li
@changelog_1064_li
MVStore: the default auto-commit buffer size is now about twice as big. This should reduce the database file size after inserting a lot of data.
MVStore: the default auto-commit buffer size is now about twice as big. This should reduce the database file size after inserting a lot of data.
@changelog_1042_li
@changelog_1065_li
The built-in functions "power" and "radians" now always return a double.
The built-in functions "power" and "radians" now always return a double.
@changelog_1043_li
@changelog_1066_li
Using "row_number" or "rownum" in views or derived tables had unexpected results if the outer query contained constraints for the given view. Example: select b.nr, b.id from (select row_number() over() as nr, a.id as id from (select id from test order by name) as a) as b where b.id = 1
Using "row_number" or "rownum" in views or derived tables had unexpected results if the outer query contained constraints for the given view. Example: select b.nr, b.id from (select row_number() over() as nr, a.id as id from (select id from test order by name) as a) as b where b.id = 1
@changelog_1044_li
@changelog_1067_li
MVStore: the Recover tool can now deal with more types of corruption in the file.
MVStore: the Recover tool can now deal with more types of corruption in the file.
@changelog_1045_li
@changelog_1068_li
MVStore: the TransactionStore now first needs to be initialized before it can be used.
MVStore: the TransactionStore now first needs to be initialized before it can be used.
@changelog_1046_li
@changelog_1069_li
Views and derived tables with equality and range conditions on the same columns did not work properly. example: select x from (select x from (select 1 as x) where x > 0 and x < 2) where x = 1
Views and derived tables with equality and range conditions on the same columns did not work properly. example: select x from (select x from (select 1 as x) where x > 0 and x < 2) where x = 1
@changelog_1047_li
@changelog_1070_li
The database URL setting PAGE_SIZE setting is now also used for the MVStore.
The database URL setting PAGE_SIZE setting is now also used for the MVStore.
@changelog_1048_li
@changelog_1071_li
MVStore: the default page split size for persistent stores is now 4096 (it was 16 KB so far). This should reduce the database file size for most situations (in some cases, less than half the size of the previous version).
MVStore: the default page split size for persistent stores is now 4096 (it was 16 KB so far). This should reduce the database file size for most situations (in some cases, less than half the size of the previous version).
@changelog_1049_li
@changelog_1072_li
With query literals disabled, auto-analyze of a table with CLOB or BLOB did not work.
With query literals disabled, auto-analyze of a table with CLOB or BLOB did not work.
@changelog_1050_li
@changelog_1073_li
MVStore: use a mark and sweep GC algorithm instead of reference counting, to ensure used chunks are never overwrite, even if the reference counting algorithm does not work properly.
MVStore: use a mark and sweep GC algorithm instead of reference counting, to ensure used chunks are never overwrite, even if the reference counting algorithm does not work properly.
@changelog_1051_li
@changelog_1074_li
In the multi-threaded mode, updating the column selectivity ("analyze") in the background sometimes did not work.
In the multi-threaded mode, updating the column selectivity ("analyze") in the background sometimes did not work.
@changelog_1052_li
@changelog_1075_li
In the multi-threaded mode, database metadata operations did sometimes not work if the schema was changed at the same time (for example, if tables were dropped).
In the multi-threaded mode, database metadata operations did sometimes not work if the schema was changed at the same time (for example, if tables were dropped).
@changelog_1053_li
@changelog_1076_li
Some CLOB and BLOB values could no longer be read when the original row was removed (even when using the MVCC mode).
Some CLOB and BLOB values could no longer be read when the original row was removed (even when using the MVCC mode).
@changelog_1054_li
@changelog_1077_li
The MVStoreTool could throw an IllegalArgumentException.
The MVStoreTool could throw an IllegalArgumentException.
@changelog_1055_li
@changelog_1078_li
Improved performance for some date / time / timestamp conversion operations. Thanks to Sergey Evdokimov for reporting the problem.
Improved performance for some date / time / timestamp conversion operations. Thanks to Sergey Evdokimov for reporting the problem.
@changelog_1056_li
@changelog_1079_li
H2 Console: the built-in web server did not work properly if an unknown file was requested.
H2 Console: the built-in web server did not work properly if an unknown file was requested.
@changelog_1057_li
@changelog_1080_li
MVStore: the jar file is renamed to "h2-mvstore-*.jar" and is deployed to Maven separately.
MVStore: the jar file is renamed to "h2-mvstore-*.jar" and is deployed to Maven separately.
@changelog_1058_li
@changelog_1081_li
MVStore: support for concurrent reads and writes is now enabled by default.
MVStore: support for concurrent reads and writes is now enabled by default.
@changelog_1059_li
@changelog_1082_li
Server mode: the transfer buffer size has been changed from 16 KB to 64 KB, after it was found that this improves performance on Linux quite a lot.
Server mode: the transfer buffer size has been changed from 16 KB to 64 KB, after it was found that this improves performance on Linux quite a lot.
@changelog_1060_li
@changelog_1083_li
H2 Console and server mode: SSL is now disabled and TLS is used to protect against the Poodle SSLv3 vulnerability. The system property to disable secure anonymous connections is now "h2.enableAnonymousTLS". The default certificate is still self-signed, so you need to manually install another one if you want to avoid man in the middle attacks.
H2 Console and server mode: SSL is now disabled and TLS is used to protect against the Poodle SSLv3 vulnerability. The system property to disable secure anonymous connections is now "h2.enableAnonymousTLS". The default certificate is still self-signed, so you need to manually install another one if you want to avoid man in the middle attacks.
@changelog_1061_li
@changelog_1084_li
MVStore: the R-tree did not correctly measure the memory usage.
MVStore: the R-tree did not correctly measure the memory usage.
@changelog_1062_li
@changelog_1085_li
MVStore: compacting a store with an R-tree did not always work.
MVStore: compacting a store with an R-tree did not always work.
@changelog_1063_li
@changelog_1086_li
Issue 581: When running in LOCK_MODE=0, JdbcDatabaseMetaData#supportsTransactionIsolationLevel(TRANSACTION_READ_UNCOMMITTED) should return false
Issue 581: When running in LOCK_MODE=0, JdbcDatabaseMetaData#supportsTransactionIsolationLevel(TRANSACTION_READ_UNCOMMITTED) should return false
@changelog_1064_li
@changelog_1087_li
Fix bug which could generate deadlocks when multiple connections accessed the same table.
Fix bug which could generate deadlocks when multiple connections accessed the same table.
@changelog_1065_li
@changelog_1088_li
Some places in the code were not respecting the value set in the "SET MAX_MEMORY_ROWS x" command
Some places in the code were not respecting the value set in the "SET MAX_MEMORY_ROWS x" command
@changelog_1066_li
@changelog_1089_li
Fix bug which could generate a NegativeArraySizeException when performing large (>40M) row union operations
Fix bug which could generate a NegativeArraySizeException when performing large (>40M) row union operations
@changelog_1067_li
@changelog_1090_li
Fix "USE schema" command for MySQL compatibility, patch by mfulton
Fix "USE schema" command for MySQL compatibility, patch by mfulton
@changelog_1068_li
@changelog_1091_li
Parse and ignore the ROW_FORMAT=DYNAMIC MySQL syntax, patch by mfulton
Parse and ignore the ROW_FORMAT=DYNAMIC MySQL syntax, patch by mfulton
@changelog_1069_h2
@changelog_1092_h2
Version 1.4.182 Beta (2014-10-17)
Version 1.4.182 Beta (2014-10-17)
@changelog_1070_li
@changelog_1093_li
MVStore: improved error messages and logging; improved behavior if there is an error when serializing objects.
MVStore: improved error messages and logging; improved behavior if there is an error when serializing objects.
@changelog_1071_li
@changelog_1094_li
OSGi: the MVStore packages are now exported.
OSGi: the MVStore packages are now exported.
@changelog_1072_li
@changelog_1095_li
With the MVStore option, when using multiple threads that concurrently create indexes or tables, it was relatively easy to get a lock timeout on the "SYS" table.
With the MVStore option, when using multiple threads that concurrently create indexes or tables, it was relatively easy to get a lock timeout on the "SYS" table.
@changelog_1073_li
@changelog_1096_li
When using the multi-threaded option, the exception "Unexpected code path" could be thrown, specially if the option "analyze_auto" was set to a low value.
When using the multi-threaded option, the exception "Unexpected code path" could be thrown, specially if the option "analyze_auto" was set to a low value.
@changelog_1074_li
@changelog_1097_li
In the server mode, when reading from a CLOB or BLOB, if the connection was closed, a NullPointerException could be thrown instead of an exception saying the connection is closed.
In the server mode, when reading from a CLOB or BLOB, if the connection was closed, a NullPointerException could be thrown instead of an exception saying the connection is closed.
@changelog_1075_li
@changelog_1098_li
DatabaseMetaData.getProcedures and getProcedureColumns could throw an exception if a user defined class is not available.
DatabaseMetaData.getProcedures and getProcedureColumns could throw an exception if a user defined class is not available.
@changelog_1076_li
@changelog_1099_li
Issue 584: the error message for a wrong sequence definition was wrong.
Issue 584: the error message for a wrong sequence definition was wrong.
@changelog_1077_li
@changelog_1100_li
CSV tool: the rowSeparator option is no longer supported, as the same can be achieved with the lineSeparator.
CSV tool: the rowSeparator option is no longer supported, as the same can be achieved with the lineSeparator.
@changelog_1078_li
@changelog_1101_li
Descending indexes on MVStore tables did not work properly.
Descending indexes on MVStore tables did not work properly.
@changelog_1079_li
@changelog_1102_li
Issue 579: Conditions on the "_rowid_" pseudo-column didn't use an index when using the MVStore.
Issue 579: Conditions on the "_rowid_" pseudo-column didn't use an index when using the MVStore.
@changelog_1080_li
@changelog_1103_li
Fixed documentation that "offset" and "fetch" are also keywords since version 1.4.x.
Fixed documentation that "offset" and "fetch" are also keywords since version 1.4.x.
@changelog_1081_li
@changelog_1104_li
The Long.MIN_VALUE could not be parsed for auto-increment (identity) columns.
The Long.MIN_VALUE could not be parsed for auto-increment (identity) columns.
@changelog_1082_li
@changelog_1105_li
Issue 573: Add implementation for Methods "isWrapperFor()" and "unwrap()" in other JDBC classes.
Issue 573: Add implementation for Methods "isWrapperFor()" and "unwrap()" in other JDBC classes.
@changelog_1083_li
@changelog_1106_li
Issue 572: MySQL compatibility for "order by" in update statements.
Issue 572: MySQL compatibility for "order by" in update statements.
@changelog_1084_li
@changelog_1107_li
The change in JDBC escape processing in version 1.4.181 affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax "{t 'time}", or "{ts 'timestamp'}", or "{d 'data'}", then both the client and the server need to be upgraded to version 1.4.181 or later.
The change in JDBC escape processing in version 1.4.181 affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax "{t 'time}", or "{ts 'timestamp'}", or "{d 'data'}", then both the client and the server need to be upgraded to version 1.4.181 or later.
@changelog_1085_h2
@changelog_1108_h2
Version 1.4.181 Beta (2014-08-06)
Version 1.4.181 Beta (2014-08-06)
@changelog_1086_li
@changelog_1109_li
Improved MySQL compatibility by supporting "use schema". Thanks a lot to Karl Pietrzak for the patch!
Improved MySQL compatibility by supporting "use schema". Thanks a lot to Karl Pietrzak for the patch!
@changelog_1087_li
@changelog_1110_li
Writing to the trace file is now faster, specially with the debug level.
Writing to the trace file is now faster, specially with the debug level.
@changelog_1088_li
@changelog_1111_li
The database option "defrag_always=true" did not work with the MVStore.
The database option "defrag_always=true" did not work with the MVStore.
@changelog_1089_li
@changelog_1112_li
The JDBC escape syntax {ts 'value'} did not interpret the value as a timestamp. The same for {d 'value'} (for date) and {t 'value'} (for time). Thanks to Lukas Eder for reporting the issue. The following problem was detected after version 1.4.181 was released: The change in JDBC escape processing affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax {t 'time'}, or {ts 'timestamp'}, or {d 'date'}, then both the client and the server need to be upgraded to version 1.4.181 or later.
The JDBC escape syntax {ts 'value'} did not interpret the value as a timestamp. The same for {d 'value'} (for date) and {t 'value'} (for time). Thanks to Lukas Eder for reporting the issue. The following problem was detected after version 1.4.181 was released: The change in JDBC escape processing affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax {t 'time'}, or {ts 'timestamp'}, or {d 'date'}, then both the client and the server need to be upgraded to version 1.4.181 or later.
@changelog_1090_li
@changelog_1113_li
File system abstraction: support replacing existing files using move (currently not for Windows).
File system abstraction: support replacing existing files using move (currently not for Windows).
@changelog_1091_li
@changelog_1114_li
The statement "shutdown defrag" now compresses the database (with the MVStore). This command can greatly reduce the file size, and is relatively fast, but is not incremental.
The statement "shutdown defrag" now compresses the database (with the MVStore). This command can greatly reduce the file size, and is relatively fast, but is not incremental.
@changelog_1092_li
@changelog_1115_li
The MVStore now automatically compacts the store in the background if there is no read or write activity, which should (after some time; sometimes about one minute) reduce the file size. This is still work in progress, feedback is welcome!
The MVStore now automatically compacts the store in the background if there is no read or write activity, which should (after some time; sometimes about one minute) reduce the file size. This is still work in progress, feedback is welcome!
@changelog_1093_li
@changelog_1116_li
Change default value of PAGE_SIZE from 2048 to 4096 to more closely match most file systems block size (PageStore only; the MVStore already used 4096).
Change default value of PAGE_SIZE from 2048 to 4096 to more closely match most file systems block size (PageStore only; the MVStore already used 4096).
@changelog_1094_li
@changelog_1117_li
Auto-scale MAX_MEMORY_ROWS and CACHE_SIZE settings by the amount of available RAM. Gives a better out of box experience for people with more powerful machines.
Auto-scale MAX_MEMORY_ROWS and CACHE_SIZE settings by the amount of available RAM. Gives a better out of box experience for people with more powerful machines.
@changelog_1095_li
@changelog_1118_li
Handle tabs like 4 spaces in web console, patch by Martin Grajcar.
Handle tabs like 4 spaces in web console, patch by Martin Grajcar.
@changelog_1096_li
@changelog_1119_li
Issue 573: Add implementation for Methods "isWrapperFor()" and "unwrap()" in JdbcConnection.java, patch by BigMichi1.
Issue 573: Add implementation for Methods "isWrapperFor()" and "unwrap()" in JdbcConnection.java, patch by BigMichi1.
@changelog_1097_h2
@changelog_1120_h2
Version 1.4.180 Beta (2014-07-13)
Version 1.4.180 Beta (2014-07-13)
@changelog_1098_li
@changelog_1121_li
MVStore: the store is now auto-compacted automatically up to some point, to avoid very large file sizes. This area is still work in progress.
MVStore: the store is now auto-compacted automatically up to some point, to avoid very large file sizes. This area is still work in progress.
@changelog_1099_li
@changelog_1122_li
Sequences of temporary tables (auto-increment or identity columns) were persisted unnecessarily in the database file, and were not removed when re-opening the database.
Sequences of temporary tables (auto-increment or identity columns) were persisted unnecessarily in the database file, and were not removed when re-opening the database.
@changelog_1100_li
@changelog_1123_li
MVStore: an IndexOutOfBoundsException could sometimes occur MVMap.openVersion when concurrently accessing the store.
MVStore: an IndexOutOfBoundsException could sometimes occur MVMap.openVersion when concurrently accessing the store.
@changelog_1101_li
@changelog_1124_li
The LIRS cache now re-sizes the internal hash map if needed.
The LIRS cache now re-sizes the internal hash map if needed.
@changelog_1102_li
@changelog_1125_li
Optionally persist session history in the H2 console. (patch from Martin Grajcar)
Optionally persist session history in the H2 console. (patch from Martin Grajcar)
@changelog_1103_li
@changelog_1126_li
Add client-info property to get the number of servers currently in the cluster and which servers that are available. (patch from Nikolaj Fogh)
Add client-info property to get the number of servers currently in the cluster and which servers that are available. (patch from Nikolaj Fogh)
@changelog_1104_li
@changelog_1127_li
Fix bug in changing encrypted DB password that kept the file handle open when the wrong password was supplied. (test case from Jens Hohmuth).
Fix bug in changing encrypted DB password that kept the file handle open when the wrong password was supplied. (test case from Jens Hohmuth).
@changelog_1105_li
@changelog_1128_li
Issue 567: H2 hangs for a long time then (sometimes) recovers. Introduce a queue when doing table locking to prevent session starvation.
Issue 567: H2 hangs for a long time then (sometimes) recovers. Introduce a queue when doing table locking to prevent session starvation.
@changelog_1106_h2
@changelog_1129_h2
Version 1.4.179 Beta (2014-06-23)
Version 1.4.179 Beta (2014-06-23)
@changelog_1107_li
@changelog_1130_li
The license was changed to MPL 2.0 (from 1.0) and EPL 1.0.
The license was changed to MPL 2.0 (from 1.0) and EPL 1.0.
@changelog_1108_li
@changelog_1131_li
Issue 565: MVStore: concurrently adding LOB objects (with MULTI_THREADED option) resulted in a NullPointerException.
Issue 565: MVStore: concurrently adding LOB objects (with MULTI_THREADED option) resulted in a NullPointerException.
@changelog_1109_li
@changelog_1132_li
MVStore: reduced dependencies to other H2 classes.
MVStore: reduced dependencies to other H2 classes.
@changelog_1110_li
@changelog_1133_li
There was a way to prevent a database from being re-opened, by creating a column constraint that references a table with a higher id, for example with "check" constraints that contains queries. This is now detected, and creating the table is prohibited. In future versions of H2, most likely creating references to other tables will no longer be supported because of such problems.
There was a way to prevent a database from being re-opened, by creating a column constraint that references a table with a higher id, for example with "check" constraints that contains queries. This is now detected, and creating the table is prohibited. In future versions of H2, most likely creating references to other tables will no longer be supported because of such problems.
@changelog_1111_li
@changelog_1134_li
MVStore: descending indexes with "nulls first" did not work as expected (null was ordered last).
MVStore: descending indexes with "nulls first" did not work as expected (null was ordered last).
@changelog_1112_li
@changelog_1135_li
Large result sets now always create temporary tables instead of temporary files.
Large result sets now always create temporary tables instead of temporary files.
@changelog_1113_li
@changelog_1136_li
When using the PageStore, opening a database failed in some cases with a NullPointerException if temporary tables were used (explicitly, or implicitly when using large result sets).
When using the PageStore, opening a database failed in some cases with a NullPointerException if temporary tables were used (explicitly, or implicitly when using large result sets).
@changelog_1114_li
@changelog_1137_li
If a database file in the PageStore file format exists, this file and this mode is now used, even if the database URL does not contain "MV_STORE=FALSE". If a MVStore file exists, it is used.
If a database file in the PageStore file format exists, this file and this mode is now used, even if the database URL does not contain "MV_STORE=FALSE". If a MVStore file exists, it is used.
@changelog_1115_li
@changelog_1138_li
Databases created with version 1.3.175 and earlier that contained foreign keys in combination with multi-column indexes could not be opened in some cases. This was due to a bugfix in version 1.3.176: Referential integrity constraints sometimes used the wrong index.
Databases created with version 1.3.175 and earlier that contained foreign keys in combination with multi-column indexes could not be opened in some cases. This was due to a bugfix in version 1.3.176: Referential integrity constraints sometimes used the wrong index.
@changelog_1116_li
@changelog_1139_li
MVStore: the ObjectDataType comparison method was incorrect if one key was Serializable and the other was of a common class.
MVStore: the ObjectDataType comparison method was incorrect if one key was Serializable and the other was of a common class.
@changelog_1117_li
@changelog_1140_li
Recursive queries with many result rows (more than the setting "max_memory_rows") did not work correctly.
Recursive queries with many result rows (more than the setting "max_memory_rows") did not work correctly.
@changelog_1118_li
@changelog_1141_li
The license has changed to MPL 2.0 + EPL 1.0.
The license has changed to MPL 2.0 + EPL 1.0.
@changelog_1119_li
@changelog_1142_li
MVStore: temporary tables from result sets could survive re-opening a database, which could result in a ClassCastException.
MVStore: temporary tables from result sets could survive re-opening a database, which could result in a ClassCastException.
@changelog_1120_li
@changelog_1143_li
Issue 566: MVStore: unique indexes that were created later on did not work correctly if there were over 5000 rows in the table. Existing databases need to be re-created (at least the broken index need to be re-built).
Issue 566: MVStore: unique indexes that were created later on did not work correctly if there were over 5000 rows in the table. Existing databases need to be re-created (at least the broken index need to be re-built).
@changelog_1121_li
@changelog_1144_li
MVStore: creating secondary indexes on large tables results in missing rows in the index.
MVStore: creating secondary indexes on large tables results in missing rows in the index.
@changelog_1122_li
@changelog_1145_li
Metadata: the password of linked tables is now only visible for admin users.
Metadata: the password of linked tables is now only visible for admin users.
@changelog_1123_li
@changelog_1146_li
For Windows, database URLs of the form "jdbc:h2:/test" where considered relative and did not work unless the system property "h2.implicitRelativePath" was used.
For Windows, database URLs of the form "jdbc:h2:/test" where considered relative and did not work unless the system property "h2.implicitRelativePath" was used.
@changelog_1124_li
@changelog_1147_li
Windows: using a base directory of "C:/" and similar did not work as expected.
Windows: using a base directory of "C:/" and similar did not work as expected.
@changelog_1125_li
@changelog_1148_li
Follow JDBC specification on Procedures MetaData, use P0 as return type of procedure.
Follow JDBC specification on Procedures MetaData, use P0 as return type of procedure.
@changelog_1126_li
@changelog_1149_li
Issue 531: IDENTITY ignored for added column.
Issue 531: IDENTITY ignored for added column.
@changelog_1127_li
@changelog_1150_li
FileSystem: improve exception throwing compatibility with JDK
FileSystem: improve exception throwing compatibility with JDK
@changelog_1128_li
@changelog_1151_li
Spatial Index: adjust costs so we do not use the spatial index if the query does not contain an intersects operator.
Spatial Index: adjust costs so we do not use the spatial index if the query does not contain an intersects operator.
@changelog_1129_li
@changelog_1152_li
Fix multi-threaded deadlock when using a View that includes a TableFunction.
Fix multi-threaded deadlock when using a View that includes a TableFunction.
@changelog_1130_li
@changelog_1153_li
Fix bug in dividing very-small BigDecimal numbers.
Fix bug in dividing very-small BigDecimal numbers.
@changelog_1131_h2
@changelog_1154_h2
Version 1.4.178 Beta (2014-05-02)
Version 1.4.178 Beta (2014-05-02)
@changelog_1132_li
@changelog_1155_li
Issue 559: Make dependency on org.osgi.service.jdbc optional.
Issue 559: Make dependency on org.osgi.service.jdbc optional.
@changelog_1133_li
@changelog_1156_li
Improve error message when the user specifies an unsupported combination of database settings.
Improve error message when the user specifies an unsupported combination of database settings.
@changelog_1134_li
@changelog_1157_li
MVStore: in the multi-threaded mode, NullPointerException and other exceptions could occur.
MVStore: in the multi-threaded mode, NullPointerException and other exceptions could occur.
@changelog_1135_li
@changelog_1158_li
MVStore: some database file could not be compacted due to a bug in the bookkeeping of the fill rate. Also, database file were compacted quite slowly. This has been improved; but more changes in this area are expected.
MVStore: some database file could not be compacted due to a bug in the bookkeeping of the fill rate. Also, database file were compacted quite slowly. This has been improved; but more changes in this area are expected.
@changelog_1136_li
@changelog_1159_li
MVStore: support for volatile maps (that don't store changes).
MVStore: support for volatile maps (that don't store changes).
@changelog_1137_li
@changelog_1160_li
MVStore mode: in-memory databases now also use the MVStore.
MVStore mode: in-memory databases now also use the MVStore.
@changelog_1138_li
@changelog_1161_li
In server mode, appending ";autocommit=false" to the database URL was working, but the return value of Connection.getAutoCommit() was wrong.
In server mode, appending ";autocommit=false" to the database URL was working, but the return value of Connection.getAutoCommit() was wrong.
@changelog_1139_li
@changelog_1162_li
Issue 561: OSGi: the import package declaration of org.h2 excluded version 1.4.
Issue 561: OSGi: the import package declaration of org.h2 excluded version 1.4.
@changelog_1140_li
@changelog_1163_li
Issue 558: with the MVStore, a NullPointerException could occur when using LOBs at session commit (LobStorageMap.removeLob).
Issue 558: with the MVStore, a NullPointerException could occur when using LOBs at session commit (LobStorageMap.removeLob).
@changelog_1141_li
@changelog_1164_li
Remove the "h2.MAX_MEMORY_ROWS_DISTINCT" system property to reduce confusion. We already have the MAX_MEMORY_ROWS setting which does a very similar thing, and is better documented.
Remove the "h2.MAX_MEMORY_ROWS_DISTINCT" system property to reduce confusion. We already have the MAX_MEMORY_ROWS setting which does a very similar thing, and is better documented.
@changelog_1142_li
@changelog_1165_li
Issue 554: Web Console in an IFrame was not fully supported.
Issue 554: Web Console in an IFrame was not fully supported.
@changelog_1143_h2
@changelog_1166_h2
Version 1.4.177 Beta (2014-04-12)
Version 1.4.177 Beta (2014-04-12)
@changelog_1144_li
@changelog_1167_li
By default, the MV_STORE option is enabled, so it is using the new MVStore storage. The MVCC setting is by default set to the same values as the MV_STORE setting, so it is also enabled by default. For testing, both settings can be disabled by appending ";MV_STORE=FALSE" and/or ";MVCC=FALSE" to the database URL.
By default, the MV_STORE option is enabled, so it is using the new MVStore storage. The MVCC setting is by default set to the same values as the MV_STORE setting, so it is also enabled by default. For testing, both settings can be disabled by appending ";MV_STORE=FALSE" and/or ";MVCC=FALSE" to the database URL.
@changelog_1145_li
@changelog_1168_li
The file locking method 'serialized' is no longer supported. This mode might return in a future version, however this is not clear right now. A new implementation and new tests would be needed.
The file locking method 'serialized' is no longer supported. This mode might return in a future version, however this is not clear right now. A new implementation and new tests would be needed.
@changelog_1146_li
@changelog_1169_li
Enable the new storage format for dates (system property "h2.storeLocalTime"). For the MVStore mode, this is always enabled, but with version 1.4 this is even enabled in the PageStore mode.
Enable the new storage format for dates (system property "h2.storeLocalTime"). For the MVStore mode, this is always enabled, but with version 1.4 this is even enabled in the PageStore mode.
@changelog_1147_li
@changelog_1170_li
Implicit relative paths are disabled (system property "h2.implicitRelativePath"), so that the database URL jdbc:h2:test now needs to be written as jdbc:h2:./test.
Implicit relative paths are disabled (system property "h2.implicitRelativePath"), so that the database URL jdbc:h2:test now needs to be written as jdbc:h2:./test.
@changelog_1148_li
@changelog_1171_li
"select ... fetch first 1 row only" is supported with the regular mode. This was disabled so far because "fetch" and "offset" are now keywords. See also Mode.supportOffsetFetch.
"select ... fetch first 1 row only" is supported with the regular mode. This was disabled so far because "fetch" and "offset" are now keywords. See also Mode.supportOffsetFetch.
@changelog_1149_li
@changelog_1172_li
Byte arrays are now sorted in unsigned mode (x'99' is larger than x'09'). (System property "h2.sortBinaryUnsigned", Mode.binaryUnsigned, setting "binary_collation").
Byte arrays are now sorted in unsigned mode (x'99' is larger than x'09'). (System property "h2.sortBinaryUnsigned", Mode.binaryUnsigned, setting "binary_collation").
@changelog_1150_li
@changelog_1173_li
Csv.getInstance will be removed in future versions of 1.4. Use the public constructor instead.
Csv.getInstance will be removed in future versions of 1.4. Use the public constructor instead.
@changelog_1151_li
@changelog_1174_li
Remove support for the limited old-style outer join syntax using "(+)". Use "outer join" instead. System property "h2.oldStyleOuterJoin".
Remove support for the limited old-style outer join syntax using "(+)". Use "outer join" instead. System property "h2.oldStyleOuterJoin".
@changelog_1152_li
@changelog_1175_li
Support the data type "DATETIME2" as an alias for "DATETIME", for MS SQL Server compatibility.
Support the data type "DATETIME2" as an alias for "DATETIME", for MS SQL Server compatibility.
@changelog_1153_li
@changelog_1176_li
Add Oracle-compatible TRANSLATE function, patch by Eric Chatellier.
Add Oracle-compatible TRANSLATE function, patch by Eric Chatellier.
@changelog_1154_h2
@changelog_1177_h2
Version 1.3.176 (2014-04-05)
Version 1.3.176 (2014-04-05)
@changelog_1155_li
@changelog_1178_li
The file locking method 'serialized' is no longer documented, as it will not be available in version 1.4.
The file locking method 'serialized' is no longer documented, as it will not be available in version 1.4.
@changelog_1156_li
@changelog_1179_li
The static method Csv.getInstance() was removed. Use the public constructor instead.
The static method Csv.getInstance() was removed. Use the public constructor instead.
@changelog_1157_li
@changelog_1180_li
The default user name for the Script, RunScript, Shell, and CreateCluster tools are no longer "sa" but an empty string.
The default user name for the Script, RunScript, Shell, and CreateCluster tools are no longer "sa" but an empty string.
@changelog_1158_li
@changelog_1181_li
The stack trace of the exception "The object is already closed" is no longer logged by default.
The stack trace of the exception "The object is already closed" is no longer logged by default.
@changelog_1159_li
@changelog_1182_li
If a value of a result set was itself a result set, the result could only be read once.
If a value of a result set was itself a result set, the result could only be read once.
@changelog_1160_li
@changelog_1183_li
Column constraints are also visible in views (patch from Nicolas Fortin for H2GIS).
Column constraints are also visible in views (patch from Nicolas Fortin for H2GIS).
@changelog_1161_li
@changelog_1184_li
Granting a additional right to a role that already had a right for that table was not working.
Granting a additional right to a role that already had a right for that table was not working.
@changelog_1162_li
@changelog_1185_li
Spatial index: a few bugs have been fixed (using spatial constraints in views, transferring geometry objects over TCP/IP, the returned geometry object is copied when needed).
Spatial index: a few bugs have been fixed (using spatial constraints in views, transferring geometry objects over TCP/IP, the returned geometry object is copied when needed).
@changelog_1163_li
@changelog_1186_li
Issue 551: the datatype documentation was incorrect (found by Bernd Eckenfels).
Issue 551: the datatype documentation was incorrect (found by Bernd Eckenfels).
@changelog_1164_li
@changelog_1187_li
Issue 368: ON DUPLICATE KEY UPDATE did not work for multi-row inserts. Test case from Angus Macdonald.
Issue 368: ON DUPLICATE KEY UPDATE did not work for multi-row inserts. Test case from Angus Macdonald.
@changelog_1165_li
@changelog_1188_li
OSGi: the package javax.tools is now imported (as an optional).
OSGi: the package javax.tools is now imported (as an optional).
@changelog_1166_li
@changelog_1189_li
H2 Console: auto-complete is now disabled by default, but there is a hot-key (Ctrl+Space).
H2 Console: auto-complete is now disabled by default, but there is a hot-key (Ctrl+Space).
@changelog_1167_li
@changelog_1190_li
H2 Console: auto-complete did not work with multi-line statements.
H2 Console: auto-complete did not work with multi-line statements.
@changelog_1168_li
@changelog_1191_li
CLOB and BLOB data was not immediately removed after a rollback.
CLOB and BLOB data was not immediately removed after a rollback.
@changelog_1169_li
@changelog_1192_li
There is a new Aggregate API that supports the internal H2 data types (GEOMETRY for example). Thanks a lot to Nicolas Fortin for the patch!
There is a new Aggregate API that supports the internal H2 data types (GEOMETRY for example). Thanks a lot to Nicolas Fortin for the patch!
@changelog_1170_li
@changelog_1193_li
Referential integrity constraints sometimes used the wrong index, such that updating a row in the referenced table incorrectly failed with a constraint violation.
Referential integrity constraints sometimes used the wrong index, such that updating a row in the referenced table incorrectly failed with a constraint violation.
@changelog_1171_li
@changelog_1194_li
The Polish translation was completed and corrected by Wojtek Jurczyk. Thanks a lot!
The Polish translation was completed and corrected by Wojtek Jurczyk. Thanks a lot!
@changelog_1172_li
@changelog_1195_li
Issue 545: Unnecessary duplicate code was removed.
Issue 545: Unnecessary duplicate code was removed.
@changelog_1173_li
@changelog_1196_li
The profiler tool can now process files with full thread dumps.
The profiler tool can now process files with full thread dumps.
@changelog_1174_li
@changelog_1197_li
MVStore: the file format was changed slightly.
MVStore: the file format was changed slightly.
@changelog_1175_li
@changelog_1198_li
MVStore mode: the CLOB and BLOB storage was re-implemented and is now much faster than with the PageStore (which is still the default storage).
MVStore mode: the CLOB and BLOB storage was re-implemented and is now much faster than with the PageStore (which is still the default storage).
@changelog_1176_li
@changelog_1199_li
MVStore mode: creating indexes is now much faster (in many cases faster than with the default PageStore).
MVStore mode: creating indexes is now much faster (in many cases faster than with the default PageStore).
@changelog_1177_li
@changelog_1200_li
Various bugs in the MVStore storage and have been fixed, including a bug in the R-tree implementation. The database could get corrupt if there were transient IO exceptions while storing.
Various bugs in the MVStore storage and have been fixed, including a bug in the R-tree implementation. The database could get corrupt if there were transient IO exceptions while storing.
@changelog_1178_li
@changelog_1201_li
The method org.h2.expression.Function.getCost could throw a NullPointException.
The method org.h2.expression.Function.getCost could throw a NullPointException.
@changelog_1179_li
@changelog_1202_li
Storing LOBs in separate files (outside of the main database file) is no longer supported for new databases.
Storing LOBs in separate files (outside of the main database file) is no longer supported for new databases.
@changelog_1180_li
@changelog_1203_li
Lucene 2 is no longer supported.
Lucene 2 is no longer supported.
@changelog_1181_li
@changelog_1204_li
Fix bug in calculating default MIN and MAX values for SEQUENCE.
Fix bug in calculating default MIN and MAX values for SEQUENCE.
@changelog_1182_li
@changelog_1205_li
Fix bug in performing IN queries with multiple values when IGNORECASE=TRUE
Fix bug in performing IN queries with multiple values when IGNORECASE=TRUE
@changelog_1183_li
@changelog_1206_li
Add entry-point to org.h2.tools.Shell so it can be called from inside an application. patch by Thomas Gillet.
Add entry-point to org.h2.tools.Shell so it can be called from inside an application. patch by Thomas Gillet.
@changelog_1184_li
@changelog_1207_li
Fix bug that prevented the PgServer from being stopped and started multiple times.
Fix bug that prevented the PgServer from being stopped and started multiple times.
@changelog_1185_li
@changelog_1208_li
Support some more DDL syntax for MySQL, patch from Peter Jentsch.
Support some more DDL syntax for MySQL, patch from Peter Jentsch.
@changelog_1186_li
@changelog_1209_li
Issue 548: TO_CHAR does not format MM and DD correctly when the month or day of the month is 1 digit, patch from "the.tucc"
Issue 548: TO_CHAR does not format MM and DD correctly when the month or day of the month is 1 digit, patch from "the.tucc"
@changelog_1187_li
@changelog_1210_li
Fix bug in varargs support in ALIAS's, patch from Nicolas Fortin
Fix bug in varargs support in ALIAS's, patch from Nicolas Fortin
@cheatSheet_1000_h1
@cheatSheet_1000_h1
...
@@ -10741,16 +10810,19 @@ Issue 390: RUNSCRIPT FROM '...' CONTINUE_ON_ERROR
...
@@ -10741,16 +10810,19 @@ Issue 390: RUNSCRIPT FROM '...' CONTINUE_ON_ERROR
@roadmap_1509_li
@roadmap_1509_li
Use Java 6 exceptions: SQLDataException, SQLSyntaxErrorException, SQLTimeoutException,..
Use Java 6 exceptions: SQLDataException, SQLSyntaxErrorException, SQLTimeoutException,..
@roadmap_1510_h2
@roadmap_1510_li
Support index-only when doing selects (i.e. without needing to load the actual table data)
@roadmap_1511_h2
Not Planned
Not Planned
@roadmap_1511_li
@roadmap_1512_li
HSQLDB (did) support this: select id i from test where i<0 (other databases don't). Supporting it may break compatibility.
HSQLDB (did) support this: select id i from test where i<0 (other databases don't). Supporting it may break compatibility.
@roadmap_1512_li
@roadmap_1513_li
String.intern (so that Strings can be compared with ==) will not be used because some VMs have problems when used extensively.
String.intern (so that Strings can be compared with ==) will not be used because some VMs have problems when used extensively.
@roadmap_1513_li
@roadmap_1514_li
In prepared statements, identifier names (table names and so on) can not be parameterized. Adding such a feature would complicate the source code without providing reasonable speedup, and would slow down regular prepared statements.
In prepared statements, identifier names (table names and so on) can not be parameterized. Adding such a feature would complicate the source code without providing reasonable speedup, and would slow down regular prepared statements.
# To use the MVCC feature, append <code>;MVCC=TRUE</code> to the database URL:
# To use the MVCC feature, append <code>;MVCC=TRUE</code> to the database URL:
@advanced_1094_p
@advanced_1094_p
# MVCC is disabled by default. The MVCC feature is not fully tested yet. The limitations of the MVCC mode are: it can not be used at the same time as <code>MULTI_THREADED=TRUE</code>; the complete undo log (the list of uncommitted changes) must fit in memory when using multi-version concurrency. The setting <code>MAX_MEMORY_UNDO</code> has no effect. It is not possible to enable or disable this setting while the database is already open. The setting must be specified in the first connection (the one that opens the database).
# The setting must be specified in the first connection (the one that opens the database). It is not possible to enable or disable this setting while the database is already open.
@advanced_1095_p
@advanced_1095_p
# If MVCC is enabled, changing the lock mode (<code>LOCK_MODE</code>) has no effect.
# If MVCC is enabled, changing the lock mode (<code>LOCK_MODE</code>) has no effect.
@advanced_1096_h2
@advanced_1096_div
クラスタリング / 高�?�用性
# The MVCC mode is enabled by default in version 1.4.x, with the default MVStore storage engine. MVCC is disabled by default when using the PageStore storage engine (which is the default in version 1.3.x). The following applies when using the PageStore storage engine: The MVCC feature is not fully tested yet. The limitations of the MVCC mode are: with the PageStore storage engine, it can not be used at the same time as <code>MULTI_THREADED=TRUE</code>; the complete undo log (the list of uncommitted changes) must fit in memory when using multi-version concurrency. The setting <code>MAX_MEMORY_UNDO</code> has no effect. Clustering / High Availability
@advanced_1097_p
@advanced_1097_p
# This database supports a simple clustering / high availability mechanism. The architecture is: two database servers run on two different computers, and on both computers is a copy of the same database. If both servers run, each database operation is executed on both computers. If one server fails (power, hardware or network failure), the other server can still continue to work. From this point on, the operations will be executed only on one server until the other server is back up.
# This database supports a simple clustering / high availability mechanism. The architecture is: two database servers run on two different computers, and on both computers is a copy of the same database. If both servers run, each database operation is executed on both computers. If one server fails (power, hardware or network failure), the other server can still continue to work. From this point on, the operations will be executed only on one server until the other server is back up.
...
@@ -1889,561 +1889,630 @@ Centralリ�?ジトリ�?�利用
...
@@ -1889,561 +1889,630 @@ Centralリ�?ジトリ�?�利用
#Next Version (unreleased)
#Next Version (unreleased)
@changelog_1002_li
@changelog_1002_li
#-
#MVStore: concurrent changes to the same row could result in the exception "The transaction log might be corrupt for key ...". This could only be reproduced with 3 or more threads.
@changelog_1003_h2
@changelog_1003_li
#Version 1.4.186 Beta (2015-03-02)
#Results with CLOB or BLOB data are no longer reused.
@changelog_1004_li
@changelog_1004_li
#The Servlet API 3.0.1 is now used, instead of 2.4.
#References to BLOB and CLOB objects now have a timeout. The configuration setting is LOB_TIMEOUT (default 5 minutes). This should avoid growing the database file if there are many queries that return BLOB or CLOB objects, and the database is not closed for a longer time.
@changelog_1005_li
@changelog_1005_li
#MVStore: old chunks no longer removed in append-only mode.
#MVStore: when committing a session that removed LOB values, changes were flushed unnecessarily.
@changelog_1006_li
@changelog_1006_li
#MVStore: the cache for page references could grow far too big, resulting in out of memory in some cases.
#Issue 610: possible integer overflow in WriteBuffer.grow().
@changelog_1007_li
@changelog_1007_li
#MVStore: orphaned lob objects were not correctly removed in some cases, making the database grow unnecessarily.
#Issue 609: the spatial index did not support NULL (ClassCastException).
@changelog_1008_li
@changelog_1008_li
#MVStore: the maximum cache size was artificially limited to 2 GB (due to an integer overflow).
#MVStore: in some cases, CLOB/BLOB data blocks were removed incorrectly when opening a database.
@changelog_1009_li
@changelog_1009_li
#MVStore / TransactionStore: concurrent updates could result in a "Too many open transactions" exception.
#MVStore: updates that affected many rows were were slow in some cases if there was a secondary index.
@changelog_1010_li
@changelog_1010_li
#StringUtils.toUpperEnglish now has a small cache. This should speed up reading from a ResultSet when using the column name.
#Using "runscript" with autocommit disabled could result in a lock timeout on the internal table "SYS".
@changelog_1011_li
@changelog_1011_li
#MVStore: up to 65535 open transactions are now supported. Previously, the limit was at most 65535 transactions between the oldest open and the newest open transaction (which was quite a strange limit).
#Issue 603: there was a memory leak when using H2 in a web application. Apache Tomcat logged an error message: "The web application ... created a ThreadLocal with key of type [org.h2.util.DateTimeUtils$1]".
@changelog_1012_li
@changelog_1012_li
#The default limit for in-place LOB objects was changed from 128 to 256 bytes. This is because each read creates a reference to a LOB, and maintaining the references is a big overhead. With the higher limit, less references are needed.
#When using the MVStore, running a SQL script generate by the Recover tool from a PageStore file failed with a strange error message (NullPointerException), now a clear error message is shown.
@changelog_1013_li
@changelog_1013_li
#Tables without columns didn't work. (The use case for such tables is testing.)
#Issue 605: with version 1.4.186, opening a database could result in an endless loop in LobStorageMap.init.
@changelog_1014_li
@changelog_1014_li
#The LIRS cache now resizes the table automatically in all cases and no longer needs the averageMemory configuration.
#Queries that use the same table alias multiple times now work. Before, the select expression list was expanded incorrectly. Example: "select * from a as x, b as x".
@changelog_1015_li
@changelog_1015_li
#Creating a linked table from an MVStore database to a non-MVStore database created a second (non-MVStore) database file.
#The MySQL compatibility feature "insert ... on duplicate key update" did not work with a non-default schema.
@changelog_1016_li
@changelog_1016_li
#In version 1.4.184, a bug was introduced that broke queries that have both joins and wildcards, for example: select * from dual join(select x from dual) on 1=1
#Issue 599: the condition "in(x, y)" could not be used in the select list when using "group by".
@changelog_1017_li
@changelog_1017_li
#Issue 598: parser fails on timestamp "24:00:00.1234" - prevent the creation of out-of-range time values.
#The LIRS cache could grow larger than the allocated memory.
@changelog_1018_li
@changelog_1018_li
#Allow declaring triggers as source code (like functions). Patch by Sylvain Cuaz.
#A new file system implementation that re-opens the file if it was closed due to the application calling Thread.interrupt(). File name prefix "retry:". Please note it is strongly recommended to avoid calling Thread.interrupt; this is a problem for various libraries, including Apache Lucene.
@changelog_1019_li
@changelog_1019_li
#Make the planner use indexes for sorting when doing a GROUP BY where all of the GROUP BY columns are not mentioned in the select. Patch by Frederico (zepfred).
#MVStore: use RandomAccessFile file system if the file name starts with "file:".
@changelog_1020_li
@changelog_1020_li
#PostgreSQL compatibility: generate_series (as an alias for system_range). Patch by litailang.
#Allow DATEADD to take a long value for count when manipulating milliseconds.
@changelog_1021_li
@changelog_1021_li
#When using MV_STORE=TRUE and the SET CACHE_SIZE setting, the cache size was incorrectly set, so that it was effectively 1024 times smaller than it should be.
@changelog_1022_li
#Concurrent CREATE TABLE... IF NOT EXISTS in the presence of MULTI_THREAD=TRUE could throw an exception.
@changelog_1023_li
#Fix bug in MVStore when creating lots of temporary tables, where we could run out of transaction IDs.
@changelog_1024_li
#Add support for PostgreSQL STRING_AGG function. Patch by Fred Aquiles.
@changelog_1025_li
#Fix bug in "jdbc:h2:nioMemFS" isRoot() function
@changelog_1026_h2
#Version 1.4.186 Beta (2015-03-02)
@changelog_1027_li
#The Servlet API 3.0.1 is now used, instead of 2.4.
@changelog_1028_li
#MVStore: old chunks no longer removed in append-only mode.
@changelog_1029_li
#MVStore: the cache for page references could grow far too big, resulting in out of memory in some cases.
@changelog_1030_li
#MVStore: orphaned lob objects were not correctly removed in some cases, making the database grow unnecessarily.
@changelog_1031_li
#MVStore: the maximum cache size was artificially limited to 2 GB (due to an integer overflow).
@changelog_1032_li
#MVStore / TransactionStore: concurrent updates could result in a "Too many open transactions" exception.
@changelog_1033_li
#StringUtils.toUpperEnglish now has a small cache. This should speed up reading from a ResultSet when using the column name.
@changelog_1034_li
#MVStore: up to 65535 open transactions are now supported. Previously, the limit was at most 65535 transactions between the oldest open and the newest open transaction (which was quite a strange limit).
@changelog_1035_li
#The default limit for in-place LOB objects was changed from 128 to 256 bytes. This is because each read creates a reference to a LOB, and maintaining the references is a big overhead. With the higher limit, less references are needed.
@changelog_1036_li
#Tables without columns didn't work. (The use case for such tables is testing.)
@changelog_1037_li
#The LIRS cache now resizes the table automatically in all cases and no longer needs the averageMemory configuration.
@changelog_1038_li
#Creating a linked table from an MVStore database to a non-MVStore database created a second (non-MVStore) database file.
@changelog_1039_li
#In version 1.4.184, a bug was introduced that broke queries that have both joins and wildcards, for example: select * from dual join(select x from dual) on 1=1
@changelog_1040_li
#Issue 598: parser fails on timestamp "24:00:00.1234" - prevent the creation of out-of-range time values.
@changelog_1041_li
#Allow declaring triggers as source code (like functions). Patch by Sylvain Cuaz.
@changelog_1042_li
#Make the planner use indexes for sorting when doing a GROUP BY where all of the GROUP BY columns are not mentioned in the select. Patch by Frederico (zepfred).
@changelog_1043_li
#PostgreSQL compatibility: generate_series (as an alias for system_range). Patch by litailang.
@changelog_1044_li
#Fix missing "column" type in right-hand parameter in ConditionIn. Patch by Arnaud Thimel.
#Fix missing "column" type in right-hand parameter in ConditionIn. Patch by Arnaud Thimel.
@changelog_1022_h2
@changelog_1045_h2
#Version 1.4.185 Beta (2015-01-16)
#Version 1.4.185 Beta (2015-01-16)
@changelog_1023_li
@changelog_1046_li
#In version 1.4.184, "group by" ignored the table name, and could pick a select column by mistake. Example: select 0 as x from system_range(1, 2) d group by d.x;
#In version 1.4.184, "group by" ignored the table name, and could pick a select column by mistake. Example: select 0 as x from system_range(1, 2) d group by d.x;
@changelog_1024_li
@changelog_1047_li
#New connection setting "REUSE_SPACE" (default: true). If disabled, all changes are appended to the database file, and existing content is never overwritten. This allows to rollback to a previous state of the database by truncating the database file.
#New connection setting "REUSE_SPACE" (default: true). If disabled, all changes are appended to the database file, and existing content is never overwritten. This allows to rollback to a previous state of the database by truncating the database file.
@changelog_1025_li
@changelog_1048_li
#Issue 587: MVStore: concurrent compaction and store operations could result in an IllegalStateException.
#Issue 587: MVStore: concurrent compaction and store operations could result in an IllegalStateException.
@changelog_1026_li
@changelog_1049_li
#Issue 594: Profiler.copyInThread does not work properly.
#Issue 594: Profiler.copyInThread does not work properly.
@changelog_1027_li
@changelog_1050_li
#Script tool: Now, SCRIPT ... TO is always used (for higher speed and lower disk space usage).
#Script tool: Now, SCRIPT ... TO is always used (for higher speed and lower disk space usage).
@changelog_1028_li
@changelog_1051_li
#Script tool: Fix parsing of BLOCKSIZE parameter, original patch by Ken Jorissen.
#Script tool: Fix parsing of BLOCKSIZE parameter, original patch by Ken Jorissen.
@changelog_1029_li
@changelog_1052_li
#Fix bug in PageStore#commit method - when the ignoreBigLog flag was set, the logic that cleared the flag could never be reached, resulting in performance degradation. Reported by Alexander Nesterov.
#Fix bug in PageStore#commit method - when the ignoreBigLog flag was set, the logic that cleared the flag could never be reached, resulting in performance degradation. Reported by Alexander Nesterov.
@changelog_1030_li
@changelog_1053_li
#Issue 552: Implement BIT_AND and BIT_OR aggregate functions.
#Issue 552: Implement BIT_AND and BIT_OR aggregate functions.
@changelog_1031_h2
@changelog_1054_h2
#Version 1.4.184 Beta (2014-12-19)
#Version 1.4.184 Beta (2014-12-19)
@changelog_1032_li
@changelog_1055_li
#In version 1.3.183, indexes were not used if the table contains columns with a default value generated by a sequence. This includes tables with identity and auto-increment columns. This bug was introduced by supporting "rownum" in views and derived tables.
#In version 1.3.183, indexes were not used if the table contains columns with a default value generated by a sequence. This includes tables with identity and auto-increment columns. This bug was introduced by supporting "rownum" in views and derived tables.
@changelog_1033_li
@changelog_1056_li
#MVStore: imported BLOB and CLOB data sometimes disappeared. This was caused by a bug in the ObjectDataType comparison.
#MVStore: imported BLOB and CLOB data sometimes disappeared. This was caused by a bug in the ObjectDataType comparison.
@changelog_1034_li
@changelog_1057_li
#Reading from a StreamStore now throws an IOException if the underlying data doesn't exist.
#Reading from a StreamStore now throws an IOException if the underlying data doesn't exist.
@changelog_1035_li
@changelog_1058_li
#MVStore: if there is an exception while saving, the store is now in all cases immediately closed.
#MVStore: if there is an exception while saving, the store is now in all cases immediately closed.
@changelog_1036_li
@changelog_1059_li
#MVStore: the dump tool could go into an endless loop for some files.
#MVStore: the dump tool could go into an endless loop for some files.
@changelog_1037_li
@changelog_1060_li
#MVStore: recovery for a database with many CLOB or BLOB entries is now much faster.
#MVStore: recovery for a database with many CLOB or BLOB entries is now much faster.
@changelog_1038_li
@changelog_1061_li
#Group by with a quoted select column name alias didn't work. Example: select 1 "a" from dual group by "a"
#Group by with a quoted select column name alias didn't work. Example: select 1 "a" from dual group by "a"
@changelog_1039_li
@changelog_1062_li
#Auto-server mode: the host name is now stored in the .lock.db file.
#Auto-server mode: the host name is now stored in the .lock.db file.
@changelog_1040_h2
@changelog_1063_h2
#Version 1.4.183 Beta (2014-12-13)
#Version 1.4.183 Beta (2014-12-13)
@changelog_1041_li
@changelog_1064_li
#MVStore: the default auto-commit buffer size is now about twice as big. This should reduce the database file size after inserting a lot of data.
#MVStore: the default auto-commit buffer size is now about twice as big. This should reduce the database file size after inserting a lot of data.
@changelog_1042_li
@changelog_1065_li
#The built-in functions "power" and "radians" now always return a double.
#The built-in functions "power" and "radians" now always return a double.
@changelog_1043_li
@changelog_1066_li
#Using "row_number" or "rownum" in views or derived tables had unexpected results if the outer query contained constraints for the given view. Example: select b.nr, b.id from (select row_number() over() as nr, a.id as id from (select id from test order by name) as a) as b where b.id = 1
#Using "row_number" or "rownum" in views or derived tables had unexpected results if the outer query contained constraints for the given view. Example: select b.nr, b.id from (select row_number() over() as nr, a.id as id from (select id from test order by name) as a) as b where b.id = 1
@changelog_1044_li
@changelog_1067_li
#MVStore: the Recover tool can now deal with more types of corruption in the file.
#MVStore: the Recover tool can now deal with more types of corruption in the file.
@changelog_1045_li
@changelog_1068_li
#MVStore: the TransactionStore now first needs to be initialized before it can be used.
#MVStore: the TransactionStore now first needs to be initialized before it can be used.
@changelog_1046_li
@changelog_1069_li
#Views and derived tables with equality and range conditions on the same columns did not work properly. example: select x from (select x from (select 1 as x) where x > 0 and x < 2) where x = 1
#Views and derived tables with equality and range conditions on the same columns did not work properly. example: select x from (select x from (select 1 as x) where x > 0 and x < 2) where x = 1
@changelog_1047_li
@changelog_1070_li
#The database URL setting PAGE_SIZE setting is now also used for the MVStore.
#The database URL setting PAGE_SIZE setting is now also used for the MVStore.
@changelog_1048_li
@changelog_1071_li
#MVStore: the default page split size for persistent stores is now 4096 (it was 16 KB so far). This should reduce the database file size for most situations (in some cases, less than half the size of the previous version).
#MVStore: the default page split size for persistent stores is now 4096 (it was 16 KB so far). This should reduce the database file size for most situations (in some cases, less than half the size of the previous version).
@changelog_1049_li
@changelog_1072_li
#With query literals disabled, auto-analyze of a table with CLOB or BLOB did not work.
#With query literals disabled, auto-analyze of a table with CLOB or BLOB did not work.
@changelog_1050_li
@changelog_1073_li
#MVStore: use a mark and sweep GC algorithm instead of reference counting, to ensure used chunks are never overwrite, even if the reference counting algorithm does not work properly.
#MVStore: use a mark and sweep GC algorithm instead of reference counting, to ensure used chunks are never overwrite, even if the reference counting algorithm does not work properly.
@changelog_1051_li
@changelog_1074_li
#In the multi-threaded mode, updating the column selectivity ("analyze") in the background sometimes did not work.
#In the multi-threaded mode, updating the column selectivity ("analyze") in the background sometimes did not work.
@changelog_1052_li
@changelog_1075_li
#In the multi-threaded mode, database metadata operations did sometimes not work if the schema was changed at the same time (for example, if tables were dropped).
#In the multi-threaded mode, database metadata operations did sometimes not work if the schema was changed at the same time (for example, if tables were dropped).
@changelog_1053_li
@changelog_1076_li
#Some CLOB and BLOB values could no longer be read when the original row was removed (even when using the MVCC mode).
#Some CLOB and BLOB values could no longer be read when the original row was removed (even when using the MVCC mode).
@changelog_1054_li
@changelog_1077_li
#The MVStoreTool could throw an IllegalArgumentException.
#The MVStoreTool could throw an IllegalArgumentException.
@changelog_1055_li
@changelog_1078_li
#Improved performance for some date / time / timestamp conversion operations. Thanks to Sergey Evdokimov for reporting the problem.
#Improved performance for some date / time / timestamp conversion operations. Thanks to Sergey Evdokimov for reporting the problem.
@changelog_1056_li
@changelog_1079_li
#H2 Console: the built-in web server did not work properly if an unknown file was requested.
#H2 Console: the built-in web server did not work properly if an unknown file was requested.
@changelog_1057_li
@changelog_1080_li
#MVStore: the jar file is renamed to "h2-mvstore-*.jar" and is deployed to Maven separately.
#MVStore: the jar file is renamed to "h2-mvstore-*.jar" and is deployed to Maven separately.
@changelog_1058_li
@changelog_1081_li
#MVStore: support for concurrent reads and writes is now enabled by default.
#MVStore: support for concurrent reads and writes is now enabled by default.
@changelog_1059_li
@changelog_1082_li
#Server mode: the transfer buffer size has been changed from 16 KB to 64 KB, after it was found that this improves performance on Linux quite a lot.
#Server mode: the transfer buffer size has been changed from 16 KB to 64 KB, after it was found that this improves performance on Linux quite a lot.
@changelog_1060_li
@changelog_1083_li
#H2 Console and server mode: SSL is now disabled and TLS is used to protect against the Poodle SSLv3 vulnerability. The system property to disable secure anonymous connections is now "h2.enableAnonymousTLS". The default certificate is still self-signed, so you need to manually install another one if you want to avoid man in the middle attacks.
#H2 Console and server mode: SSL is now disabled and TLS is used to protect against the Poodle SSLv3 vulnerability. The system property to disable secure anonymous connections is now "h2.enableAnonymousTLS". The default certificate is still self-signed, so you need to manually install another one if you want to avoid man in the middle attacks.
@changelog_1061_li
@changelog_1084_li
#MVStore: the R-tree did not correctly measure the memory usage.
#MVStore: the R-tree did not correctly measure the memory usage.
@changelog_1062_li
@changelog_1085_li
#MVStore: compacting a store with an R-tree did not always work.
#MVStore: compacting a store with an R-tree did not always work.
@changelog_1063_li
@changelog_1086_li
#Issue 581: When running in LOCK_MODE=0, JdbcDatabaseMetaData#supportsTransactionIsolationLevel(TRANSACTION_READ_UNCOMMITTED) should return false
#Issue 581: When running in LOCK_MODE=0, JdbcDatabaseMetaData#supportsTransactionIsolationLevel(TRANSACTION_READ_UNCOMMITTED) should return false
@changelog_1064_li
@changelog_1087_li
#Fix bug which could generate deadlocks when multiple connections accessed the same table.
#Fix bug which could generate deadlocks when multiple connections accessed the same table.
@changelog_1065_li
@changelog_1088_li
#Some places in the code were not respecting the value set in the "SET MAX_MEMORY_ROWS x" command
#Some places in the code were not respecting the value set in the "SET MAX_MEMORY_ROWS x" command
@changelog_1066_li
@changelog_1089_li
#Fix bug which could generate a NegativeArraySizeException when performing large (>40M) row union operations
#Fix bug which could generate a NegativeArraySizeException when performing large (>40M) row union operations
@changelog_1067_li
@changelog_1090_li
#Fix "USE schema" command for MySQL compatibility, patch by mfulton
#Fix "USE schema" command for MySQL compatibility, patch by mfulton
@changelog_1068_li
@changelog_1091_li
#Parse and ignore the ROW_FORMAT=DYNAMIC MySQL syntax, patch by mfulton
#Parse and ignore the ROW_FORMAT=DYNAMIC MySQL syntax, patch by mfulton
@changelog_1069_h2
@changelog_1092_h2
#Version 1.4.182 Beta (2014-10-17)
#Version 1.4.182 Beta (2014-10-17)
@changelog_1070_li
@changelog_1093_li
#MVStore: improved error messages and logging; improved behavior if there is an error when serializing objects.
#MVStore: improved error messages and logging; improved behavior if there is an error when serializing objects.
@changelog_1071_li
@changelog_1094_li
#OSGi: the MVStore packages are now exported.
#OSGi: the MVStore packages are now exported.
@changelog_1072_li
@changelog_1095_li
#With the MVStore option, when using multiple threads that concurrently create indexes or tables, it was relatively easy to get a lock timeout on the "SYS" table.
#With the MVStore option, when using multiple threads that concurrently create indexes or tables, it was relatively easy to get a lock timeout on the "SYS" table.
@changelog_1073_li
@changelog_1096_li
#When using the multi-threaded option, the exception "Unexpected code path" could be thrown, specially if the option "analyze_auto" was set to a low value.
#When using the multi-threaded option, the exception "Unexpected code path" could be thrown, specially if the option "analyze_auto" was set to a low value.
@changelog_1074_li
@changelog_1097_li
#In the server mode, when reading from a CLOB or BLOB, if the connection was closed, a NullPointerException could be thrown instead of an exception saying the connection is closed.
#In the server mode, when reading from a CLOB or BLOB, if the connection was closed, a NullPointerException could be thrown instead of an exception saying the connection is closed.
@changelog_1075_li
@changelog_1098_li
#DatabaseMetaData.getProcedures and getProcedureColumns could throw an exception if a user defined class is not available.
#DatabaseMetaData.getProcedures and getProcedureColumns could throw an exception if a user defined class is not available.
@changelog_1076_li
@changelog_1099_li
#Issue 584: the error message for a wrong sequence definition was wrong.
#Issue 584: the error message for a wrong sequence definition was wrong.
@changelog_1077_li
@changelog_1100_li
#CSV tool: the rowSeparator option is no longer supported, as the same can be achieved with the lineSeparator.
#CSV tool: the rowSeparator option is no longer supported, as the same can be achieved with the lineSeparator.
@changelog_1078_li
@changelog_1101_li
#Descending indexes on MVStore tables did not work properly.
#Descending indexes on MVStore tables did not work properly.
@changelog_1079_li
@changelog_1102_li
#Issue 579: Conditions on the "_rowid_" pseudo-column didn't use an index when using the MVStore.
#Issue 579: Conditions on the "_rowid_" pseudo-column didn't use an index when using the MVStore.
@changelog_1080_li
@changelog_1103_li
#Fixed documentation that "offset" and "fetch" are also keywords since version 1.4.x.
#Fixed documentation that "offset" and "fetch" are also keywords since version 1.4.x.
@changelog_1081_li
@changelog_1104_li
#The Long.MIN_VALUE could not be parsed for auto-increment (identity) columns.
#The Long.MIN_VALUE could not be parsed for auto-increment (identity) columns.
@changelog_1082_li
@changelog_1105_li
#Issue 573: Add implementation for Methods "isWrapperFor()" and "unwrap()" in other JDBC classes.
#Issue 573: Add implementation for Methods "isWrapperFor()" and "unwrap()" in other JDBC classes.
@changelog_1083_li
@changelog_1106_li
#Issue 572: MySQL compatibility for "order by" in update statements.
#Issue 572: MySQL compatibility for "order by" in update statements.
@changelog_1084_li
@changelog_1107_li
#The change in JDBC escape processing in version 1.4.181 affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax "{t 'time}", or "{ts 'timestamp'}", or "{d 'data'}", then both the client and the server need to be upgraded to version 1.4.181 or later.
#The change in JDBC escape processing in version 1.4.181 affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax "{t 'time}", or "{ts 'timestamp'}", or "{d 'data'}", then both the client and the server need to be upgraded to version 1.4.181 or later.
@changelog_1085_h2
@changelog_1108_h2
#Version 1.4.181 Beta (2014-08-06)
#Version 1.4.181 Beta (2014-08-06)
@changelog_1086_li
@changelog_1109_li
#Improved MySQL compatibility by supporting "use schema". Thanks a lot to Karl Pietrzak for the patch!
#Improved MySQL compatibility by supporting "use schema". Thanks a lot to Karl Pietrzak for the patch!
@changelog_1087_li
@changelog_1110_li
#Writing to the trace file is now faster, specially with the debug level.
#Writing to the trace file is now faster, specially with the debug level.
@changelog_1088_li
@changelog_1111_li
#The database option "defrag_always=true" did not work with the MVStore.
#The database option "defrag_always=true" did not work with the MVStore.
@changelog_1089_li
@changelog_1112_li
#The JDBC escape syntax {ts 'value'} did not interpret the value as a timestamp. The same for {d 'value'} (for date) and {t 'value'} (for time). Thanks to Lukas Eder for reporting the issue. The following problem was detected after version 1.4.181 was released: The change in JDBC escape processing affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax {t 'time'}, or {ts 'timestamp'}, or {d 'date'}, then both the client and the server need to be upgraded to version 1.4.181 or later.
#The JDBC escape syntax {ts 'value'} did not interpret the value as a timestamp. The same for {d 'value'} (for date) and {t 'value'} (for time). Thanks to Lukas Eder for reporting the issue. The following problem was detected after version 1.4.181 was released: The change in JDBC escape processing affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax {t 'time'}, or {ts 'timestamp'}, or {d 'date'}, then both the client and the server need to be upgraded to version 1.4.181 or later.
@changelog_1090_li
@changelog_1113_li
#File system abstraction: support replacing existing files using move (currently not for Windows).
#File system abstraction: support replacing existing files using move (currently not for Windows).
@changelog_1091_li
@changelog_1114_li
#The statement "shutdown defrag" now compresses the database (with the MVStore). This command can greatly reduce the file size, and is relatively fast, but is not incremental.
#The statement "shutdown defrag" now compresses the database (with the MVStore). This command can greatly reduce the file size, and is relatively fast, but is not incremental.
@changelog_1092_li
@changelog_1115_li
#The MVStore now automatically compacts the store in the background if there is no read or write activity, which should (after some time; sometimes about one minute) reduce the file size. This is still work in progress, feedback is welcome!
#The MVStore now automatically compacts the store in the background if there is no read or write activity, which should (after some time; sometimes about one minute) reduce the file size. This is still work in progress, feedback is welcome!
@changelog_1093_li
@changelog_1116_li
#Change default value of PAGE_SIZE from 2048 to 4096 to more closely match most file systems block size (PageStore only; the MVStore already used 4096).
#Change default value of PAGE_SIZE from 2048 to 4096 to more closely match most file systems block size (PageStore only; the MVStore already used 4096).
@changelog_1094_li
@changelog_1117_li
#Auto-scale MAX_MEMORY_ROWS and CACHE_SIZE settings by the amount of available RAM. Gives a better out of box experience for people with more powerful machines.
#Auto-scale MAX_MEMORY_ROWS and CACHE_SIZE settings by the amount of available RAM. Gives a better out of box experience for people with more powerful machines.
@changelog_1095_li
@changelog_1118_li
#Handle tabs like 4 spaces in web console, patch by Martin Grajcar.
#Handle tabs like 4 spaces in web console, patch by Martin Grajcar.
@changelog_1096_li
@changelog_1119_li
#Issue 573: Add implementation for Methods "isWrapperFor()" and "unwrap()" in JdbcConnection.java, patch by BigMichi1.
#Issue 573: Add implementation for Methods "isWrapperFor()" and "unwrap()" in JdbcConnection.java, patch by BigMichi1.
@changelog_1097_h2
@changelog_1120_h2
#Version 1.4.180 Beta (2014-07-13)
#Version 1.4.180 Beta (2014-07-13)
@changelog_1098_li
@changelog_1121_li
#MVStore: the store is now auto-compacted automatically up to some point, to avoid very large file sizes. This area is still work in progress.
#MVStore: the store is now auto-compacted automatically up to some point, to avoid very large file sizes. This area is still work in progress.
@changelog_1099_li
@changelog_1122_li
#Sequences of temporary tables (auto-increment or identity columns) were persisted unnecessarily in the database file, and were not removed when re-opening the database.
#Sequences of temporary tables (auto-increment or identity columns) were persisted unnecessarily in the database file, and were not removed when re-opening the database.
@changelog_1100_li
@changelog_1123_li
#MVStore: an IndexOutOfBoundsException could sometimes occur MVMap.openVersion when concurrently accessing the store.
#MVStore: an IndexOutOfBoundsException could sometimes occur MVMap.openVersion when concurrently accessing the store.
@changelog_1101_li
@changelog_1124_li
#The LIRS cache now re-sizes the internal hash map if needed.
#The LIRS cache now re-sizes the internal hash map if needed.
@changelog_1102_li
@changelog_1125_li
#Optionally persist session history in the H2 console. (patch from Martin Grajcar)
#Optionally persist session history in the H2 console. (patch from Martin Grajcar)
@changelog_1103_li
@changelog_1126_li
#Add client-info property to get the number of servers currently in the cluster and which servers that are available. (patch from Nikolaj Fogh)
#Add client-info property to get the number of servers currently in the cluster and which servers that are available. (patch from Nikolaj Fogh)
@changelog_1104_li
@changelog_1127_li
#Fix bug in changing encrypted DB password that kept the file handle open when the wrong password was supplied. (test case from Jens Hohmuth).
#Fix bug in changing encrypted DB password that kept the file handle open when the wrong password was supplied. (test case from Jens Hohmuth).
@changelog_1105_li
@changelog_1128_li
#Issue 567: H2 hangs for a long time then (sometimes) recovers. Introduce a queue when doing table locking to prevent session starvation.
#Issue 567: H2 hangs for a long time then (sometimes) recovers. Introduce a queue when doing table locking to prevent session starvation.
@changelog_1106_h2
@changelog_1129_h2
#Version 1.4.179 Beta (2014-06-23)
#Version 1.4.179 Beta (2014-06-23)
@changelog_1107_li
@changelog_1130_li
#The license was changed to MPL 2.0 (from 1.0) and EPL 1.0.
#The license was changed to MPL 2.0 (from 1.0) and EPL 1.0.
@changelog_1108_li
@changelog_1131_li
#Issue 565: MVStore: concurrently adding LOB objects (with MULTI_THREADED option) resulted in a NullPointerException.
#Issue 565: MVStore: concurrently adding LOB objects (with MULTI_THREADED option) resulted in a NullPointerException.
@changelog_1109_li
@changelog_1132_li
#MVStore: reduced dependencies to other H2 classes.
#MVStore: reduced dependencies to other H2 classes.
@changelog_1110_li
@changelog_1133_li
#There was a way to prevent a database from being re-opened, by creating a column constraint that references a table with a higher id, for example with "check" constraints that contains queries. This is now detected, and creating the table is prohibited. In future versions of H2, most likely creating references to other tables will no longer be supported because of such problems.
#There was a way to prevent a database from being re-opened, by creating a column constraint that references a table with a higher id, for example with "check" constraints that contains queries. This is now detected, and creating the table is prohibited. In future versions of H2, most likely creating references to other tables will no longer be supported because of such problems.
@changelog_1111_li
@changelog_1134_li
#MVStore: descending indexes with "nulls first" did not work as expected (null was ordered last).
#MVStore: descending indexes with "nulls first" did not work as expected (null was ordered last).
@changelog_1112_li
@changelog_1135_li
#Large result sets now always create temporary tables instead of temporary files.
#Large result sets now always create temporary tables instead of temporary files.
@changelog_1113_li
@changelog_1136_li
#When using the PageStore, opening a database failed in some cases with a NullPointerException if temporary tables were used (explicitly, or implicitly when using large result sets).
#When using the PageStore, opening a database failed in some cases with a NullPointerException if temporary tables were used (explicitly, or implicitly when using large result sets).
@changelog_1114_li
@changelog_1137_li
#If a database file in the PageStore file format exists, this file and this mode is now used, even if the database URL does not contain "MV_STORE=FALSE". If a MVStore file exists, it is used.
#If a database file in the PageStore file format exists, this file and this mode is now used, even if the database URL does not contain "MV_STORE=FALSE". If a MVStore file exists, it is used.
@changelog_1115_li
@changelog_1138_li
#Databases created with version 1.3.175 and earlier that contained foreign keys in combination with multi-column indexes could not be opened in some cases. This was due to a bugfix in version 1.3.176: Referential integrity constraints sometimes used the wrong index.
#Databases created with version 1.3.175 and earlier that contained foreign keys in combination with multi-column indexes could not be opened in some cases. This was due to a bugfix in version 1.3.176: Referential integrity constraints sometimes used the wrong index.
@changelog_1116_li
@changelog_1139_li
#MVStore: the ObjectDataType comparison method was incorrect if one key was Serializable and the other was of a common class.
#MVStore: the ObjectDataType comparison method was incorrect if one key was Serializable and the other was of a common class.
@changelog_1117_li
@changelog_1140_li
#Recursive queries with many result rows (more than the setting "max_memory_rows") did not work correctly.
#Recursive queries with many result rows (more than the setting "max_memory_rows") did not work correctly.
@changelog_1118_li
@changelog_1141_li
#The license has changed to MPL 2.0 + EPL 1.0.
#The license has changed to MPL 2.0 + EPL 1.0.
@changelog_1119_li
@changelog_1142_li
#MVStore: temporary tables from result sets could survive re-opening a database, which could result in a ClassCastException.
#MVStore: temporary tables from result sets could survive re-opening a database, which could result in a ClassCastException.
@changelog_1120_li
@changelog_1143_li
#Issue 566: MVStore: unique indexes that were created later on did not work correctly if there were over 5000 rows in the table. Existing databases need to be re-created (at least the broken index need to be re-built).
#Issue 566: MVStore: unique indexes that were created later on did not work correctly if there were over 5000 rows in the table. Existing databases need to be re-created (at least the broken index need to be re-built).
@changelog_1121_li
@changelog_1144_li
#MVStore: creating secondary indexes on large tables results in missing rows in the index.
#MVStore: creating secondary indexes on large tables results in missing rows in the index.
@changelog_1122_li
@changelog_1145_li
#Metadata: the password of linked tables is now only visible for admin users.
#Metadata: the password of linked tables is now only visible for admin users.
@changelog_1123_li
@changelog_1146_li
#For Windows, database URLs of the form "jdbc:h2:/test" where considered relative and did not work unless the system property "h2.implicitRelativePath" was used.
#For Windows, database URLs of the form "jdbc:h2:/test" where considered relative and did not work unless the system property "h2.implicitRelativePath" was used.
@changelog_1124_li
@changelog_1147_li
#Windows: using a base directory of "C:/" and similar did not work as expected.
#Windows: using a base directory of "C:/" and similar did not work as expected.
@changelog_1125_li
@changelog_1148_li
#Follow JDBC specification on Procedures MetaData, use P0 as return type of procedure.
#Follow JDBC specification on Procedures MetaData, use P0 as return type of procedure.
@changelog_1126_li
@changelog_1149_li
#Issue 531: IDENTITY ignored for added column.
#Issue 531: IDENTITY ignored for added column.
@changelog_1127_li
@changelog_1150_li
#FileSystem: improve exception throwing compatibility with JDK
#FileSystem: improve exception throwing compatibility with JDK
@changelog_1128_li
@changelog_1151_li
#Spatial Index: adjust costs so we do not use the spatial index if the query does not contain an intersects operator.
#Spatial Index: adjust costs so we do not use the spatial index if the query does not contain an intersects operator.
@changelog_1129_li
@changelog_1152_li
#Fix multi-threaded deadlock when using a View that includes a TableFunction.
#Fix multi-threaded deadlock when using a View that includes a TableFunction.
@changelog_1130_li
@changelog_1153_li
#Fix bug in dividing very-small BigDecimal numbers.
#Fix bug in dividing very-small BigDecimal numbers.
@changelog_1131_h2
@changelog_1154_h2
#Version 1.4.178 Beta (2014-05-02)
#Version 1.4.178 Beta (2014-05-02)
@changelog_1132_li
@changelog_1155_li
#Issue 559: Make dependency on org.osgi.service.jdbc optional.
#Issue 559: Make dependency on org.osgi.service.jdbc optional.
@changelog_1133_li
@changelog_1156_li
#Improve error message when the user specifies an unsupported combination of database settings.
#Improve error message when the user specifies an unsupported combination of database settings.
@changelog_1134_li
@changelog_1157_li
#MVStore: in the multi-threaded mode, NullPointerException and other exceptions could occur.
#MVStore: in the multi-threaded mode, NullPointerException and other exceptions could occur.
@changelog_1135_li
@changelog_1158_li
#MVStore: some database file could not be compacted due to a bug in the bookkeeping of the fill rate. Also, database file were compacted quite slowly. This has been improved; but more changes in this area are expected.
#MVStore: some database file could not be compacted due to a bug in the bookkeeping of the fill rate. Also, database file were compacted quite slowly. This has been improved; but more changes in this area are expected.
@changelog_1136_li
@changelog_1159_li
#MVStore: support for volatile maps (that don't store changes).
#MVStore: support for volatile maps (that don't store changes).
@changelog_1137_li
@changelog_1160_li
#MVStore mode: in-memory databases now also use the MVStore.
#MVStore mode: in-memory databases now also use the MVStore.
@changelog_1138_li
@changelog_1161_li
#In server mode, appending ";autocommit=false" to the database URL was working, but the return value of Connection.getAutoCommit() was wrong.
#In server mode, appending ";autocommit=false" to the database URL was working, but the return value of Connection.getAutoCommit() was wrong.
@changelog_1139_li
@changelog_1162_li
#Issue 561: OSGi: the import package declaration of org.h2 excluded version 1.4.
#Issue 561: OSGi: the import package declaration of org.h2 excluded version 1.4.
@changelog_1140_li
@changelog_1163_li
#Issue 558: with the MVStore, a NullPointerException could occur when using LOBs at session commit (LobStorageMap.removeLob).
#Issue 558: with the MVStore, a NullPointerException could occur when using LOBs at session commit (LobStorageMap.removeLob).
@changelog_1141_li
@changelog_1164_li
#Remove the "h2.MAX_MEMORY_ROWS_DISTINCT" system property to reduce confusion. We already have the MAX_MEMORY_ROWS setting which does a very similar thing, and is better documented.
#Remove the "h2.MAX_MEMORY_ROWS_DISTINCT" system property to reduce confusion. We already have the MAX_MEMORY_ROWS setting which does a very similar thing, and is better documented.
@changelog_1142_li
@changelog_1165_li
#Issue 554: Web Console in an IFrame was not fully supported.
#Issue 554: Web Console in an IFrame was not fully supported.
@changelog_1143_h2
@changelog_1166_h2
#Version 1.4.177 Beta (2014-04-12)
#Version 1.4.177 Beta (2014-04-12)
@changelog_1144_li
@changelog_1167_li
#By default, the MV_STORE option is enabled, so it is using the new MVStore storage. The MVCC setting is by default set to the same values as the MV_STORE setting, so it is also enabled by default. For testing, both settings can be disabled by appending ";MV_STORE=FALSE" and/or ";MVCC=FALSE" to the database URL.
#By default, the MV_STORE option is enabled, so it is using the new MVStore storage. The MVCC setting is by default set to the same values as the MV_STORE setting, so it is also enabled by default. For testing, both settings can be disabled by appending ";MV_STORE=FALSE" and/or ";MVCC=FALSE" to the database URL.
@changelog_1145_li
@changelog_1168_li
#The file locking method 'serialized' is no longer supported. This mode might return in a future version, however this is not clear right now. A new implementation and new tests would be needed.
#The file locking method 'serialized' is no longer supported. This mode might return in a future version, however this is not clear right now. A new implementation and new tests would be needed.
@changelog_1146_li
@changelog_1169_li
#Enable the new storage format for dates (system property "h2.storeLocalTime"). For the MVStore mode, this is always enabled, but with version 1.4 this is even enabled in the PageStore mode.
#Enable the new storage format for dates (system property "h2.storeLocalTime"). For the MVStore mode, this is always enabled, but with version 1.4 this is even enabled in the PageStore mode.
@changelog_1147_li
@changelog_1170_li
#Implicit relative paths are disabled (system property "h2.implicitRelativePath"), so that the database URL jdbc:h2:test now needs to be written as jdbc:h2:./test.
#Implicit relative paths are disabled (system property "h2.implicitRelativePath"), so that the database URL jdbc:h2:test now needs to be written as jdbc:h2:./test.
@changelog_1148_li
@changelog_1171_li
#"select ... fetch first 1 row only" is supported with the regular mode. This was disabled so far because "fetch" and "offset" are now keywords. See also Mode.supportOffsetFetch.
#"select ... fetch first 1 row only" is supported with the regular mode. This was disabled so far because "fetch" and "offset" are now keywords. See also Mode.supportOffsetFetch.
@changelog_1149_li
@changelog_1172_li
#Byte arrays are now sorted in unsigned mode (x'99' is larger than x'09'). (System property "h2.sortBinaryUnsigned", Mode.binaryUnsigned, setting "binary_collation").
#Byte arrays are now sorted in unsigned mode (x'99' is larger than x'09'). (System property "h2.sortBinaryUnsigned", Mode.binaryUnsigned, setting "binary_collation").
@changelog_1150_li
@changelog_1173_li
#Csv.getInstance will be removed in future versions of 1.4. Use the public constructor instead.
#Csv.getInstance will be removed in future versions of 1.4. Use the public constructor instead.
@changelog_1151_li
@changelog_1174_li
#Remove support for the limited old-style outer join syntax using "(+)". Use "outer join" instead. System property "h2.oldStyleOuterJoin".
#Remove support for the limited old-style outer join syntax using "(+)". Use "outer join" instead. System property "h2.oldStyleOuterJoin".
@changelog_1152_li
@changelog_1175_li
#Support the data type "DATETIME2" as an alias for "DATETIME", for MS SQL Server compatibility.
#Support the data type "DATETIME2" as an alias for "DATETIME", for MS SQL Server compatibility.
@changelog_1153_li
@changelog_1176_li
#Add Oracle-compatible TRANSLATE function, patch by Eric Chatellier.
#Add Oracle-compatible TRANSLATE function, patch by Eric Chatellier.
@changelog_1154_h2
@changelog_1177_h2
#Version 1.3.176 (2014-04-05)
#Version 1.3.176 (2014-04-05)
@changelog_1155_li
@changelog_1178_li
#The file locking method 'serialized' is no longer documented, as it will not be available in version 1.4.
#The file locking method 'serialized' is no longer documented, as it will not be available in version 1.4.
@changelog_1156_li
@changelog_1179_li
#The static method Csv.getInstance() was removed. Use the public constructor instead.
#The static method Csv.getInstance() was removed. Use the public constructor instead.
@changelog_1157_li
@changelog_1180_li
#The default user name for the Script, RunScript, Shell, and CreateCluster tools are no longer "sa" but an empty string.
#The default user name for the Script, RunScript, Shell, and CreateCluster tools are no longer "sa" but an empty string.
@changelog_1158_li
@changelog_1181_li
#The stack trace of the exception "The object is already closed" is no longer logged by default.
#The stack trace of the exception "The object is already closed" is no longer logged by default.
@changelog_1159_li
@changelog_1182_li
#If a value of a result set was itself a result set, the result could only be read once.
#If a value of a result set was itself a result set, the result could only be read once.
@changelog_1160_li
@changelog_1183_li
#Column constraints are also visible in views (patch from Nicolas Fortin for H2GIS).
#Column constraints are also visible in views (patch from Nicolas Fortin for H2GIS).
@changelog_1161_li
@changelog_1184_li
#Granting a additional right to a role that already had a right for that table was not working.
#Granting a additional right to a role that already had a right for that table was not working.
@changelog_1162_li
@changelog_1185_li
#Spatial index: a few bugs have been fixed (using spatial constraints in views, transferring geometry objects over TCP/IP, the returned geometry object is copied when needed).
#Spatial index: a few bugs have been fixed (using spatial constraints in views, transferring geometry objects over TCP/IP, the returned geometry object is copied when needed).
@changelog_1163_li
@changelog_1186_li
#Issue 551: the datatype documentation was incorrect (found by Bernd Eckenfels).
#Issue 551: the datatype documentation was incorrect (found by Bernd Eckenfels).
@changelog_1164_li
@changelog_1187_li
#Issue 368: ON DUPLICATE KEY UPDATE did not work for multi-row inserts. Test case from Angus Macdonald.
#Issue 368: ON DUPLICATE KEY UPDATE did not work for multi-row inserts. Test case from Angus Macdonald.
@changelog_1165_li
@changelog_1188_li
#OSGi: the package javax.tools is now imported (as an optional).
#OSGi: the package javax.tools is now imported (as an optional).
@changelog_1166_li
@changelog_1189_li
#H2 Console: auto-complete is now disabled by default, but there is a hot-key (Ctrl+Space).
#H2 Console: auto-complete is now disabled by default, but there is a hot-key (Ctrl+Space).
@changelog_1167_li
@changelog_1190_li
#H2 Console: auto-complete did not work with multi-line statements.
#H2 Console: auto-complete did not work with multi-line statements.
@changelog_1168_li
@changelog_1191_li
#CLOB and BLOB data was not immediately removed after a rollback.
#CLOB and BLOB data was not immediately removed after a rollback.
@changelog_1169_li
@changelog_1192_li
#There is a new Aggregate API that supports the internal H2 data types (GEOMETRY for example). Thanks a lot to Nicolas Fortin for the patch!
#There is a new Aggregate API that supports the internal H2 data types (GEOMETRY for example). Thanks a lot to Nicolas Fortin for the patch!
@changelog_1170_li
@changelog_1193_li
#Referential integrity constraints sometimes used the wrong index, such that updating a row in the referenced table incorrectly failed with a constraint violation.
#Referential integrity constraints sometimes used the wrong index, such that updating a row in the referenced table incorrectly failed with a constraint violation.
@changelog_1171_li
@changelog_1194_li
#The Polish translation was completed and corrected by Wojtek Jurczyk. Thanks a lot!
#The Polish translation was completed and corrected by Wojtek Jurczyk. Thanks a lot!
@changelog_1172_li
@changelog_1195_li
#Issue 545: Unnecessary duplicate code was removed.
#Issue 545: Unnecessary duplicate code was removed.
@changelog_1173_li
@changelog_1196_li
#The profiler tool can now process files with full thread dumps.
#The profiler tool can now process files with full thread dumps.
@changelog_1174_li
@changelog_1197_li
#MVStore: the file format was changed slightly.
#MVStore: the file format was changed slightly.
@changelog_1175_li
@changelog_1198_li
#MVStore mode: the CLOB and BLOB storage was re-implemented and is now much faster than with the PageStore (which is still the default storage).
#MVStore mode: the CLOB and BLOB storage was re-implemented and is now much faster than with the PageStore (which is still the default storage).
@changelog_1176_li
@changelog_1199_li
#MVStore mode: creating indexes is now much faster (in many cases faster than with the default PageStore).
#MVStore mode: creating indexes is now much faster (in many cases faster than with the default PageStore).
@changelog_1177_li
@changelog_1200_li
#Various bugs in the MVStore storage and have been fixed, including a bug in the R-tree implementation. The database could get corrupt if there were transient IO exceptions while storing.
#Various bugs in the MVStore storage and have been fixed, including a bug in the R-tree implementation. The database could get corrupt if there were transient IO exceptions while storing.
@changelog_1178_li
@changelog_1201_li
#The method org.h2.expression.Function.getCost could throw a NullPointException.
#The method org.h2.expression.Function.getCost could throw a NullPointException.
@changelog_1179_li
@changelog_1202_li
#Storing LOBs in separate files (outside of the main database file) is no longer supported for new databases.
#Storing LOBs in separate files (outside of the main database file) is no longer supported for new databases.
@changelog_1180_li
@changelog_1203_li
#Lucene 2 is no longer supported.
#Lucene 2 is no longer supported.
@changelog_1181_li
@changelog_1204_li
#Fix bug in calculating default MIN and MAX values for SEQUENCE.
#Fix bug in calculating default MIN and MAX values for SEQUENCE.
@changelog_1182_li
@changelog_1205_li
#Fix bug in performing IN queries with multiple values when IGNORECASE=TRUE
#Fix bug in performing IN queries with multiple values when IGNORECASE=TRUE
@changelog_1183_li
@changelog_1206_li
#Add entry-point to org.h2.tools.Shell so it can be called from inside an application. patch by Thomas Gillet.
#Add entry-point to org.h2.tools.Shell so it can be called from inside an application. patch by Thomas Gillet.
@changelog_1184_li
@changelog_1207_li
#Fix bug that prevented the PgServer from being stopped and started multiple times.
#Fix bug that prevented the PgServer from being stopped and started multiple times.
@changelog_1185_li
@changelog_1208_li
#Support some more DDL syntax for MySQL, patch from Peter Jentsch.
#Support some more DDL syntax for MySQL, patch from Peter Jentsch.
@changelog_1186_li
@changelog_1209_li
#Issue 548: TO_CHAR does not format MM and DD correctly when the month or day of the month is 1 digit, patch from "the.tucc"
#Issue 548: TO_CHAR does not format MM and DD correctly when the month or day of the month is 1 digit, patch from "the.tucc"
@changelog_1187_li
@changelog_1210_li
#Fix bug in varargs support in ALIAS's, patch from Nicolas Fortin
#Fix bug in varargs support in ALIAS's, patch from Nicolas Fortin
#Support index-only when doing selects (i.e. without needing to load the actual table data)
@roadmap_1511_h2
#Not Planned
#Not Planned
@roadmap_1511_li
@roadmap_1512_li
#HSQLDB (did) support this: select id i from test where i<0 (other databases don't). Supporting it may break compatibility.
#HSQLDB (did) support this: select id i from test where i<0 (other databases don't). Supporting it may break compatibility.
@roadmap_1512_li
@roadmap_1513_li
#String.intern (so that Strings can be compared with ==) will not be used because some VMs have problems when used extensively.
#String.intern (so that Strings can be compared with ==) will not be used because some VMs have problems when used extensively.
@roadmap_1513_li
@roadmap_1514_li
#In prepared statements, identifier names (table names and so on) can not be parameterized. Adding such a feature would complicate the source code without providing reasonable speedup, and would slow down regular prepared statements.
#In prepared statements, identifier names (table names and so on) can not be parameterized. Adding such a feature would complicate the source code without providing reasonable speedup, and would slow down regular prepared statements.
@@ -92,9 +92,9 @@ advanced_1090_p=\ If a connection cannot get a lock on an object, the connection
...
@@ -92,9 +92,9 @@ advanced_1090_p=\ If a connection cannot get a lock on an object, the connection
advanced_1091_h2=Multi-Version Concurrency Control (MVCC)
advanced_1091_h2=Multi-Version Concurrency Control (MVCC)
advanced_1092_p=\ The MVCC feature allows higher concurrency than using (table level or row level) locks. When using MVCC in this database, delete, insert and update operations will only issue a shared lock on the table. An exclusive lock is still used when adding or removing columns, when dropping the table, and when using <code>SELECT ... FOR UPDATE</code>. Connections only 'see' committed data, and own changes. That means, if connection A updates a row but doesn't commit this change yet, connection B will see the old value. Only when the change is committed, the new value is visible by other connections (read committed). If multiple connections concurrently try to update the same row, the database waits until it can apply the change, but at most until the lock timeout expires.
advanced_1092_p=\ The MVCC feature allows higher concurrency than using (table level or row level) locks. When using MVCC in this database, delete, insert and update operations will only issue a shared lock on the table. An exclusive lock is still used when adding or removing columns, when dropping the table, and when using <code>SELECT ... FOR UPDATE</code>. Connections only 'see' committed data, and own changes. That means, if connection A updates a row but doesn't commit this change yet, connection B will see the old value. Only when the change is committed, the new value is visible by other connections (read committed). If multiple connections concurrently try to update the same row, the database waits until it can apply the change, but at most until the lock timeout expires.
advanced_1093_p=\ To use the MVCC feature, append <code>;MVCC\=TRUE</code> to the database URL\:
advanced_1093_p=\ To use the MVCC feature, append <code>;MVCC\=TRUE</code> to the database URL\:
advanced_1094_p=\ MVCC is disabled by default. The MVCC feature is not fully tested yet. The limitations of the MVCC mode are\:it can not be used at the same time as <code>MULTI_THREADED\=TRUE</code>; the complete undo log (the list of uncommitted changes) must fit in memory when using multi-version concurrency. The setting <code>MAX_MEMORY_UNDO</code> has no effect. It is not possible to enable or disable this setting while the database is already open. The setting must be specified in the first connection (the one that opens the database).
advanced_1094_p=\ The setting must be specified in the first connection (the one that opens the database). It is not possible to enable or disable this setting while the database is already open.
advanced_1095_p=\ If MVCC is enabled, changing the lock mode (<code>LOCK_MODE</code>) has no effect.
advanced_1095_p=\ If MVCC is enabled, changing the lock mode (<code>LOCK_MODE</code>) has no effect.
advanced_1096_h2=Clustering / High Availability
advanced_1096_div=\ The MVCC mode is enabled by default in version 1.4.x, with the default MVStore storage engine. MVCC is disabled by default when using the PageStore storage engine (which is the default in version 1.3.x). The following applies when using the PageStore storage engine\:The MVCC feature is not fully tested yet. The limitations of the MVCC mode are\:with the PageStore storage engine, it can not be used at the same time as <code>MULTI_THREADED\=TRUE</code>; the complete undo log (the list of uncommitted changes) must fit in memory when using multi-version concurrency. The setting <code>MAX_MEMORY_UNDO</code> has no effect. Clustering / High Availability
advanced_1097_p=\ This database supports a simple clustering / high availability mechanism. The architecture is\:two database servers run on two different computers, and on both computers is a copy of the same database. If both servers run, each database operation is executed on both computers. If one server fails (power, hardware or network failure), the other server can still continue to work. From this point on, the operations will be executed only on one server until the other server is back up.
advanced_1097_p=\ This database supports a simple clustering / high availability mechanism. The architecture is\:two database servers run on two different computers, and on both computers is a copy of the same database. If both servers run, each database operation is executed on both computers. If one server fails (power, hardware or network failure), the other server can still continue to work. From this point on, the operations will be executed only on one server until the other server is back up.
advanced_1098_p=\ Clustering can only be used in the server mode (the embedded mode does not support clustering). The cluster can be re-created using the <code>CreateCluster</code> tool without stopping the remaining server. Applications that are still connected are automatically disconnected, however when appending <code>;AUTO_RECONNECT\=TRUE</code>, they will recover from that.
advanced_1098_p=\ Clustering can only be used in the server mode (the embedded mode does not support clustering). The cluster can be re-created using the <code>CreateCluster</code> tool without stopping the remaining server. Applications that are still connected are automatically disconnected, however when appending <code>;AUTO_RECONNECT\=TRUE</code>, they will recover from that.
advanced_1099_p=\ To initialize the cluster, use the following steps\:
advanced_1099_p=\ To initialize the cluster, use the following steps\:
...
@@ -628,192 +628,215 @@ build_1111_li=The rail images (one straight, four junctions, two turns) are gene
...
@@ -628,192 +628,215 @@ 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=-
changelog_1002_li=MVStore\:concurrent changes to the same row could result in the exception "The transaction log might be corrupt for key ...". This could only be reproduced with 3 or more threads.
changelog_1003_li=Results with CLOB or BLOB data are no longer reused.
changelog_1004_li=The Servlet API 3.0.1 is now used, instead of 2.4.
changelog_1004_li=References to BLOB and CLOB objects now have a timeout. The configuration setting is LOB_TIMEOUT (default 5 minutes). This should avoid growing the database file if there are many queries that return BLOB or CLOB objects, and the database is not closed for a longer time.
changelog_1005_li=MVStore\:old chunks no longer removed in append-only mode.
changelog_1005_li=MVStore\:when committing a session that removed LOB values, changes were flushed unnecessarily.
changelog_1006_li=MVStore\:the cache for page references could grow far too big, resulting in out of memory in some cases.
changelog_1006_li=Issue 610\:possible integer overflow in WriteBuffer.grow().
changelog_1007_li=MVStore\:orphaned lob objects were not correctly removed in some cases, making the database grow unnecessarily.
changelog_1007_li=Issue 609\:the spatial index did not support NULL (ClassCastException).
changelog_1008_li=MVStore\:the maximum cache size was artificially limited to 2 GB (due to an integer overflow).
changelog_1008_li=MVStore\:in some cases, CLOB/BLOB data blocks were removed incorrectly when opening a database.
changelog_1009_li=MVStore / TransactionStore\:concurrent updates could result in a "Too many open transactions" exception.
changelog_1009_li=MVStore\:updates that affected many rows were were slow in some cases if there was a secondary index.
changelog_1010_li=StringUtils.toUpperEnglish now has a small cache. This should speed up reading from a ResultSet when using the column name.
changelog_1010_li=Using "runscript" with autocommit disabled could result in a lock timeout on the internal table "SYS".
changelog_1011_li=MVStore\:up to 65535 open transactions are now supported. Previously, the limit was at most 65535 transactions between the oldest open and the newest open transaction (which was quite a strange limit).
changelog_1011_li=Issue 603\:there was a memory leak when using H2 in a web application. Apache Tomcat logged an error message\:"The web application ... created a ThreadLocal with key of type [org.h2.util.DateTimeUtils$1]".
changelog_1012_li=The default limit for in-place LOB objects was changed from 128 to 256 bytes. This is because each read creates a reference to a LOB, and maintaining the references is a big overhead. With the higher limit, less references are needed.
changelog_1012_li=When using the MVStore, running a SQL script generate by the Recover tool from a PageStore file failed with a strange error message (NullPointerException), now a clear error message is shown.
changelog_1013_li=Tables without columns didn't work. (The use case for such tables is testing.)
changelog_1013_li=Issue 605\:with version 1.4.186, opening a database could result in an endless loop in LobStorageMap.init.
changelog_1014_li=The LIRS cache now resizes the table automatically in all cases and no longer needs the averageMemory configuration.
changelog_1014_li=Queries that use the same table alias multiple times now work. Before, the select expression list was expanded incorrectly. Example\:"select * from a as x, b as x".
changelog_1015_li=Creating a linked table from an MVStore database to a non-MVStore database created a second (non-MVStore) database file.
changelog_1015_li=The MySQL compatibility feature "insert ... on duplicate key update" did not work with a non-default schema.
changelog_1016_li=In version 1.4.184, a bug was introduced that broke queries that have both joins and wildcards, for example\:select * from dual join(select x from dual) on 1\=1
changelog_1016_li=Issue 599\:the condition "in(x, y)" could not be used in the select list when using "group by".
changelog_1017_li=Issue 598\:parser fails on timestamp "24\:00\:00.1234" - prevent the creation of out-of-range time values.
changelog_1017_li=The LIRS cache could grow larger than the allocated memory.
changelog_1018_li=Allow declaring triggers as source code (like functions). Patch by Sylvain Cuaz.
changelog_1018_li=A new file system implementation that re-opens the file if it was closed due to the application calling Thread.interrupt(). File name prefix "retry\:". Please note it is strongly recommended to avoid calling Thread.interrupt; this is a problem for various libraries, including Apache Lucene.
changelog_1019_li=Make the planner use indexes for sorting when doing a GROUP BY where all of the GROUP BY columns are not mentioned in the select. Patch by Frederico (zepfred).
changelog_1019_li=MVStore\: use RandomAccessFile file system if the file name starts with "file\:".
changelog_1020_li=PostgreSQL compatibility\:generate_series (as an alias for system_range). Patch by litailang.
changelog_1020_li=Allow DATEADD to take a long value for count when manipulating milliseconds.
changelog_1021_li=Fix missing "column" type in right-hand parameter in ConditionIn. Patch by Arnaud Thimel.
changelog_1021_li=When using MV_STORE\=TRUE and the SET CACHE_SIZE setting, the cache size was incorrectly set, so that it was effectively 1024 times smaller than it should be.
changelog_1022_li=Concurrent CREATE TABLE... IF NOT EXISTS in the presence of MULTI_THREAD\=TRUE could throw an exception.
changelog_1023_li=In version 1.4.184, "group by" ignored the table name, and could pick a select column by mistake. Example\:select 0 as x from system_range(1, 2) d group by d.x;
changelog_1023_li=Fix bug in MVStore when creating lots of temporary tables, where we could run out of transaction IDs.
changelog_1024_li=New connection setting "REUSE_SPACE" (default\:true). If disabled, all changes are appended to the database file, and existing content is never overwritten. This allows to rollback to a previous state of the database by truncating the database file.
changelog_1024_li=Add support for PostgreSQL STRING_AGG function. Patch by Fred Aquiles.
changelog_1025_li=Issue 587\:MVStore\:concurrent compaction and store operations could result in an IllegalStateException.
changelog_1025_li=Fix bug in "jdbc\:h2\:nioMemFS" isRoot() function
changelog_1026_li=Issue 594\:Profiler.copyInThread does not work properly.
changelog_1027_li=Script tool\:Now, SCRIPT ... TO is always used (for higher speed and lower disk space usage).
changelog_1027_li=The Servlet API 3.0.1 is now used, instead of 2.4.
changelog_1028_li=Script tool\:Fix parsing of BLOCKSIZE parameter, original patch by Ken Jorissen.
changelog_1028_li=MVStore\:old chunks no longer removed in append-only mode.
changelog_1029_li=Fix bug in PageStore\#commit method - when the ignoreBigLog flag was set, the logic that cleared the flag could never be reached, resulting in performance degradation. Reported by Alexander Nesterov.
changelog_1029_li=MVStore\:the cache for page references could grow far too big, resulting in out of memory in some cases.
changelog_1030_li=Issue 552\:Implement BIT_AND and BIT_OR aggregate functions.
changelog_1030_li=MVStore\:orphaned lob objects were not correctly removed in some cases, making the database grow unnecessarily.
changelog_1031_li=MVStore\:the maximum cache size was artificially limited to 2 GB (due to an integer overflow).
changelog_1032_li=In version 1.3.183, indexes were not used if the table contains columns with a default value generated by a sequence. This includes tables with identity and auto-increment columns. This bug was introduced by supporting "rownum" in views and derived tables.
changelog_1032_li=MVStore / TransactionStore\:concurrent updates could result in a "Too many open transactions" exception.
changelog_1033_li=MVStore\:imported BLOB and CLOB data sometimes disappeared. This was caused by a bug in the ObjectDataType comparison.
changelog_1033_li=StringUtils.toUpperEnglish now has a small cache. This should speed up reading from a ResultSet when using the column name.
changelog_1034_li=Reading from a StreamStore now throws an IOException if the underlying data doesn't exist.
changelog_1034_li=MVStore\:up to 65535 open transactions are now supported. Previously, the limit was at most 65535 transactions between the oldest open and the newest open transaction (which was quite a strange limit).
changelog_1035_li=MVStore\:if there is an exception while saving, the store is now in all cases immediately closed.
changelog_1035_li=The default limit for in-place LOB objects was changed from 128 to 256 bytes. This is because each read creates a reference to a LOB, and maintaining the references is a big overhead. With the higher limit, less references are needed.
changelog_1036_li=MVStore\:the dump tool could go into an endless loop for some files.
changelog_1036_li=Tables without columns didn't work. (The use case for such tables is testing.)
changelog_1037_li=MVStore\:recovery for a database with many CLOB or BLOB entries is now much faster.
changelog_1037_li=The LIRS cache now resizes the table automatically in all cases and no longer needs the averageMemory configuration.
changelog_1038_li=Group by with a quoted select column name alias didn't work. Example\:select 1 "a" from dual group by "a"
changelog_1038_li=Creating a linked table from an MVStore database to a non-MVStore database created a second (non-MVStore) database file.
changelog_1039_li=Auto-server mode\:the host name is now stored in the .lock.db file.
changelog_1039_li=In version 1.4.184, a bug was introduced that broke queries that have both joins and wildcards, for example\:select * from dual join(select x from dual) on 1\=1
changelog_1040_li=Issue 598\:parser fails on timestamp "24\:00\:00.1234" - prevent the creation of out-of-range time values.
changelog_1041_li=MVStore\:the default auto-commit buffer size is now about twice as big. This should reduce the database file size after inserting a lot of data.
changelog_1041_li=Allow declaring triggers as source code (like functions). Patch by Sylvain Cuaz.
changelog_1042_li=The built-in functions "power" and "radians" now always return a double.
changelog_1042_li=Make the planner use indexes for sorting when doing a GROUP BY where all of the GROUP BY columns are not mentioned in the select. Patch by Frederico (zepfred).
changelog_1043_li=Using "row_number" or "rownum" in views or derived tables had unexpected results if the outer query contained constraints for the given view. Example\:select b.nr, b.id from (select row_number() over() as nr, a.id as id from (select id from test order by name) as a) as b where b.id \=1
changelog_1043_li=PostgreSQL compatibility\:generate_series (as an alias for system_range). Patch by litailang.
changelog_1044_li=MVStore\:the Recover tool can now deal with more types of corruption in the file.
changelog_1044_li=Fix missing "column" type in right-hand parameter in ConditionIn. Patch by Arnaud Thimel.
changelog_1045_li=MVStore\:the TransactionStore now first needs to be initialized before it can be used.
changelog_1046_li=Views and derived tables with equality and range conditions on the same columns did not work properly. example\:select x from (select x from (select 1 as x) where x > 0 and x < 2) where x \=1
changelog_1046_li=In version 1.4.184, "group by" ignored the table name, and could pick a select column by mistake. Example\:select 0 as x from system_range(1, 2) d group by d.x;
changelog_1047_li=The database URL setting PAGE_SIZE setting is now also used for the MVStore.
changelog_1047_li=New connection setting "REUSE_SPACE" (default\:true). If disabled, all changes are appended to the database file, and existing content is never overwritten. This allows to rollback to a previous state of the database by truncating the database file.
changelog_1048_li=MVStore\:the default page split size for persistent stores is now 4096 (it was 16 KB so far). This should reduce the database file size for most situations (in some cases, less than half the size of the previous version).
changelog_1048_li=Issue 587\:MVStore\:concurrent compaction and store operations could result in an IllegalStateException.
changelog_1049_li=With query literals disabled, auto-analyze of a table with CLOB or BLOB did not work.
changelog_1049_li=Issue 594\:Profiler.copyInThread does not work properly.
changelog_1050_li=MVStore\:use a mark and sweep GC algorithm instead of reference counting, to ensure used chunks are never overwrite, even if the reference counting algorithm does not work properly.
changelog_1050_li=Script tool\:Now, SCRIPT ... TO is always used (for higher speed and lower disk space usage).
changelog_1051_li=In the multi-threaded mode, updating the column selectivity ("analyze") in the background sometimes did not work.
changelog_1051_li=Script tool\:Fix parsing of BLOCKSIZE parameter, original patch by Ken Jorissen.
changelog_1052_li=In the multi-threaded mode, database metadata operations did sometimes not work if the schema was changed at the same time (for example, if tables were dropped).
changelog_1052_li=Fix bug in PageStore\#commit method - when the ignoreBigLog flag was set, the logic that cleared the flag could never be reached, resulting in performance degradation. Reported by Alexander Nesterov.
changelog_1053_li=Some CLOB and BLOB values could no longer be read when the original row was removed (even when using the MVCC mode).
changelog_1053_li=Issue 552\:Implement BIT_AND and BIT_OR aggregate functions.
changelog_1054_li=The MVStoreTool could throw an IllegalArgumentException.
changelog_1055_li=Improved performance for some date / time / timestamp conversion operations. Thanks to Sergey Evdokimov for reporting the problem.
changelog_1055_li=In version 1.3.183, indexes were not used if the table contains columns with a default value generated by a sequence. This includes tables with identity and auto-increment columns. This bug was introduced by supporting "rownum" in views and derived tables.
changelog_1056_li=H2 Console\:the built-in web server did not work properly if an unknown file was requested.
changelog_1056_li=MVStore\:imported BLOB and CLOB data sometimes disappeared. This was caused by a bug in the ObjectDataType comparison.
changelog_1057_li=MVStore\:the jar file is renamed to "h2-mvstore-*.jar" and is deployed to Maven separately.
changelog_1057_li=Reading from a StreamStore now throws an IOException if the underlying data doesn't exist.
changelog_1058_li=MVStore\:support for concurrent reads and writes is now enabled by default.
changelog_1058_li=MVStore\:if there is an exception while saving, the store is now in all cases immediately closed.
changelog_1059_li=Server mode\:the transfer buffer size has been changed from 16 KB to 64 KB, after it was found that this improves performance on Linux quite a lot.
changelog_1059_li=MVStore\:the dump tool could go into an endless loop for some files.
changelog_1060_li=H2 Console and server mode\:SSL is now disabled and TLS is used to protect against the Poodle SSLv3 vulnerability. The system property to disable secure anonymous connections is now "h2.enableAnonymousTLS". The default certificate is still self-signed, so you need to manually install another one if you want to avoid man in the middle attacks.
changelog_1060_li=MVStore\:recovery for a database with many CLOB or BLOB entries is now much faster.
changelog_1061_li=MVStore\:the R-tree did not correctly measure the memory usage.
changelog_1061_li=Group by with a quoted select column name alias didn't work. Example\:select 1 "a" from dual group by "a"
changelog_1062_li=MVStore\:compacting a store with an R-tree did not always work.
changelog_1062_li=Auto-server mode\:the host name is now stored in the .lock.db file.
changelog_1063_li=Issue 581\:When running in LOCK_MODE\=0, JdbcDatabaseMetaData\#supportsTransactionIsolationLevel(TRANSACTION_READ_UNCOMMITTED) should return false
changelog_1064_li=Fix bug which could generate deadlocks when multiple connections accessed the same table.
changelog_1064_li=MVStore\:the default auto-commit buffer size is now about twice as big. This should reduce the database file size after inserting a lot of data.
changelog_1065_li=Some places in the code were not respecting the value set in the "SET MAX_MEMORY_ROWS x" command
changelog_1065_li=The built-in functions "power" and "radians" now always return a double.
changelog_1066_li=Fix bug which could generate a NegativeArraySizeException when performing large (>40M) row union operations
changelog_1066_li=Using "row_number" or "rownum" in views or derived tables had unexpected results if the outer query contained constraints for the given view. Example\:select b.nr, b.id from (select row_number() over() as nr, a.id as id from (select id from test order by name) as a) as b where b.id \=1
changelog_1067_li=Fix "USE schema" command for MySQL compatibility, patch by mfulton
changelog_1067_li=MVStore\:the Recover tool can now deal with more types of corruption in the file.
changelog_1068_li=Parse and ignore the ROW_FORMAT\=DYNAMIC MySQL syntax, patch by mfulton
changelog_1068_li=MVStore\:the TransactionStore now first needs to be initialized before it can be used.
changelog_1069_li=Views and derived tables with equality and range conditions on the same columns did not work properly. example\:select x from (select x from (select 1 as x) where x > 0 and x < 2) where x \=1
changelog_1070_li=MVStore\:improved error messages and logging; improved behavior if there is an error when serializing objects.
changelog_1070_li=The database URL setting PAGE_SIZE setting is now also used for the MVStore.
changelog_1071_li=OSGi\:the MVStore packages are now exported.
changelog_1071_li=MVStore\:the default page split size for persistent stores is now 4096 (it was 16 KB so far). This should reduce the database file size for most situations (in some cases, less than half the size of the previous version).
changelog_1072_li=With the MVStore option, when using multiple threads that concurrently create indexes or tables, it was relatively easy to get a lock timeout on the "SYS" table.
changelog_1072_li=With query literals disabled, auto-analyze of a table with CLOB or BLOB did not work.
changelog_1073_li=When using the multi-threaded option, the exception "Unexpected code path" could be thrown, specially if the option "analyze_auto" was set to a low value.
changelog_1073_li=MVStore\:use a mark and sweep GC algorithm instead of reference counting, to ensure used chunks are never overwrite, even if the reference counting algorithm does not work properly.
changelog_1074_li=In the server mode, when reading from a CLOB or BLOB, if the connection was closed, a NullPointerException could be thrown instead of an exception saying the connection is closed.
changelog_1074_li=In the multi-threaded mode, updating the column selectivity ("analyze") in the background sometimes did not work.
changelog_1075_li=DatabaseMetaData.getProcedures and getProcedureColumns could throw an exception if a user defined class is not available.
changelog_1075_li=In the multi-threaded mode, database metadata operations did sometimes not work if the schema was changed at the same time (for example, if tables were dropped).
changelog_1076_li=Issue 584\:the error message for a wrong sequence definition was wrong.
changelog_1076_li=Some CLOB and BLOB values could no longer be read when the original row was removed (even when using the MVCC mode).
changelog_1077_li=CSV tool\:the rowSeparator option is no longer supported, as the same can be achieved with the lineSeparator.
changelog_1077_li=The MVStoreTool could throw an IllegalArgumentException.
changelog_1078_li=Descending indexes on MVStore tables did not work properly.
changelog_1078_li=Improved performance for some date / time / timestamp conversion operations. Thanks to Sergey Evdokimov for reporting the problem.
changelog_1079_li=Issue 579\:Conditions on the "_rowid_" pseudo-column didn't use an index when using the MVStore.
changelog_1079_li=H2 Console\:the built-in web server did not work properly if an unknown file was requested.
changelog_1080_li=Fixed documentation that "offset" and "fetch" are also keywords since version 1.4.x.
changelog_1080_li=MVStore\:the jar file is renamed to "h2-mvstore-*.jar" and is deployed to Maven separately.
changelog_1081_li=The Long.MIN_VALUE could not be parsed for auto-increment (identity) columns.
changelog_1081_li=MVStore\:support for concurrent reads and writes is now enabled by default.
changelog_1082_li=Issue 573\:Add implementation for Methods "isWrapperFor()" and "unwrap()" in other JDBC classes.
changelog_1082_li=Server mode\:the transfer buffer size has been changed from 16 KB to 64 KB, after it was found that this improves performance on Linux quite a lot.
changelog_1083_li=Issue 572\:MySQL compatibility for "order by" in update statements.
changelog_1083_li=H2 Console and server mode\:SSL is now disabled and TLS is used to protect against the Poodle SSLv3 vulnerability. The system property to disable secure anonymous connections is now "h2.enableAnonymousTLS". The default certificate is still self-signed, so you need to manually install another one if you want to avoid man in the middle attacks.
changelog_1084_li=The change in JDBC escape processing in version 1.4.181 affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax "{t 'time}", or "{ts 'timestamp'}", or "{d 'data'}", then both the client and the server need to be upgraded to version 1.4.181 or later.
changelog_1084_li=MVStore\:the R-tree did not correctly measure the memory usage.
changelog_1085_li=MVStore\:compacting a store with an R-tree did not always work.
changelog_1086_li=Improved MySQL compatibility by supporting "use schema". Thanks a lot to Karl Pietrzak for the patch\!
changelog_1086_li=Issue 581\:When running in LOCK_MODE\=0, JdbcDatabaseMetaData\#supportsTransactionIsolationLevel(TRANSACTION_READ_UNCOMMITTED) should return false
changelog_1087_li=Writing to the trace file is now faster, specially with the debug level.
changelog_1087_li=Fix bug which could generate deadlocks when multiple connections accessed the same table.
changelog_1088_li=The database option "defrag_always\=true" did not work with the MVStore.
changelog_1088_li=Some places in the code were not respecting the value set in the "SET MAX_MEMORY_ROWS x" command
changelog_1089_li=The JDBC escape syntax {ts 'value'} did not interpret the value as a timestamp. The same for {d 'value'} (for date) and {t 'value'} (for time). Thanks to Lukas Eder for reporting the issue. The following problem was detected after version 1.4.181 was released\:The change in JDBC escape processing affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax {t 'time'}, or {ts 'timestamp'}, or {d 'date'}, then both the client and the server need to be upgraded to version 1.4.181 or later.
changelog_1089_li=Fix bug which could generate a NegativeArraySizeException when performing large (>40M) row union operations
changelog_1090_li=File system abstraction\:support replacing existing files using move (currently not for Windows).
changelog_1090_li=Fix "USE schema" command for MySQL compatibility, patch by mfulton
changelog_1091_li=The statement "shutdown defrag" now compresses the database (with the MVStore). This command can greatly reduce the file size, and is relatively fast, but is not incremental.
changelog_1091_li=Parse and ignore the ROW_FORMAT\=DYNAMIC MySQL syntax, patch by mfulton
changelog_1092_li=The MVStore now automatically compacts the store in the background if there is no read or write activity, which should (after some time; sometimes about one minute) reduce the file size. This is still work in progress, feedback is welcome\!
changelog_1093_li=Change default value of PAGE_SIZE from 2048 to 4096 to more closely match most file systems block size (PageStore only; the MVStore already used 4096).
changelog_1093_li=MVStore\:improved error messages and logging; improved behavior if there is an error when serializing objects.
changelog_1094_li=Auto-scale MAX_MEMORY_ROWS and CACHE_SIZE settings by the amount of available RAM. Gives a better out of box experience for people with more powerful machines.
changelog_1094_li=OSGi\:the MVStore packages are now exported.
changelog_1095_li=Handle tabs like 4 spaces in web console, patch by Martin Grajcar.
changelog_1095_li=With the MVStore option, when using multiple threads that concurrently create indexes or tables, it was relatively easy to get a lock timeout on the "SYS" table.
changelog_1096_li=Issue 573\:Add implementation for Methods "isWrapperFor()" and "unwrap()" in JdbcConnection.java, patch by BigMichi1.
changelog_1096_li=When using the multi-threaded option, the exception "Unexpected code path" could be thrown, specially if the option "analyze_auto" was set to a low value.
changelog_1097_li=In the server mode, when reading from a CLOB or BLOB, if the connection was closed, a NullPointerException could be thrown instead of an exception saying the connection is closed.
changelog_1098_li=MVStore\:the store is now auto-compacted automatically up to some point, to avoid very large file sizes. This area is still work in progress.
changelog_1098_li=DatabaseMetaData.getProcedures and getProcedureColumns could throw an exception if a user defined class is not available.
changelog_1099_li=Sequences of temporary tables (auto-increment or identity columns) were persisted unnecessarily in the database file, and were not removed when re-opening the database.
changelog_1099_li=Issue 584\:the error message for a wrong sequence definition was wrong.
changelog_1100_li=MVStore\:an IndexOutOfBoundsException could sometimes occur MVMap.openVersion when concurrently accessing the store.
changelog_1100_li=CSV tool\:the rowSeparator option is no longer supported, as the same can be achieved with the lineSeparator.
changelog_1101_li=The LIRS cache now re-sizes the internal hash map if needed.
changelog_1101_li=Descending indexes on MVStore tables did not work properly.
changelog_1102_li=Optionally persist session history in the H2 console. (patch from Martin Grajcar)
changelog_1102_li=Issue 579\:Conditions on the "_rowid_" pseudo-column didn't use an index when using the MVStore.
changelog_1103_li=Add client-info property to get the number of servers currently in the cluster and which servers that are available. (patch from Nikolaj Fogh)
changelog_1103_li=Fixed documentation that "offset" and "fetch" are also keywords since version 1.4.x.
changelog_1104_li=Fix bug in changing encrypted DB password that kept the file handle open when the wrong password was supplied. (test case from Jens Hohmuth).
changelog_1104_li=The Long.MIN_VALUE could not be parsed for auto-increment (identity) columns.
changelog_1105_li=Issue 567\:H2 hangs for a long time then (sometimes) recovers. Introduce a queue when doing table locking to prevent session starvation.
changelog_1105_li=Issue 573\:Add implementation for Methods "isWrapperFor()" and "unwrap()" in other JDBC classes.
changelog_1106_li=Issue 572\:MySQL compatibility for "order by" in update statements.
changelog_1107_li=The license was changed to MPL 2.0 (from 1.0) and EPL 1.0.
changelog_1107_li=The change in JDBC escape processing in version 1.4.181 affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax "{t 'time}", or "{ts 'timestamp'}", or "{d 'data'}", then both the client and the server need to be upgraded to version 1.4.181 or later.
changelog_1108_li=Issue 565\:MVStore\:concurrently adding LOB objects (with MULTI_THREADED option) resulted in a NullPointerException.
changelog_1109_li=MVStore\:reduced dependencies to other H2 classes.
changelog_1109_li=Improved MySQL compatibility by supporting "use schema". Thanks a lot to Karl Pietrzak for the patch\!
changelog_1110_li=There was a way to prevent a database from being re-opened, by creating a column constraint that references a table with a higher id, for example with "check" constraints that contains queries. This is now detected, and creating the table is prohibited. In future versions of H2, most likely creating references to other tables will no longer be supported because of such problems.
changelog_1110_li=Writing to the trace file is now faster, specially with the debug level.
changelog_1111_li=MVStore\:descending indexes with "nulls first" did not work as expected (null was ordered last).
changelog_1111_li=The database option "defrag_always\=true" did not work with the MVStore.
changelog_1112_li=Large result sets now always create temporary tables instead of temporary files.
changelog_1112_li=The JDBC escape syntax {ts 'value'} did not interpret the value as a timestamp. The same for {d 'value'} (for date) and {t 'value'} (for time). Thanks to Lukas Eder for reporting the issue. The following problem was detected after version 1.4.181 was released\:The change in JDBC escape processing affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax {t 'time'}, or {ts 'timestamp'}, or {d 'date'}, then both the client and the server need to be upgraded to version 1.4.181 or later.
changelog_1113_li=When using the PageStore, opening a database failed in some cases with a NullPointerException if temporary tables were used (explicitly, or implicitly when using large result sets).
changelog_1113_li=File system abstraction\:support replacing existing files using move (currently not for Windows).
changelog_1114_li=If a database file in the PageStore file format exists, this file and this mode is now used, even if the database URL does not contain "MV_STORE\=FALSE". If a MVStore file exists, it is used.
changelog_1114_li=The statement "shutdown defrag" now compresses the database (with the MVStore). This command can greatly reduce the file size, and is relatively fast, but is not incremental.
changelog_1115_li=Databases created with version 1.3.175 and earlier that contained foreign keys in combination with multi-column indexes could not be opened in some cases. This was due to a bugfix in version 1.3.176\:Referential integrity constraints sometimes used the wrong index.
changelog_1115_li=The MVStore now automatically compacts the store in the background if there is no read or write activity, which should (after some time; sometimes about one minute) reduce the file size. This is still work in progress, feedback is welcome\!
changelog_1116_li=MVStore\:the ObjectDataType comparison method was incorrect if one key was Serializable and the other was of a common class.
changelog_1116_li=Change default value of PAGE_SIZE from 2048 to 4096 to more closely match most file systems block size (PageStore only; the MVStore already used 4096).
changelog_1117_li=Recursive queries with many result rows (more than the setting "max_memory_rows") did not work correctly.
changelog_1117_li=Auto-scale MAX_MEMORY_ROWS and CACHE_SIZE settings by the amount of available RAM. Gives a better out of box experience for people with more powerful machines.
changelog_1118_li=The license has changed to MPL 2.0 + EPL 1.0.
changelog_1118_li=Handle tabs like 4 spaces in web console, patch by Martin Grajcar.
changelog_1119_li=MVStore\:temporary tables from result sets could survive re-opening a database, which could result in a ClassCastException.
changelog_1119_li=Issue 573\:Add implementation for Methods "isWrapperFor()" and "unwrap()" in JdbcConnection.java, patch by BigMichi1.
changelog_1120_li=Issue 566\:MVStore\:unique indexes that were created later on did not work correctly if there were over 5000 rows in the table. Existing databases need to be re-created (at least the broken index need to be re-built).
changelog_1121_li=MVStore\:creating secondary indexes on large tables results in missing rows in the index.
changelog_1121_li=MVStore\:the store is now auto-compacted automatically up to some point, to avoid very large file sizes. This area is still work in progress.
changelog_1122_li=Metadata\:the password of linked tables is now only visible for admin users.
changelog_1122_li=Sequences of temporary tables (auto-increment or identity columns) were persisted unnecessarily in the database file, and were not removed when re-opening the database.
changelog_1123_li=For Windows, database URLs of the form "jdbc\:h2\:/test" where considered relative and did not work unless the system property "h2.implicitRelativePath" was used.
changelog_1123_li=MVStore\:an IndexOutOfBoundsException could sometimes occur MVMap.openVersion when concurrently accessing the store.
changelog_1124_li=Windows\:using a base directory of "C\:/" and similar did not work as expected.
changelog_1124_li=The LIRS cache now re-sizes the internal hash map if needed.
changelog_1125_li=Follow JDBC specification on Procedures MetaData, use P0 as return type of procedure.
changelog_1125_li=Optionally persist session history in the H2 console. (patch from Martin Grajcar)
changelog_1126_li=Issue 531\:IDENTITY ignored for added column.
changelog_1126_li=Add client-info property to get the number of servers currently in the cluster and which servers that are available. (patch from Nikolaj Fogh)
changelog_1127_li=FileSystem\:improve exception throwing compatibility with JDK
changelog_1127_li=Fix bug in changing encrypted DB password that kept the file handle open when the wrong password was supplied. (test case from Jens Hohmuth).
changelog_1128_li=Spatial Index\:adjust costs so we do not use the spatial index if the query does not contain an intersects operator.
changelog_1128_li=Issue 567\:H2 hangs for a long time then (sometimes) recovers. Introduce a queue when doing table locking to prevent session starvation.
changelog_1129_li=Fix multi-threaded deadlock when using a View that includes a TableFunction.
changelog_1131_li=Issue 565\:MVStore\:concurrently adding LOB objects (with MULTI_THREADED option) resulted in a NullPointerException.
changelog_1132_li=Issue 559\:Make dependency on org.osgi.service.jdbc optional.
changelog_1132_li=MVStore\:reduced dependencies to other H2 classes.
changelog_1133_li=Improve error message when the user specifies an unsupported combination of database settings.
changelog_1133_li=There was a way to prevent a database from being re-opened, by creating a column constraint that references a table with a higher id, for example with "check" constraints that contains queries. This is now detected, and creating the table is prohibited. In future versions of H2, most likely creating references to other tables will no longer be supported because of such problems.
changelog_1134_li=MVStore\:in the multi-threaded mode, NullPointerException and other exceptions could occur.
changelog_1134_li=MVStore\:descending indexes with "nulls first" did not work as expected (null was ordered last).
changelog_1135_li=MVStore\:some database file could not be compacted due to a bug in the bookkeeping of the fill rate. Also, database file were compacted quite slowly. This has been improved; but more changes in this area are expected.
changelog_1135_li=Large result sets now always create temporary tables instead of temporary files.
changelog_1136_li=MVStore\:support for volatile maps (that don't store changes).
changelog_1136_li=When using the PageStore, opening a database failed in some cases with a NullPointerException if temporary tables were used (explicitly, or implicitly when using large result sets).
changelog_1137_li=MVStore mode\:in-memory databases now also use the MVStore.
changelog_1137_li=If a database file in the PageStore file format exists, this file and this mode is now used, even if the database URL does not contain "MV_STORE\=FALSE". If a MVStore file exists, it is used.
changelog_1138_li=In server mode, appending ";autocommit\=false" to the database URL was working, but the return value of Connection.getAutoCommit() was wrong.
changelog_1138_li=Databases created with version 1.3.175 and earlier that contained foreign keys in combination with multi-column indexes could not be opened in some cases. This was due to a bugfix in version 1.3.176\:Referential integrity constraints sometimes used the wrong index.
changelog_1139_li=Issue 561\:OSGi\:the import package declaration of org.h2 excluded version 1.4.
changelog_1139_li=MVStore\:the ObjectDataType comparison method was incorrect if one key was Serializable and the other was of a common class.
changelog_1140_li=Issue 558\:with the MVStore, a NullPointerException could occur when using LOBs at session commit (LobStorageMap.removeLob).
changelog_1140_li=Recursive queries with many result rows (more than the setting "max_memory_rows") did not work correctly.
changelog_1141_li=Remove the "h2.MAX_MEMORY_ROWS_DISTINCT" system property to reduce confusion. We already have the MAX_MEMORY_ROWS setting which does a very similar thing, and is better documented.
changelog_1141_li=The license has changed to MPL 2.0 + EPL 1.0.
changelog_1142_li=Issue 554\:Web Console in an IFrame was not fully supported.
changelog_1142_li=MVStore\:temporary tables from result sets could survive re-opening a database, which could result in a ClassCastException.
changelog_1143_li=Issue 566\:MVStore\:unique indexes that were created later on did not work correctly if there were over 5000 rows in the table. Existing databases need to be re-created (at least the broken index need to be re-built).
changelog_1144_li=By default, the MV_STORE option is enabled, so it is using the new MVStore storage. The MVCC setting is by default set to the same values as the MV_STORE setting, so it is also enabled by default. For testing, both settings can be disabled by appending ";MV_STORE\=FALSE" and/or ";MVCC\=FALSE" to the database URL.
changelog_1144_li=MVStore\:creating secondary indexes on large tables results in missing rows in the index.
changelog_1145_li=The file locking method 'serialized' is no longer supported. This mode might return in a future version, however this is not clear right now. A new implementation and new tests would be needed.
changelog_1145_li=Metadata\:the password of linked tables is now only visible for admin users.
changelog_1146_li=Enable the new storage format for dates (system property "h2.storeLocalTime"). For the MVStore mode, this is always enabled, but with version 1.4 this is even enabled in the PageStore mode.
changelog_1146_li=For Windows, database URLs of the form "jdbc\:h2\:/test" where considered relative and did not work unless the system property "h2.implicitRelativePath" was used.
changelog_1147_li=Implicit relative paths are disabled (system property "h2.implicitRelativePath"), so that the database URL jdbc\:h2\:test now needs to be written as jdbc\:h2\:./test.
changelog_1147_li=Windows\:using a base directory of "C\:/" and similar did not work as expected.
changelog_1148_li="select ... fetch first 1 row only"is supported with the regular mode. This was disabled so far because "fetch" and "offset" are now keywords. See also Mode.supportOffsetFetch.
changelog_1148_li=Follow JDBC specification on Procedures MetaData, use P0 as return type of procedure.
changelog_1149_li=Byte arrays are now sorted in unsigned mode (x'99' is larger than x'09'). (System property "h2.sortBinaryUnsigned", Mode.binaryUnsigned, setting "binary_collation").
changelog_1149_li=Issue 531\:IDENTITY ignored for added column.
changelog_1150_li=Csv.getInstance will be removed in future versions of 1.4. Use the public constructor instead.
changelog_1150_li=FileSystem\:improve exception throwing compatibility with JDK
changelog_1151_li=Remove support for the limited old-style outer join syntax using "(+)". Use "outer join" instead. System property "h2.oldStyleOuterJoin".
changelog_1151_li=Spatial Index\:adjust costs so we do not use the spatial index if the query does not contain an intersects operator.
changelog_1152_li=Support the data type "DATETIME2" as an alias for "DATETIME", for MS SQL Server compatibility.
changelog_1152_li=Fix multi-threaded deadlock when using a View that includes a TableFunction.
changelog_1153_li=Add Oracle-compatible TRANSLATE function, patch by Eric Chatellier.
changelog_1153_li=Fix bug in dividing very-small BigDecimal numbers.
changelog_1155_li=The file locking method 'serialized' is no longer documented, as it will not be available in version 1.4.
changelog_1155_li=Issue 559\:Make dependency on org.osgi.service.jdbc optional.
changelog_1156_li=The static method Csv.getInstance() was removed. Use the public constructor instead.
changelog_1156_li=Improve error message when the user specifies an unsupported combination of database settings.
changelog_1157_li=The default user name for the Script, RunScript, Shell, and CreateCluster tools are no longer "sa" but an empty string.
changelog_1157_li=MVStore\:in the multi-threaded mode, NullPointerException and other exceptions could occur.
changelog_1158_li=The stack trace of the exception "The object is already closed" is no longer logged by default.
changelog_1158_li=MVStore\:some database file could not be compacted due to a bug in the bookkeeping of the fill rate. Also, database file were compacted quite slowly. This has been improved; but more changes in this area are expected.
changelog_1159_li=If a value of a result set was itself a result set, the result could only be read once.
changelog_1159_li=MVStore\:support for volatile maps (that don't store changes).
changelog_1160_li=Column constraints are also visible in views (patch from Nicolas Fortin for H2GIS).
changelog_1160_li=MVStore mode\:in-memory databases now also use the MVStore.
changelog_1161_li=Granting a additional right to a role that already had a right for that table was not working.
changelog_1161_li=In server mode, appending ";autocommit\=false" to the database URL was working, but the return value of Connection.getAutoCommit() was wrong.
changelog_1162_li=Spatial index\:a few bugs have been fixed (using spatial constraints in views, transferring geometry objects over TCP/IP, the returned geometry object is copied when needed).
changelog_1162_li=Issue 561\:OSGi\:the import package declaration of org.h2 excluded version 1.4.
changelog_1163_li=Issue 551\:the datatype documentation was incorrect (found by Bernd Eckenfels).
changelog_1163_li=Issue 558\:with the MVStore, a NullPointerException could occur when using LOBs at session commit (LobStorageMap.removeLob).
changelog_1164_li=Issue 368\:ON DUPLICATE KEY UPDATE did not work for multi-row inserts. Test case from Angus Macdonald.
changelog_1164_li=Remove the "h2.MAX_MEMORY_ROWS_DISTINCT" system property to reduce confusion. We already have the MAX_MEMORY_ROWS setting which does a very similar thing, and is better documented.
changelog_1165_li=OSGi\:the package javax.tools is now imported (as an optional).
changelog_1165_li=Issue 554\:Web Console in an IFrame was not fully supported.
changelog_1166_li=H2 Console\:auto-complete is now disabled by default, but there is a hot-key (Ctrl+Space).
changelog_1167_li=H2 Console\:auto-complete did not work with multi-line statements.
changelog_1167_li=By default, the MV_STORE option is enabled, so it is using the new MVStore storage. The MVCC setting is by default set to the same values as the MV_STORE setting, so it is also enabled by default. For testing, both settings can be disabled by appending ";MV_STORE\=FALSE" and/or ";MVCC\=FALSE" to the database URL.
changelog_1168_li=CLOB and BLOB data was not immediately removed after a rollback.
changelog_1168_li=The file locking method 'serialized' is no longer supported. This mode might return in a future version, however this is not clear right now. A new implementation and new tests would be needed.
changelog_1169_li=There is a new Aggregate API that supports the internal H2 data types (GEOMETRY for example). Thanks a lot to Nicolas Fortin for the patch\!
changelog_1169_li=Enable the new storage format for dates (system property "h2.storeLocalTime"). For the MVStore mode, this is always enabled, but with version 1.4 this is even enabled in the PageStore mode.
changelog_1170_li=Referential integrity constraints sometimes used the wrong index, such that updating a row in the referenced table incorrectly failed with a constraint violation.
changelog_1170_li=Implicit relative paths are disabled (system property "h2.implicitRelativePath"), so that the database URL jdbc\:h2\:test now needs to be written as jdbc\:h2\:./test.
changelog_1171_li=The Polish translation was completed and corrected by Wojtek Jurczyk. Thanks a lot\!
changelog_1171_li="select ... fetch first 1 row only"is supported with the regular mode. This was disabled so far because "fetch" and "offset" are now keywords. See also Mode.supportOffsetFetch.
changelog_1172_li=Issue 545\:Unnecessary duplicate code was removed.
changelog_1172_li=Byte arrays are now sorted in unsigned mode (x'99' is larger than x'09'). (System property "h2.sortBinaryUnsigned", Mode.binaryUnsigned, setting "binary_collation").
changelog_1173_li=The profiler tool can now process files with full thread dumps.
changelog_1173_li=Csv.getInstance will be removed in future versions of 1.4. Use the public constructor instead.
changelog_1174_li=MVStore\:the file format was changed slightly.
changelog_1174_li=Remove support for the limited old-style outer join syntax using "(+)". Use "outer join" instead. System property "h2.oldStyleOuterJoin".
changelog_1175_li=MVStore mode\:the CLOB and BLOB storage was re-implemented and is now much faster than with the PageStore (which is still the default storage).
changelog_1175_li=Support the data type "DATETIME2" as an alias for "DATETIME", for MS SQL Server compatibility.
changelog_1176_li=MVStore mode\:creating indexes is now much faster (in many cases faster than with the default PageStore).
changelog_1176_li=Add Oracle-compatible TRANSLATE function, patch by Eric Chatellier.
changelog_1177_li=Various bugs in the MVStore storage and have been fixed, including a bug in the R-tree implementation. The database could get corrupt if there were transient IO exceptions while storing.
changelog_1177_h2=Version 1.3.176 (2014-04-05)
changelog_1178_li=The method org.h2.expression.Function.getCost could throw a NullPointException.
changelog_1178_li=The file locking method 'serialized' is no longer documented, as it will not be available in version 1.4.
changelog_1179_li=Storing LOBs in separate files (outside of the main database file) is no longer supported for new databases.
changelog_1179_li=The static method Csv.getInstance() was removed. Use the public constructor instead.
changelog_1180_li=Lucene 2 is no longer supported.
changelog_1180_li=The default user name for the Script, RunScript, Shell, and CreateCluster tools are no longer "sa" but an empty string.
changelog_1181_li=Fix bug in calculating default MIN and MAX values for SEQUENCE.
changelog_1181_li=The stack trace of the exception "The object is already closed" is no longer logged by default.
changelog_1182_li=Fix bug in performing IN queries with multiple values when IGNORECASE\=TRUE
changelog_1182_li=If a value of a result set was itself a result set, the result could only be read once.
changelog_1183_li=Add entry-point to org.h2.tools.Shell so it can be called from inside an application. patch by Thomas Gillet.
changelog_1183_li=Column constraints are also visible in views (patch from Nicolas Fortin for H2GIS).
changelog_1184_li=Fix bug that prevented the PgServer from being stopped and started multiple times.
changelog_1184_li=Granting a additional right to a role that already had a right for that table was not working.
changelog_1185_li=Support some more DDL syntax for MySQL, patch from Peter Jentsch.
changelog_1185_li=Spatial index\:a few bugs have been fixed (using spatial constraints in views, transferring geometry objects over TCP/IP, the returned geometry object is copied when needed).
changelog_1186_li=Issue 548\:TO_CHAR does not format MM and DD correctly when the month or day of the month is 1 digit, patch from "the.tucc"
changelog_1186_li=Issue 551\:the datatype documentation was incorrect (found by Bernd Eckenfels).
changelog_1187_li=Fix bug in varargs support in ALIAS's, patch from Nicolas Fortin
changelog_1187_li=Issue 368\:ON DUPLICATE KEY UPDATE did not work for multi-row inserts. Test case from Angus Macdonald.
changelog_1188_li=OSGi\:the package javax.tools is now imported (as an optional).
changelog_1189_li=H2 Console\:auto-complete is now disabled by default, but there is a hot-key (Ctrl+Space).
changelog_1190_li=H2 Console\:auto-complete did not work with multi-line statements.
changelog_1191_li=CLOB and BLOB data was not immediately removed after a rollback.
changelog_1192_li=There is a new Aggregate API that supports the internal H2 data types (GEOMETRY for example). Thanks a lot to Nicolas Fortin for the patch\!
changelog_1193_li=Referential integrity constraints sometimes used the wrong index, such that updating a row in the referenced table incorrectly failed with a constraint violation.
changelog_1194_li=The Polish translation was completed and corrected by Wojtek Jurczyk. Thanks a lot\!
changelog_1195_li=Issue 545\:Unnecessary duplicate code was removed.
changelog_1196_li=The profiler tool can now process files with full thread dumps.
changelog_1197_li=MVStore\:the file format was changed slightly.
changelog_1198_li=MVStore mode\:the CLOB and BLOB storage was re-implemented and is now much faster than with the PageStore (which is still the default storage).
changelog_1199_li=MVStore mode\:creating indexes is now much faster (in many cases faster than with the default PageStore).
changelog_1200_li=Various bugs in the MVStore storage and have been fixed, including a bug in the R-tree implementation. The database could get corrupt if there were transient IO exceptions while storing.
changelog_1201_li=The method org.h2.expression.Function.getCost could throw a NullPointException.
changelog_1202_li=Storing LOBs in separate files (outside of the main database file) is no longer supported for new databases.
changelog_1203_li=Lucene 2 is no longer supported.
changelog_1204_li=Fix bug in calculating default MIN and MAX values for SEQUENCE.
changelog_1205_li=Fix bug in performing IN queries with multiple values when IGNORECASE\=TRUE
changelog_1206_li=Add entry-point to org.h2.tools.Shell so it can be called from inside an application. patch by Thomas Gillet.
changelog_1207_li=Fix bug that prevented the PgServer from being stopped and started multiple times.
changelog_1208_li=Support some more DDL syntax for MySQL, patch from Peter Jentsch.
changelog_1209_li=Issue 548\:TO_CHAR does not format MM and DD correctly when the month or day of the month is 1 digit, patch from "the.tucc"
changelog_1210_li=Fix bug in varargs support in ALIAS's, patch from Nicolas Fortin
cheatSheet_1000_h1=H2 Database Engine Cheat Sheet
cheatSheet_1000_h1=H2 Database Engine Cheat Sheet
cheatSheet_1001_h2=Using H2
cheatSheet_1001_h2=Using H2
cheatSheet_1002_a=H2
cheatSheet_1002_a=H2
...
@@ -3579,10 +3602,11 @@ roadmap_1506_li=Sybase SQL Anywhere compatibility\: SELECT TOP ... START AT ...
...
@@ -3579,10 +3602,11 @@ roadmap_1506_li=Sybase SQL Anywhere compatibility\: SELECT TOP ... START AT ...
roadmap_1510_li=Support index-only when doing selects (i.e. without needing to load the actual table data)
roadmap_1511_li=HSQLDB (did) support this\:select id i from test where i<0 (other databases don't). Supporting it may break compatibility.
roadmap_1511_h2=Not Planned
roadmap_1512_li=String.intern (so that Strings can be compared with \=\=) will not be used because some VMs have problems when used extensively.
roadmap_1512_li=HSQLDB (did) support this\:select id i from test where i<0 (other databases don't). Supporting it may break compatibility.
roadmap_1513_li=In prepared statements, identifier names (table names and so on) can not be parameterized. Adding such a feature would complicate the source code without providing reasonable speedup, and would slow down regular prepared statements.
roadmap_1513_li=String.intern (so that Strings can be compared with \=\=) will not be used because some VMs have problems when used extensively.
roadmap_1514_li=In prepared statements, identifier names (table names and so on) can not be parameterized. Adding such a feature would complicate the source code without providing reasonable speedup, and would slow down regular prepared statements.
