@@ -1202,7 +1202,7 @@ The maximum file size for FAT or FAT32 file systems is 4 GB. That means when usi
...
@@ -1202,7 +1202,7 @@ The maximum file size for FAT or FAT32 file systems is 4 GB. That means when usi
The maximum number of rows per table is 2^64.
The maximum number of rows per table is 2^64.
@advanced_1401_li
@advanced_1401_li
Main memory requirements: The larger the database, the more main memory is required. With the version 1.1 storage mechanism, the minimum main memory required for a 12 GB database was around 240 MB. With the current page store, the minimum main memory required is much lower, around 1 MB for each 8 GB database file size.
Main memory requirements: The larger the database, the more main memory is required. With the current storage mechanism (the page store), the minimum main memory required is around 1 MB for each 8 GB database file size.
@advanced_1402_li
@advanced_1402_li
Limit on the complexity of SQL statements. Statements of the following form will result in a stack overflow exception:
Limit on the complexity of SQL statements. Statements of the following form will result in a stack overflow exception:
...
@@ -1658,555 +1658,567 @@ For in-memory databases, creating an index on a CLOB or BLOB column is no longer
...
@@ -1658,555 +1658,567 @@ For in-memory databases, creating an index on a CLOB or BLOB column is no longer
New column "information_schema.tables.row_count_estimate".
New column "information_schema.tables.row_count_estimate".
@changelog_1007_li
@changelog_1007_li
Issue 468: trunc(timestamp) could return the wrong value.
Issue 468: trunc(timestamp) could return the wrong value (+12 hours), and trunc(number) throw a NullPointerException.
@changelog_1008_li
@changelog_1008_li
Fixed a deadlock when updating LOB's concurrently. See TestLob.testDeadlock2().
The expression trunc(number) threw a NullPointerException.
@changelog_1009_li
@changelog_1009_li
Fixed a deadlock related to very large temporary result sets.
Fixed a deadlock when updating LOB's concurrently. See TestLob.testDeadlock2().
@changelog_1010_li
@changelog_1010_li
Add "-list" command line option to Shell tool so that result-list-mode can be triggered when reading from a file.
Fixed a deadlock related to very large temporary result sets.
@changelog_1011_li
@changelog_1011_li
Issue 474: H2 Mysql Compatibility code fails to ignore "COMMENT" in CREATE TABLE, patch from Aaron Azeckoski.
Add "-list" command line option to Shell tool so that result-list-mode can be triggered when reading from a file.
@changelog_1012_li
@changelog_1012_li
Issue 476: Broken link in jaqu.html
Issue 474: H2 MySQL Compatibility code fails to ignore "COMMENT" in CREATE TABLE, patch from Aaron Azeckoski.
@changelog_1013_li
@changelog_1013_li
Fix potential UTF8 encoding issue in org.h2.store.FileStore, reported by Juerg Spiess.
Issue 476: Broken link in jaqu.html
@changelog_1014_li
@changelog_1014_li
Improve error message when check constraint is broken, test case from Gili (cowwoc).
Fix potential UTF8 encoding issue in org.h2.store.FileStore, reported by Juerg Spiess.
@changelog_1015_li
@changelog_1015_li
Improve error message when we have a unique constraint violation, displays the offending key in the error message.
Improve error message when check constraint is broken, test case from Gili (cowwoc).
@changelog_1016_li
@changelog_1016_li
Issue 478: Support for "SHOW TRANSACTION ISOLATION LEVEL", patch from Andrew Franklin.
Improve error message when we have a unique constraint violation, displays the offending key in the error message.
@changelog_1017_li
@changelog_1017_li
Issue 475: PgServer: add support for CancelRequest, patch from Andrew Franklin.
Issue 478: Support for "SHOW TRANSACTION ISOLATION LEVEL", patch from Andrew Franklin.
@changelog_1018_li
@changelog_1018_li
Issue 473: PgServer missing -key option, patch from Andrew Franklin.
Issue 475: PgServer: add support for CancelRequest, patch from Andrew Franklin.
@changelog_1019_li
@changelog_1019_li
Issue 471: CREATE VIEW does not check user rights, patch from Andrew Franklin.
Issue 473: PgServer missing -key option, patch from Andrew Franklin.
@changelog_1020_li
@changelog_1020_li
Issue 477: PgServer binary transmission of query params is unimplemented, patch from Andrew Franklin.
Issue 471: CREATE VIEW does not check user rights, patch from Andrew Franklin.
@changelog_1021_li
@changelog_1021_li
Issue 479: Support for SUBSTRING without a FROM condition, patch from Andrew Franklin.
Issue 477: PgServer binary transmission of query params is unimplemented, patch from Andrew Franklin.
@changelog_1022_li
@changelog_1022_li
Issue 472: PgServer does not work with any recent Postgres JDBC driver, patch from Andrew Franklin.
Issue 479: Support for SUBSTRING without a FROM condition, patch from Andrew Franklin.
@changelog_1023_li
@changelog_1023_li
Add syntax for passing additional parameters into custom TableEngine implementations.
Issue 472: PgServer does not work with any recent Postgres JDBC driver, patch from Andrew Franklin.
@changelog_1024_li
@changelog_1024_li
Issue 480: Bugfix post issue #475, #477, patch from Andrew Franklin.
Add syntax for passing additional parameters into custom TableEngine implementations.
@changelog_1025_li
@changelog_1025_li
Issue 481: Further extensions to PgServer to support better support PG JDBC, patch from Andrew Franklin.
Issue 480: Bugfix post issue 475, 477, patch from Andrew Franklin.
@changelog_1026_li
@changelog_1026_li
Add support for spatial datatype GEOMETRY.
Issue 481: Further extensions to PgServer to support better support PG JDBC, patch from Andrew Franklin.
@changelog_1027_li
@changelog_1027_li
Add support for in-memory spatial index.
Add support for spatial datatype GEOMETRY.
@changelog_1028_li
@changelog_1028_li
Add support for in-memory spatial index.
@changelog_1029_li
change the PageStore#changeCount field from an int to a long, to cope with databases with very high transaction rates.
change the PageStore#changeCount field from an int to a long, to cope with databases with very high transaction rates.
@changelog_1029_h2
@changelog_1030_li
Fix a NullPointerException when attempting to add foreign key reference to a view.
@changelog_1031_li
Add sufficient ClientInfo support to our javax.sql.Connection implementation to make WebSphere happy.
@changelog_1032_li
Issue 482: class LobStorageBackend$LobInputStream does not override the method InputStream.available().
@changelog_1033_h2
Version 1.3.172 (2013-05-25)
Version 1.3.172 (2013-05-25)
@changelog_1030_li
@changelog_1034_li
Referential integrity: when adding a referential integrity constraint failed, and if creating the constraint automatically created an index, this index was not removed.
Referential integrity: when adding a referential integrity constraint failed, and if creating the constraint automatically created an index, this index was not removed.
@changelog_1031_li
@changelog_1035_li
The auto-analyze feature now only reads 1000 rows per table instead of 10000.
The auto-analyze feature now only reads 1000 rows per table instead of 10000.
@changelog_1032_li
@changelog_1036_li
The optimization for IN(...) queries combined with OR could result in a strange exception of the type "column x must be included in the group by list".
The optimization for IN(...) queries combined with OR could result in a strange exception of the type "column x must be included in the group by list".
@changelog_1033_li
@changelog_1037_li
Issue 454: Use Charset for type-safety.
Issue 454: Use Charset for type-safety.
@changelog_1034_li
@changelog_1038_li
Queries with both LIMIT and OFFSET could throw an IllegalArgumentException.
Queries with both LIMIT and OFFSET could throw an IllegalArgumentException.
@changelog_1035_li
@changelog_1039_li
MVStore: multiple issues were fixed: 460, 461, 462, 464, 466.
MVStore: multiple issues were fixed: 460, 461, 462, 464, 466.
@changelog_1036_li
@changelog_1040_li
MVStore: larger stores (multiple GB) are now much faster.
MVStore: larger stores (multiple GB) are now much faster.
@changelog_1037_li
@changelog_1041_li
When using local temporary tables and not dropping them manually before closing the session, and then killing the process could result in a database that couldn't be opened (except when using the recover tool).
When using local temporary tables and not dropping them manually before closing the session, and then killing the process could result in a database that couldn't be opened (except when using the recover tool).
@changelog_1038_li
@changelog_1042_li
Support TRUNC(timestamp) for improved Oracle compatibility.
Support TRUNC(timestamp) for improved Oracle compatibility.
@changelog_1039_li
@changelog_1043_li
Add support for CREATE TABLE TEST (ID BIGSERIAL) for PostgreSQL compatibility. Patch from Jesse Long.
Add support for CREATE TABLE TEST (ID BIGSERIAL) for PostgreSQL compatibility. Patch from Jesse Long.
@changelog_1040_li
@changelog_1044_li
Add new collation command SET BINARY_COLLATION UNSIGNED, helps with people testing BINARY columns in MySQL mode.
Add new collation command SET BINARY_COLLATION UNSIGNED, helps with people testing BINARY columns in MySQL mode.
@changelog_1041_li
@changelog_1045_li
Issue 453: ABBA race conditions in TABLE LINK connection sharing.
Issue 453: ABBA race conditions in TABLE LINK connection sharing.
@changelog_1042_li
@changelog_1046_li
Issue 449: Postgres Serial data type should not automatically be marked as primary key
Issue 449: Postgres Serial data type should not automatically be marked as primary key
@changelog_1043_li
@changelog_1047_li
Issue 406: Support "select h2version()"
Issue 406: Support "select h2version()"
@changelog_1044_li
@changelog_1048_li
Issue 389: When there is a multi-column primary key, H2 does not seem to always pick the right index
Issue 389: When there is a multi-column primary key, H2 does not seem to always pick the right index
@changelog_1045_li
@changelog_1049_li
Issue 305: Implement SELECT ... FOR FETCH ONLY
Issue 305: Implement SELECT ... FOR FETCH ONLY
@changelog_1046_li
@changelog_1050_li
Issue 274: Sybase/MSSQLServer compatibility - Add GETDATE and CHARINDEX system functions
Issue 274: Sybase/MSSQLServer compatibility - Add GETDATE and CHARINDEX system functions
@changelog_1047_li
@changelog_1051_li
Issue 274: Sybase/MSSQLServer compatibility - swap parameters of CONVERT function.
Issue 274: Sybase/MSSQLServer compatibility - swap parameters of CONVERT function.
@changelog_1048_li
@changelog_1052_li
Issue 274: Sybase/MSSQLServer compatibility - support index clause e.g. "select * from test (index table1_index)"
Issue 274: Sybase/MSSQLServer compatibility - support index clause e.g. "select * from test (index table1_index)"
@changelog_1049_li
@changelog_1053_li
Fix bug in Optimizing SELECT * FROM A WHERE X=1 OR X=2 OR X=3 into SELECT * FROM A WHERE X IN (1,2,3)
Fix bug in Optimizing SELECT * FROM A WHERE X=1 OR X=2 OR X=3 into SELECT * FROM A WHERE X IN (1,2,3)
@changelog_1050_li
@changelog_1054_li
Issue 442: Groovy patch for SourceCompiler (function ALIAS)
Issue 442: Groovy patch for SourceCompiler (function ALIAS)
@changelog_1051_li
@changelog_1055_li
Issue 459: Improve LOB documentation
Issue 459: Improve LOB documentation
@changelog_1052_h2
@changelog_1056_h2
Version 1.3.171 (2013-03-17)
Version 1.3.171 (2013-03-17)
@changelog_1053_li
@changelog_1057_li
Security: the TCP server did not correctly restrict access rights of clients in some cases. This was specially a problem when using the flag "tcpAllowOthers".
Security: the TCP server did not correctly restrict access rights of clients in some cases. This was specially a problem when using the flag "tcpAllowOthers".
@changelog_1054_li
@changelog_1058_li
H2 Console: the session timeout can now be configured using the system property "h2.consoleTimeout".
H2 Console: the session timeout can now be configured using the system property "h2.consoleTimeout".
@changelog_1055_li
@changelog_1059_li
Issue 431: Improved compatibility with MySQL: support for "ENGINE=InnoDB charset=UTF8" when creating a table.
Issue 431: Improved compatibility with MySQL: support for "ENGINE=InnoDB charset=UTF8" when creating a table.
@changelog_1056_li
@changelog_1060_li
Issue 249: Improved compatibility with MySQL in the MySQL mode: now the methods DatabaseMetaData methods stores*Case*Identifiers return the same as MySQL when using the MySQL mode.
Issue 249: Improved compatibility with MySQL in the MySQL mode: now the methods DatabaseMetaData methods stores*Case*Identifiers return the same as MySQL when using the MySQL mode.
@changelog_1057_li
@changelog_1061_li
Issue 434: H2 Console didn't work in the Chrome browser due to a wrong viewport argument.
Issue 434: H2 Console didn't work in the Chrome browser due to a wrong viewport argument.
@changelog_1058_li
@changelog_1062_li
There was a possibility that the .lock.db file was not deleted when the database was closed, which could slow down opening the database.
There was a possibility that the .lock.db file was not deleted when the database was closed, which could slow down opening the database.
@changelog_1059_li
@changelog_1063_li
The SQL script generated by the "script" command contained inconsistent newlines on Windows.
The SQL script generated by the "script" command contained inconsistent newlines on Windows.
@changelog_1060_li
@changelog_1064_li
When using trace level 4 (SLF4J) in the server mode, a directory "trace.db" and an empty file was created on the client side. This is no longer made.
When using trace level 4 (SLF4J) in the server mode, a directory "trace.db" and an empty file was created on the client side. This is no longer made.
@changelog_1061_li
@changelog_1065_li
Optimize IN(...) queries: there was a bug in version 1.3.170 if the type of the left hand side didn't match the type of the right hand side. Fixed.
Optimize IN(...) queries: there was a bug in version 1.3.170 if the type of the left hand side didn't match the type of the right hand side. Fixed.
@changelog_1062_li
@changelog_1066_li
Optimize IN(...) queries: there was a bug in version 1.3.170 for comparison of the type "X IN(NULL, NULL)". Fixed.
Optimize IN(...) queries: there was a bug in version 1.3.170 for comparison of the type "X IN(NULL, NULL)". Fixed.
@changelog_1063_li
@changelog_1067_li
Timestamps with timezone that were passed as a string were not always converted correctly. For example "2012-11-06T23:00:00.000Z" was converted to "2012-11-06" instead of to "2012-11-07" in the timezone CET. Thanks a lot to Steve Hruda for reporting the problem!
Timestamps with timezone that were passed as a string were not always converted correctly. For example "2012-11-06T23:00:00.000Z" was converted to "2012-11-06" instead of to "2012-11-07" in the timezone CET. Thanks a lot to Steve Hruda for reporting the problem!
@changelog_1064_li
@changelog_1068_li
New table engine "org.h2.mvstore.db.MVTableEngine" that internally uses the MVStore to persist data. To try it out, append ";DEFAULT_TABLE_ENGINE=org.h2.mvstore.db.MVTableEngine" to the database URL. This is still very experimental, and many features are not supported yet. The data is stored in a file with the suffix ".mv.db".
New table engine "org.h2.mvstore.db.MVTableEngine" that internally uses the MVStore to persist data. To try it out, append ";DEFAULT_TABLE_ENGINE=org.h2.mvstore.db.MVTableEngine" to the database URL. This is still very experimental, and many features are not supported yet. The data is stored in a file with the suffix ".mv.db".
@changelog_1065_li
@changelog_1069_li
New connection setting "DEFAULT_TABLE_ENGINE" to use a specific table engine if none is set explicitly. This is to simplify testing the MVStore table engine.
New connection setting "DEFAULT_TABLE_ENGINE" to use a specific table engine if none is set explicitly. This is to simplify testing the MVStore table engine.
@changelog_1066_li
@changelog_1070_li
MVStore: encrypted stores are now supported. Only standardized algorithms are used: PBKDF2, SHA-256, XTS-AES, AES-128.
MVStore: encrypted stores are now supported. Only standardized algorithms are used: PBKDF2, SHA-256, XTS-AES, AES-128.
@changelog_1067_li
@changelog_1071_li
MVStore: improved API thanks to Simo Tripodi.
MVStore: improved API thanks to Simo Tripodi.
@changelog_1068_li
@changelog_1072_li
MVStore: maps can now be renamed.
MVStore: maps can now be renamed.
@changelog_1069_li
@changelog_1073_li
MVStore: store the file header also at the end of each chunk, which results in a further reduced number of write operations.
MVStore: store the file header also at the end of each chunk, which results in a further reduced number of write operations.
@changelog_1070_li
@changelog_1074_li
MVStore: a map implementation that supports concurrent operations.
MVStore: a map implementation that supports concurrent operations.
@changelog_1071_li
@changelog_1075_li
MVStore: unified exception handling; the version is included in the messages.
MVStore: unified exception handling; the version is included in the messages.
@changelog_1072_li
@changelog_1076_li
MVStore: old data is now retained for 45 seconds by default.
MVStore: old data is now retained for 45 seconds by default.
@changelog_1073_li
@changelog_1077_li
MVStore: compress is now disabled by default, and can be enabled on request.
MVStore: compress is now disabled by default, and can be enabled on request.
@changelog_1074_li
@changelog_1078_li
Support ALTER TABLE ADD ... AFTER. Patch from Andrew Gaul (argaul at gmail.com). Fixes issue 401.
Support ALTER TABLE ADD ... AFTER. Patch from Andrew Gaul (argaul at gmail.com). Fixes issue 401.
@changelog_1075_li
@changelog_1079_li
Improved OSGi support. H2 now registers itself as a DataSourceFactory service. Fixes issue 365.
Improved OSGi support. H2 now registers itself as a DataSourceFactory service. Fixes issue 365.
@changelog_1076_li
@changelog_1080_li
Add a DISK_SPACE_USED system function. Fixes issue 270.
Add a DISK_SPACE_USED system function. Fixes issue 270.
@changelog_1077_li
@changelog_1081_li
Fix a compile-time ambiguity when compiling with JDK7, thanks to a patch from Lukas Eder.
Fix a compile-time ambiguity when compiling with JDK7, thanks to a patch from Lukas Eder.
@changelog_1078_li
@changelog_1082_li
Supporting dropping an index for Lucene full-text indexes.
Supporting dropping an index for Lucene full-text indexes.
@changelog_1079_li
@changelog_1083_li
Optimized performance for SELECT ... ORDER BY X LIMIT Y OFFSET Z queries for in-memory databases using partial sort (by Sergi Vladykin).
Optimized performance for SELECT ... ORDER BY X LIMIT Y OFFSET Z queries for in-memory databases using partial sort (by Sergi Vladykin).
@changelog_1080_li
@changelog_1084_li
Experimental off-heap memory storage engine "nioMemFS:" and "nioMemLZF:", suggestion from Mark Addleman.
Experimental off-heap memory storage engine "nioMemFS:" and "nioMemLZF:", suggestion from Mark Addleman.
@changelog_1081_li
@changelog_1085_li
Issue 438: JdbcDatabaseMetaData.getSchemas() is no longer supported as of 1.3.169.
Issue 438: JdbcDatabaseMetaData.getSchemas() is no longer supported as of 1.3.169.
@changelog_1082_li
@changelog_1086_li
MySQL compatibility: support for ALTER TABLE tableName MODIFY [COLUMN] columnName columnDef. Patch from Ville Koskela.
MySQL compatibility: support for ALTER TABLE tableName MODIFY [COLUMN] columnName columnDef. Patch from Ville Koskela.
@changelog_1083_li
@changelog_1087_li
Issue 404: SHOW COLUMNS FROM tableName does not work with ALLOW_LITERALS=NUMBERS.
Issue 404: SHOW COLUMNS FROM tableName does not work with ALLOW_LITERALS=NUMBERS.
@changelog_1084_li
@changelog_1088_li
Throw an explicit error to make it clear we don't support the TRIGGER combination of SELECT and FOR EACH ROW.
Throw an explicit error to make it clear we don't support the TRIGGER combination of SELECT and FOR EACH ROW.
@changelog_1085_li
@changelog_1089_li
Issue 439: Utils.sortTopN does not handle single-element arrays.
Issue 439: Utils.sortTopN does not handle single-element arrays.
@changelog_1086_h2
@changelog_1090_h2
Version 1.3.170 (2012-11-30)
Version 1.3.170 (2012-11-30)
@changelog_1087_li
@changelog_1091_li
Issue 407: The TriggerAdapter didn't work with CLOB and BLOB columns.
Issue 407: The TriggerAdapter didn't work with CLOB and BLOB columns.
@changelog_1088_li
@changelog_1092_li
PostgreSQL compatibility: support for data types BIGSERIAL and SERIAL as an alias for AUTO_INCREMENT.
PostgreSQL compatibility: support for data types BIGSERIAL and SERIAL as an alias for AUTO_INCREMENT.
@changelog_1089_li
@changelog_1093_li
Issue 417: H2 Console: the web session timeout didn't work, resulting in a memory leak. This was only a problem if the H2 Console was run for a long time and many sessions were opened.
Issue 417: H2 Console: the web session timeout didn't work, resulting in a memory leak. This was only a problem if the H2 Console was run for a long time and many sessions were opened.
@changelog_1090_li
@changelog_1094_li
Issue 412: Running the Server tool with just the option "-browser" will now log a warning.
Issue 412: Running the Server tool with just the option "-browser" will now log a warning.
@changelog_1091_li
@changelog_1095_li
Issue 411: CloseWatcher registration was not concurrency-safe.
Issue 411: CloseWatcher registration was not concurrency-safe.
@changelog_1092_li
@changelog_1096_li
MySQL compatibility: support for CONCAT_WS. Thanks a lot to litailang for the patch!
MySQL compatibility: support for CONCAT_WS. Thanks a lot to litailang for the patch!
@changelog_1093_li
@changelog_1097_li
PostgreSQL compatibility: support for EXTRACT(WEEK FROM dateColumn). Thanks to Prashant Bhat for the patch!
PostgreSQL compatibility: support for EXTRACT(WEEK FROM dateColumn). Thanks to Prashant Bhat for the patch!
@changelog_1094_li
@changelog_1098_li
Fix for a bug where we would sometimes use the wrong unique constraint to validate foreign key constraints.
Fix for a bug where we would sometimes use the wrong unique constraint to validate foreign key constraints.
@changelog_1095_li
@changelog_1099_li
Support BOM at the beginning of files for the RUNSCRIPT command
Support BOM at the beginning of files for the RUNSCRIPT command
@changelog_1096_li
@changelog_1100_li
Fix in calling SET @X = IDENTITY() where it would return NULL incorrectly
Fix in calling SET @X = IDENTITY() where it would return NULL incorrectly
@changelog_1097_li
@changelog_1101_li
Fix ABBA deadlock between adding a constraint and the H2-Log-Writer thread.
Fix ABBA deadlock between adding a constraint and the H2-Log-Writer thread.
@changelog_1098_li
@changelog_1102_li
Optimize IN(...) queries where the values are constant and of the same type.
Optimize IN(...) queries where the values are constant and of the same type.
@changelog_1099_li
@changelog_1103_li
Restore tool: the parameter "quiet" was not used and is now removed.
Restore tool: the parameter "quiet" was not used and is now removed.
@changelog_1100_li
@changelog_1104_li
Fix ConcurrentModificationException when creating tables and executing SHOW TABLES in parallel. Reported by Viktor Voytovych.
Fix ConcurrentModificationException when creating tables and executing SHOW TABLES in parallel. Reported by Viktor Voytovych.
@changelog_1101_li
@changelog_1105_li
Serialization is now pluggable using the system property "h2.javaObjectSerializer". Thanks to Sergi Vladykin for the patch!
Serialization is now pluggable using the system property "h2.javaObjectSerializer". Thanks to Sergi Vladykin for the patch!
@changelog_1102_h2
@changelog_1106_h2
Version 1.3.169 (2012-09-09)
Version 1.3.169 (2012-09-09)
@changelog_1103_li
@changelog_1107_li
The default jar file is now compiled for Java 6.
The default jar file is now compiled for Java 6.
@changelog_1104_li
@changelog_1108_li
The new jar file will probably not end up in the central Maven repository in the next few weeks because Sonatype has disabled automatic synchronization from SourceForge (which they call 'legacy sync' now). It will probably take some time until this is sorted out. The H2 jar files are deployed to http://h2database.com/m2-repo/com/h2database/h2/maven-metadata.xml and http://hsql.sourceforge.net/m2-repo/com/h2database/h2/maven-metadata.xml as usual.
The new jar file will probably not end up in the central Maven repository in the next few weeks because Sonatype has disabled automatic synchronization from SourceForge (which they call 'legacy sync' now). It will probably take some time until this is sorted out. The H2 jar files are deployed to http://h2database.com/m2-repo/com/h2database/h2/maven-metadata.xml and http://hsql.sourceforge.net/m2-repo/com/h2database/h2/maven-metadata.xml as usual.
@changelog_1105_li
@changelog_1109_li
A part of the documentation and the H2 Console has been changed to support the Apple retina display.
A part of the documentation and the H2 Console has been changed to support the Apple retina display.
@changelog_1106_li
@changelog_1110_li
The CreateCluster tool could not be used if the source database contained a CLOB or BLOB. The root cause was that the TCP server did not synchronize on the session, which caused a problem when using the exclusive mode.
The CreateCluster tool could not be used if the source database contained a CLOB or BLOB. The root cause was that the TCP server did not synchronize on the session, which caused a problem when using the exclusive mode.
@changelog_1107_li
@changelog_1111_li
Statement.getQueryTimeout(): only the first call to this method will query the database. If the query timeout was changed in another way than calling setQueryTimeout, this method will always return the last value. This was changed because Hibernate calls getQueryTimeout() a lot.
Statement.getQueryTimeout(): only the first call to this method will query the database. If the query timeout was changed in another way than calling setQueryTimeout, this method will always return the last value. This was changed because Hibernate calls getQueryTimeout() a lot.
@changelog_1108_li
@changelog_1112_li
Issue 416: PreparedStatement.setNString throws AbstractMethodError. All implemented JDBC 4 methods that don't break compatibility with Java 5 are now included in the default jar file.
Issue 416: PreparedStatement.setNString throws AbstractMethodError. All implemented JDBC 4 methods that don't break compatibility with Java 5 are now included in the default jar file.
@changelog_1109_li
@changelog_1113_li
Issue 414: for some functions, the parameters were evaluated twice (for example "char(nextval(..))" ran "nextval(..)" twice).
Issue 414: for some functions, the parameters were evaluated twice (for example "char(nextval(..))" ran "nextval(..)" twice).
@changelog_1110_li
@changelog_1114_li
The ResultSetMetaData methods getSchemaName and getTableName could return null instead of "" (an empty string) as specified in the JDBC API.
The ResultSetMetaData methods getSchemaName and getTableName could return null instead of "" (an empty string) as specified in the JDBC API.
@changelog_1111_li
@changelog_1115_li
Added compatibility for "SET NAMES" query in MySQL compatibility mode.
Added compatibility for "SET NAMES" query in MySQL compatibility mode.
@changelog_1112_h2
@changelog_1116_h2
Version 1.3.168 (2012-07-13)
Version 1.3.168 (2012-07-13)
@changelog_1113_li
@changelog_1117_li
The message "Transaction log could not be truncated" was sometimes written to the .trace.db file even if there was no problem truncating the transaction log.
The message "Transaction log could not be truncated" was sometimes written to the .trace.db file even if there was no problem truncating the transaction log.
@changelog_1114_li
@changelog_1118_li
New system property "h2.serializeJavaObject" (default: true) that allows to disable serializing Java objects, so that the objects compareTo and toString methods can be used.
New system property "h2.serializeJavaObject" (default: true) that allows to disable serializing Java objects, so that the objects compareTo and toString methods can be used.
@changelog_1115_li
@changelog_1119_li
Dylan has translated the H2 Console tool to Korean. Thanks a lot!
Dylan has translated the H2 Console tool to Korean. Thanks a lot!
@changelog_1116_li
@changelog_1120_li
Executing the statement CREATE INDEX IF ALREADY EXISTS if the index already exists no longer fails for a read only database.
Executing the statement CREATE INDEX IF ALREADY EXISTS if the index already exists no longer fails for a read only database.
@changelog_1117_li
@changelog_1121_li
MVCC: concurrently updating a row could result in the row to appear deleted in the second connection, if there are multiple unique indexes (or a primary key and at least one unique index). Thanks a lot to Teruo for the patch!
MVCC: concurrently updating a row could result in the row to appear deleted in the second connection, if there are multiple unique indexes (or a primary key and at least one unique index). Thanks a lot to Teruo for the patch!
@changelog_1118_li
@changelog_1122_li
Fulltext search: in-memory Lucene indexes are now supported.
Fulltext search: in-memory Lucene indexes are now supported.
@changelog_1119_li
@changelog_1123_li
Fulltext search: UUID primary keys are now supported.
Fulltext search: UUID primary keys are now supported.
@changelog_1120_li
@changelog_1124_li
Apache Tomcat 7.x will now longer log a warning when unloading the web application, if using a connection pool.
Apache Tomcat 7.x will now longer log a warning when unloading the web application, if using a connection pool.
@changelog_1121_li
@changelog_1125_li
H2 Console: support the Midori browser (for Debian / Raspberry Pi)
H2 Console: support the Midori browser (for Debian / Raspberry Pi)
@changelog_1122_li
@changelog_1126_li
When opening a remote session, don't open a temporary file if the trace level is set to zero
When opening a remote session, don't open a temporary file if the trace level is set to zero
@changelog_1123_li
@changelog_1127_li
Use HMAC for authenticating remote LOB id's, removing the need for maintaining a cache, and removing the limit on the number of LOBs per result set.
Use HMAC for authenticating remote LOB id's, removing the need for maintaining a cache, and removing the limit on the number of LOBs per result set.
@changelog_1124_li
@changelog_1128_li
H2 Console: HTML and XML documents can now be edited in an updatable result set. There is (limited) support for editing multi-line documents.
H2 Console: HTML and XML documents can now be edited in an updatable result set. There is (limited) support for editing multi-line documents.
@changelog_1125_h2
@changelog_1129_h2
Version 1.3.167 (2012-05-23)
Version 1.3.167 (2012-05-23)
@changelog_1126_li
@changelog_1130_li
H2 Console: when editing a row, an empty varchar column was replaced with a single space.
H2 Console: when editing a row, an empty varchar column was replaced with a single space.
@changelog_1127_li
@changelog_1131_li
Lukas Eder has updated the jOOQ documentation.
Lukas Eder has updated the jOOQ documentation.
@changelog_1128_li
@changelog_1132_li
Some nested joins could not be executed, for example: select * from (select * from (select * from a) a right join b b) c;
Some nested joins could not be executed, for example: select * from (select * from (select * from a) a right join b b) c;
@changelog_1129_li
@changelog_1133_li
MS SQL Server compatibility: ISNULL is now an alias for IFNULL.
MS SQL Server compatibility: ISNULL is now an alias for IFNULL.
@changelog_1130_li
@changelog_1134_li
Terrence Huang has completed the translation of the H2 Console tool to Chinese. Thanks a lot!
Terrence Huang has completed the translation of the H2 Console tool to Chinese. Thanks a lot!
@changelog_1131_li
@changelog_1135_li
Server mode: the number of CLOB / BLOB values that were cached on the server is now the maximum of: 5 times the SERVER_RESULT_SET_FETCH_SIZE (which is 100 by default), and SysProperties.SERVER_CACHED_OBJECTS.
Server mode: the number of CLOB / BLOB values that were cached on the server is now the maximum of: 5 times the SERVER_RESULT_SET_FETCH_SIZE (which is 100 by default), and SysProperties.SERVER_CACHED_OBJECTS.
@changelog_1132_li
@changelog_1136_li
In the trace file, the query execution time was incorrect in some cases, specially for the statement SET TRACE_LEVEL_FILE 2.
In the trace file, the query execution time was incorrect in some cases, specially for the statement SET TRACE_LEVEL_FILE 2.
@changelog_1133_li
@changelog_1137_li
The feature LOG_SIZE_LIMIT that was introduced in version 1.3.165 did not always work correctly (specially with regards to multithreading) and has been removed. The message "Transaction log could not be truncated" is still written to the .trace.db file if required.
The feature LOG_SIZE_LIMIT that was introduced in version 1.3.165 did not always work correctly (specially with regards to multithreading) and has been removed. The message "Transaction log could not be truncated" is still written to the .trace.db file if required.
@changelog_1134_li
@changelog_1138_li
Then reading from a resource using the prefix "classpath:", the ContextClassLoader is now used if the resource can't be read otherwise.
Then reading from a resource using the prefix "classpath:", the ContextClassLoader is now used if the resource can't be read otherwise.
@changelog_1135_li
@changelog_1139_li
DatabaseEventListener now calls setProgress whenever a statement starts and ends.
DatabaseEventListener now calls setProgress whenever a statement starts and ends.
@changelog_1136_li
@changelog_1140_li
DatabaseEventListener now calls setProgress periodically while a statement is running.
DatabaseEventListener now calls setProgress periodically while a statement is running.
@changelog_1137_li
@changelog_1141_li
The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME.
The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME.
@changelog_1138_li
@changelog_1142_li
Issue 378: when using views, the wrong values were bound to a parameter in some cases.
Issue 378: when using views, the wrong values were bound to a parameter in some cases.
@changelog_1139_li
@changelog_1143_li
Terrence Huang has translated the error messages to Chinese. Thanks a lot!
Terrence Huang has translated the error messages to Chinese. Thanks a lot!
@changelog_1140_li
@changelog_1144_li
TRUNC was added as an alias for TRUNCATE.
TRUNC was added as an alias for TRUNCATE.
@changelog_1141_li
@changelog_1145_li
Small optimisation for accessing result values by column name.
Small optimisation for accessing result values by column name.
@changelog_1142_li
@changelog_1146_li
Fix for bug in Statement.getMoreResults(int)
Fix for bug in Statement.getMoreResults(int)
@changelog_1143_li
@changelog_1147_li
The SCRIPT statements now supports filtering by schema and table. Thanks a lot to Jacob Qvortrup for providing the patch!
The SCRIPT statements now supports filtering by schema and table. Thanks a lot to Jacob Qvortrup for providing the patch!
@changelog_1144_h2
@changelog_1148_h2
Version 1.3.166 (2012-04-08)
Version 1.3.166 (2012-04-08)
@changelog_1145_li
@changelog_1149_li
Indexes on column that are larger than half the page size (wide indexes) could sometimes get corrupt, resulting in an ArrayIndexOutOfBoundsException in PageBtree.getRow or "Row not found" in PageBtreeLeaf. Also, such indexes used too much disk space.
Indexes on column that are larger than half the page size (wide indexes) could sometimes get corrupt, resulting in an ArrayIndexOutOfBoundsException in PageBtree.getRow or "Row not found" in PageBtreeLeaf. Also, such indexes used too much disk space.
@changelog_1146_li
@changelog_1150_li
Server mode: when retrieving more than 64 rows each containing a CLOB or BLOB, the error message "The object is already closed" was thrown.
Server mode: when retrieving more than 64 rows each containing a CLOB or BLOB, the error message "The object is already closed" was thrown.
@changelog_1147_li
@changelog_1151_li
ConvertTraceFile: the time in the trace file is now parsed as a long.
ConvertTraceFile: the time in the trace file is now parsed as a long.
@changelog_1148_li
@changelog_1152_li
Invalid connection settings are now detected.
Invalid connection settings are now detected.
@changelog_1149_li
@changelog_1153_li
Issue 387: WHERE condition getting pushed into sub-query with LIMIT.
Issue 387: WHERE condition getting pushed into sub-query with LIMIT.
@changelog_1150_h2
@changelog_1154_h2
Version 1.3.165 (2012-03-18)
Version 1.3.165 (2012-03-18)
@changelog_1151_li
@changelog_1155_li
Better string representation for decimal values (for example 0.00000000 instead of 0E-26).
Better string representation for decimal values (for example 0.00000000 instead of 0E-26).
@changelog_1152_li
@changelog_1156_li
Prepared statements could only be re-used if the same data types were used the second time they were executed.
Prepared statements could only be re-used if the same data types were used the second time they were executed.
@changelog_1153_li
@changelog_1157_li
In error messages about referential constraint violation, the values are now included.
In error messages about referential constraint violation, the values are now included.
@changelog_1154_li
@changelog_1158_li
SCRIPT and RUNSCRIPT: the password can now be set using a prepared statement. Previously, it was required to be a literal in the SQL statement.
SCRIPT and RUNSCRIPT: the password can now be set using a prepared statement. Previously, it was required to be a literal in the SQL statement.
@changelog_1155_li
@changelog_1159_li
MySQL compatibility: SUBSTR with a negative start index now works like MySQL.
MySQL compatibility: SUBSTR with a negative start index now works like MySQL.
@changelog_1156_li
@changelog_1160_li
When enabling autocommit, the transaction is now committed (as required by the JDBC API).
When enabling autocommit, the transaction is now committed (as required by the JDBC API).
@changelog_1157_li
@changelog_1161_li
The shell script <code>h2.sh</code> did not work with spaces in the path. It also works now with quoted spaces in the argument list. Thanks a lot to Shimizu Fumiyuki for the patch!
The shell script <code>h2.sh</code> did not work with spaces in the path. It also works now with quoted spaces in the argument list. Thanks a lot to Shimizu Fumiyuki for the patch!
@changelog_1158_li
@changelog_1162_li
If the transaction log could not be truncated because of an uncommitted transaction, now "Transaction log could not be truncated" is written to the .trace.db file. Before, the database file was growing and it was hard to find out what the root cause was. To avoid the database file from growing, a new feature to automatically rollback the oldest transaction is available now. To enable it, append ;LOG_SIZE_LIMIT=32 to the database URL (in that case, the oldest session is rolled back if the transaction log is 32 MB).
If the transaction log could not be truncated because of an uncommitted transaction, now "Transaction log could not be truncated" is written to the .trace.db file. Before, the database file was growing and it was hard to find out what the root cause was. To avoid the database file from growing, a new feature to automatically rollback the oldest transaction is available now. To enable it, append ;LOG_SIZE_LIMIT=32 to the database URL (in that case, the oldest session is rolled back if the transaction log is 32 MB).
@changelog_1159_li
@changelog_1163_li
ALTER TABLE ADD can now add more than one column at a time.
ALTER TABLE ADD can now add more than one column at a time.
@changelog_1160_li
@changelog_1164_li
Issue 380: ALTER TABLE ADD FOREIGN KEY with an explicit index didn't verify the index can be used, which would lead to a NullPointerException later on.
Issue 380: ALTER TABLE ADD FOREIGN KEY with an explicit index didn't verify the index can be used, which would lead to a NullPointerException later on.
@changelog_1161_li
@changelog_1165_li
Issue 384: the wrong kind of exception (NullPointerException) was thrown in a UNION query with an incorrect ORDER BY expression.
Issue 384: the wrong kind of exception (NullPointerException) was thrown in a UNION query with an incorrect ORDER BY expression.
@changelog_1162_li
@changelog_1166_li
Issue 362: support LIMIT in UPDATE statements.
Issue 362: support LIMIT in UPDATE statements.
@changelog_1163_li
@changelog_1167_li
Browser: if no default browser is set, Google Chrome is now used if available. If not available, then Konqueror, Netscape, or Opera is used if available (as before).
Browser: if no default browser is set, Google Chrome is now used if available. If not available, then Konqueror, Netscape, or Opera is used if available (as before).
@changelog_1164_li
@changelog_1168_li
CSV tool: new feature to disable writing the column header (option writeColumnHeader).
CSV tool: new feature to disable writing the column header (option writeColumnHeader).
@changelog_1165_li
@changelog_1169_li
CSV tool: new feature to preserve the case sensitivity of column names (option caseSensitiveColumnNames).
CSV tool: new feature to preserve the case sensitivity of column names (option caseSensitiveColumnNames).
@changelog_1166_li
@changelog_1170_li
PostgreSQL compatibility: LOG(x) is base 10 in the PostgreSQL mode.
PostgreSQL compatibility: LOG(x) is base 10 in the PostgreSQL mode.
@changelog_1167_h2
@changelog_1171_h2
Version 1.3.164 (2012-02-03)
Version 1.3.164 (2012-02-03)
@changelog_1168_li
@changelog_1172_li
New built-in function ARRAY_CONTAINS.
New built-in function ARRAY_CONTAINS.
@changelog_1169_li
@changelog_1173_li
Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
@changelog_1170_li
@changelog_1174_li
Trying to convert a VARCHAR to UUID will now fail if the text contains a character that is not a hex digit, '-', or not a whitespace.
Trying to convert a VARCHAR to UUID will now fail if the text contains a character that is not a hex digit, '-', or not a whitespace.
@changelog_1171_li
@changelog_1175_li
TriggerAdapter: in "before" triggers, values can be changed using the ResultSet.updateX methods.
TriggerAdapter: in "before" triggers, values can be changed using the ResultSet.updateX methods.
@changelog_1172_li
@changelog_1176_li
Creating a table with column data type NULL now works (even if not very useful).
Creating a table with column data type NULL now works (even if not very useful).
@changelog_1173_li
@changelog_1177_li
ALTER TABLE ALTER COLUMN no longer copies the data for widening conversions (for example if only the precision was increased) unless necessary.
ALTER TABLE ALTER COLUMN no longer copies the data for widening conversions (for example if only the precision was increased) unless necessary.
@changelog_1174_li
@changelog_1178_li
Multi-threaded kernel: concurrently running an online backup and updating the database resulted in a broken (transactionally incorrect) backup file in some cases.
Multi-threaded kernel: concurrently running an online backup and updating the database resulted in a broken (transactionally incorrect) backup file in some cases.
@changelog_1175_li
@changelog_1179_li
The script created by SCRIPT DROP did not always work if multiple views existed that depend on each other.
The script created by SCRIPT DROP did not always work if multiple views existed that depend on each other.
@changelog_1176_li
@changelog_1180_li
MathUtils.getSecureRandom could log a warning to System.err in case the /dev/random is very slow, and the System.getProperties().toString() returned a string larger than 64 KB.
MathUtils.getSecureRandom could log a warning to System.err in case the /dev/random is very slow, and the System.getProperties().toString() returned a string larger than 64 KB.
@changelog_1177_li
@changelog_1181_li
The database file locking mechanism "FS" (;FILE_LOCK=FS) did not work on Linux since version 1.3.161.
The database file locking mechanism "FS" (;FILE_LOCK=FS) did not work on Linux since version 1.3.161.
@changelog_1178_li
@changelog_1182_li
Sequences: the functions NEXTVAL and CURRVAL did not work as expected when using quoted, mixed case sequence names.
Sequences: the functions NEXTVAL and CURRVAL did not work as expected when using quoted, mixed case sequence names.
@changelog_1179_li
@changelog_1183_li
The constructor for Csv objects is now public, and Csv.getInstance() is now deprecated.
The constructor for Csv objects is now public, and Csv.getInstance() is now deprecated.
@changelog_1180_li
@changelog_1184_li
SimpleResultSet: updating a result set is now supported.
SimpleResultSet: updating a result set is now supported.
@changelog_1181_li
@changelog_1185_li
Database URL: extra semicolons are not supported.
Database URL: extra semicolons are not supported.
@changelog_1182_h2
@changelog_1186_h2
Version 1.3.163 (2011-12-30)
Version 1.3.163 (2011-12-30)
@changelog_1183_li
@changelog_1187_li
On out of disk space, the database could get corrupt sometimes, if later write operations succeeded. The same problem happened on other kinds of I/O exceptions (where one or some of the writes fail, but subsequent writes succeed). Now the file is closed on the first unsuccessful write operation, so that later requests fail consistently.
On out of disk space, the database could get corrupt sometimes, if later write operations succeeded. The same problem happened on other kinds of I/O exceptions (where one or some of the writes fail, but subsequent writes succeed). Now the file is closed on the first unsuccessful write operation, so that later requests fail consistently.
@changelog_1184_li
@changelog_1188_li
DatabaseEventListener.diskSpaceIsLow() is no longer supported because it can't be guaranteed that it always works correctly.
DatabaseEventListener.diskSpaceIsLow() is no longer supported because it can't be guaranteed that it always works correctly.
@changelog_1185_li
@changelog_1189_li
XMLTEXT now supports an optional parameter to escape newlines.
XMLTEXT now supports an optional parameter to escape newlines.
@changelog_1186_li
@changelog_1190_li
XMLNODE now support an optional parameter to disable indentation.
XMLNODE now support an optional parameter to disable indentation.
@changelog_1187_li
@changelog_1191_li
Csv.write now formats date, time, and timestamp values using java.sql.Date / Time / Timestamp.toString(). Previously, ResultSet.getString() was used, which didn't work well for Oracle.
Csv.write now formats date, time, and timestamp values using java.sql.Date / Time / Timestamp.toString(). Previously, ResultSet.getString() was used, which didn't work well for Oracle.
@changelog_1188_li
@changelog_1192_li
The shell script <code>h2.sh</code> can now be run from within a different directory. Thanks a lot to Daniel Serodio for the patch!
The shell script <code>h2.sh</code> can now be run from within a different directory. Thanks a lot to Daniel Serodio for the patch!
@changelog_1189_li
@changelog_1193_li
The page size of a persistent database can now be queries using: select * from information_schema.settings where name = 'info.PAGE_SIZE'
The page size of a persistent database can now be queries using: select * from information_schema.settings where name = 'info.PAGE_SIZE'
@changelog_1190_li
@changelog_1194_li
In the server mode, BLOB and CLOB objects are no longer closed when the result set is closed (as required by the JDBC spec).
In the server mode, BLOB and CLOB objects are no longer closed when the result set is closed (as required by the JDBC spec).
@cheatSheet_1000_h1
@cheatSheet_1000_h1
...
@@ -7148,51 +7160,48 @@ Table Engine for H2
...
@@ -7148,51 +7160,48 @@ Table Engine for H2
The plan is to use the MVStore as the default storage engine for the H2 database in the future (supporting SQL, JDBC, transactions, MVCC, and so on). This is work in progress. To try it out, append <code>;DEFAULT_TABLE_ENGINE=org.h2.mvstore.db.MVTableEngine</code> to the database URL. In general, functionality and performance should be similar than the current default storage engine (the page store). There are a few features that have not been implemented yet or are not complete:
The plan is to use the MVStore as the default storage engine for the H2 database in the future (supporting SQL, JDBC, transactions, MVCC, and so on). This is work in progress. To try it out, append <code>;DEFAULT_TABLE_ENGINE=org.h2.mvstore.db.MVTableEngine</code> to the database URL. In general, functionality and performance should be similar than the current default storage engine (the page store). There are a few features that have not been implemented yet or are not complete:
@mvstore_1111_li
@mvstore_1111_li
Changing the cache size.
Changing the cache size is currently not supported.
@mvstore_1112_li
@mvstore_1112_li
Two-phase commit.
The database metadata is still stored in a <code>.h2.db</code> file, and the <code>.lock.db</code> file is still used to lock a database (long term, the plan is to no longer use those files).
@mvstore_1113_li
@mvstore_1113_li
The database metadata is still stored in a <code>.h2.db</code> file.
@mvstore_1114_li
The database file(s) sometimes do not shrink as expected.
The database file(s) sometimes do not shrink as expected.
@mvstore_1115_h2
@mvstore_1114_h2
Similar Projects and Differences to Other Storage Engines
Similar Projects and Differences to Other Storage Engines
@mvstore_1116_p
@mvstore_1115_p
Unlike similar storage engines like LevelDB and Kyoto Cabinet, the MVStore is written in Java and can easily be embedded in a Java and Android application.
Unlike similar storage engines like LevelDB and Kyoto Cabinet, the MVStore is written in Java and can easily be embedded in a Java and Android application.
@mvstore_1117_p
@mvstore_1116_p
The MVStore is somewhat similar to the Berkeley DB Java Edition because it is also written in Java, and is also a log structured storage, but the H2 license is more liberal.
The MVStore is somewhat similar to the Berkeley DB Java Edition because it is also written in Java, and is also a log structured storage, but the H2 license is more liberal.
@mvstore_1118_p
@mvstore_1117_p
Like SQLite, the MVStore keeps all data in one file. Unlike SQLite, the MVStore uses is a log structured storage. The plan is to make the MVStore both easier to use as well as faster than SQLite. In a recent (very simple) test, the MVStore was about twice as fast as SQLite on Android.
Like SQLite, the MVStore keeps all data in one file. Unlike SQLite, the MVStore uses is a log structured storage. The plan is to make the MVStore both easier to use as well as faster than SQLite. In a recent (very simple) test, the MVStore was about twice as fast as SQLite on Android.
@mvstore_1119_p
@mvstore_1118_p
The API of the MVStore is similar to MapDB (previously known as JDBM) from Jan Kotek, and some code is shared between MapDB and JDBM. However, unlike MapDB, the MVStore uses is a log structured storage. The MVStore does not have a record size limit.
The API of the MVStore is similar to MapDB (previously known as JDBM) from Jan Kotek, and some code is shared between MapDB and JDBM. However, unlike MapDB, the MVStore uses is a log structured storage. The MVStore does not have a record size limit.
@mvstore_1120_h2
@mvstore_1119_h2
Current State
Current State
@mvstore_1121_p
@mvstore_1120_p
The code is still experimental at this stage. The API as well as the behavior may partially change. Features may be added and removed (even thought the main features will stay).
The code is still experimental at this stage. The API as well as the behavior may partially change. Features may be added and removed (even thought the main features will stay).
@mvstore_1122_h2
@mvstore_1121_h2
Requirements
Requirements
@mvstore_1123_p
@mvstore_1122_p
The MVStore is included in the latest H2 jar file.
The MVStore is included in the latest H2 jar file.
@mvstore_1124_p
@mvstore_1123_p
There are no special requirements to use it. The MVStore should run on any JVM as well as on Android.
There are no special requirements to use it. The MVStore should run on any JVM as well as on Android.
@mvstore_1125_p
@mvstore_1124_p
To build just the MVStore (without the database engine), run:
To build just the MVStore (without the database engine), run:
@mvstore_1126_p
@mvstore_1125_p
This will create the file <code>bin/h2mvstore-1.3.172.jar</code> (about 130 KB).
This will create the file <code>bin/h2mvstore-1.3.172.jar</code> (about 130 KB).
#Main memory requirements: The larger the database, the more main memory is required. With the version 1.1 storage mechanism, the minimum main memory required for a 12 GB database was around 240 MB. With the current page store, the minimum main memory required is much lower, around 1 MB for each 8 GB database file size.
#Main memory requirements: The larger the database, the more main memory is required. With the current storage mechanism (the page store), the minimum main memory required is around 1 MB for each 8 GB database file size.
@advanced_1402_li
@advanced_1402_li
#Limit on the complexity of SQL statements. Statements of the following form will result in a stack overflow exception:
#Limit on the complexity of SQL statements. Statements of the following form will result in a stack overflow exception:
#Issue 468: trunc(timestamp) could return the wrong value.
#Issue 468: trunc(timestamp) could return the wrong value (+12 hours), and trunc(number) throw a NullPointerException.
@changelog_1008_li
@changelog_1008_li
#Fixed a deadlock when updating LOB's concurrently. See TestLob.testDeadlock2().
#The expression trunc(number) threw a NullPointerException.
@changelog_1009_li
@changelog_1009_li
#Fixed a deadlock related to very large temporary result sets.
#Fixed a deadlock when updating LOB's concurrently. See TestLob.testDeadlock2().
@changelog_1010_li
@changelog_1010_li
#Add "-list" command line option to Shell tool so that result-list-mode can be triggered when reading from a file.
#Fixed a deadlock related to very large temporary result sets.
@changelog_1011_li
@changelog_1011_li
#Issue 474: H2 Mysql Compatibility code fails to ignore "COMMENT" in CREATE TABLE, patch from Aaron Azeckoski.
#Add "-list" command line option to Shell tool so that result-list-mode can be triggered when reading from a file.
@changelog_1012_li
@changelog_1012_li
#Issue 476: Broken link in jaqu.html
#Issue 474: H2 MySQL Compatibility code fails to ignore "COMMENT" in CREATE TABLE, patch from Aaron Azeckoski.
@changelog_1013_li
@changelog_1013_li
#Fix potential UTF8 encoding issue in org.h2.store.FileStore, reported by Juerg Spiess.
#Issue 476: Broken link in jaqu.html
@changelog_1014_li
@changelog_1014_li
#Improve error message when check constraint is broken, test case from Gili (cowwoc).
#Fix potential UTF8 encoding issue in org.h2.store.FileStore, reported by Juerg Spiess.
@changelog_1015_li
@changelog_1015_li
#Improve error message when we have a unique constraint violation, displays the offending key in the error message.
#Improve error message when check constraint is broken, test case from Gili (cowwoc).
@changelog_1016_li
@changelog_1016_li
#Issue 478: Support for "SHOW TRANSACTION ISOLATION LEVEL", patch from Andrew Franklin.
#Improve error message when we have a unique constraint violation, displays the offending key in the error message.
@changelog_1017_li
@changelog_1017_li
#Issue 475: PgServer: add support for CancelRequest, patch from Andrew Franklin.
#Issue 478: Support for "SHOW TRANSACTION ISOLATION LEVEL", patch from Andrew Franklin.
@changelog_1018_li
@changelog_1018_li
#Issue 473: PgServer missing -key option, patch from Andrew Franklin.
#Issue 475: PgServer: add support for CancelRequest, patch from Andrew Franklin.
@changelog_1019_li
@changelog_1019_li
#Issue 471: CREATE VIEW does not check user rights, patch from Andrew Franklin.
#Issue 473: PgServer missing -key option, patch from Andrew Franklin.
@changelog_1020_li
@changelog_1020_li
#Issue 477: PgServer binary transmission of query params is unimplemented, patch from Andrew Franklin.
#Issue 471: CREATE VIEW does not check user rights, patch from Andrew Franklin.
@changelog_1021_li
@changelog_1021_li
#Issue 479: Support for SUBSTRING without a FROM condition, patch from Andrew Franklin.
#Issue 477: PgServer binary transmission of query params is unimplemented, patch from Andrew Franklin.
@changelog_1022_li
@changelog_1022_li
#Issue 472: PgServer does not work with any recent Postgres JDBC driver, patch from Andrew Franklin.
#Issue 479: Support for SUBSTRING without a FROM condition, patch from Andrew Franklin.
@changelog_1023_li
@changelog_1023_li
#Add syntax for passing additional parameters into custom TableEngine implementations.
#Issue 472: PgServer does not work with any recent Postgres JDBC driver, patch from Andrew Franklin.
@changelog_1024_li
@changelog_1024_li
#Issue 480: Bugfix post issue #475, #477, patch from Andrew Franklin.
#Add syntax for passing additional parameters into custom TableEngine implementations.
@changelog_1025_li
@changelog_1025_li
#Issue 481: Further extensions to PgServer to support better support PG JDBC, patch from Andrew Franklin.
#Issue 480: Bugfix post issue 475, 477, patch from Andrew Franklin.
@changelog_1026_li
@changelog_1026_li
#Add support for spatial datatype GEOMETRY.
#Issue 481: Further extensions to PgServer to support better support PG JDBC, patch from Andrew Franklin.
@changelog_1027_li
@changelog_1027_li
#Add support for in-memory spatial index.
#Add support for spatial datatype GEOMETRY.
@changelog_1028_li
@changelog_1028_li
#Add support for in-memory spatial index.
@changelog_1029_li
#change the PageStore#changeCount field from an int to a long, to cope with databases with very high transaction rates.
#change the PageStore#changeCount field from an int to a long, to cope with databases with very high transaction rates.
@changelog_1029_h2
@changelog_1030_li
#Fix a NullPointerException when attempting to add foreign key reference to a view.
@changelog_1031_li
#Add sufficient ClientInfo support to our javax.sql.Connection implementation to make WebSphere happy.
@changelog_1032_li
#Issue 482: class LobStorageBackend$LobInputStream does not override the method InputStream.available().
@changelog_1033_h2
#Version 1.3.172 (2013-05-25)
#Version 1.3.172 (2013-05-25)
@changelog_1030_li
@changelog_1034_li
#Referential integrity: when adding a referential integrity constraint failed, and if creating the constraint automatically created an index, this index was not removed.
#Referential integrity: when adding a referential integrity constraint failed, and if creating the constraint automatically created an index, this index was not removed.
@changelog_1031_li
@changelog_1035_li
#The auto-analyze feature now only reads 1000 rows per table instead of 10000.
#The auto-analyze feature now only reads 1000 rows per table instead of 10000.
@changelog_1032_li
@changelog_1036_li
#The optimization for IN(...) queries combined with OR could result in a strange exception of the type "column x must be included in the group by list".
#The optimization for IN(...) queries combined with OR could result in a strange exception of the type "column x must be included in the group by list".
@changelog_1033_li
@changelog_1037_li
#Issue 454: Use Charset for type-safety.
#Issue 454: Use Charset for type-safety.
@changelog_1034_li
@changelog_1038_li
#Queries with both LIMIT and OFFSET could throw an IllegalArgumentException.
#Queries with both LIMIT and OFFSET could throw an IllegalArgumentException.
@changelog_1035_li
@changelog_1039_li
#MVStore: multiple issues were fixed: 460, 461, 462, 464, 466.
#MVStore: multiple issues were fixed: 460, 461, 462, 464, 466.
@changelog_1036_li
@changelog_1040_li
#MVStore: larger stores (multiple GB) are now much faster.
#MVStore: larger stores (multiple GB) are now much faster.
@changelog_1037_li
@changelog_1041_li
#When using local temporary tables and not dropping them manually before closing the session, and then killing the process could result in a database that couldn't be opened (except when using the recover tool).
#When using local temporary tables and not dropping them manually before closing the session, and then killing the process could result in a database that couldn't be opened (except when using the recover tool).
@changelog_1038_li
@changelog_1042_li
#Support TRUNC(timestamp) for improved Oracle compatibility.
#Support TRUNC(timestamp) for improved Oracle compatibility.
@changelog_1039_li
@changelog_1043_li
#Add support for CREATE TABLE TEST (ID BIGSERIAL) for PostgreSQL compatibility. Patch from Jesse Long.
#Add support for CREATE TABLE TEST (ID BIGSERIAL) for PostgreSQL compatibility. Patch from Jesse Long.
@changelog_1040_li
@changelog_1044_li
#Add new collation command SET BINARY_COLLATION UNSIGNED, helps with people testing BINARY columns in MySQL mode.
#Add new collation command SET BINARY_COLLATION UNSIGNED, helps with people testing BINARY columns in MySQL mode.
@changelog_1041_li
@changelog_1045_li
#Issue 453: ABBA race conditions in TABLE LINK connection sharing.
#Issue 453: ABBA race conditions in TABLE LINK connection sharing.
@changelog_1042_li
@changelog_1046_li
#Issue 449: Postgres Serial data type should not automatically be marked as primary key
#Issue 449: Postgres Serial data type should not automatically be marked as primary key
@changelog_1043_li
@changelog_1047_li
#Issue 406: Support "select h2version()"
#Issue 406: Support "select h2version()"
@changelog_1044_li
@changelog_1048_li
#Issue 389: When there is a multi-column primary key, H2 does not seem to always pick the right index
#Issue 389: When there is a multi-column primary key, H2 does not seem to always pick the right index
@changelog_1045_li
@changelog_1049_li
#Issue 305: Implement SELECT ... FOR FETCH ONLY
#Issue 305: Implement SELECT ... FOR FETCH ONLY
@changelog_1046_li
@changelog_1050_li
#Issue 274: Sybase/MSSQLServer compatibility - Add GETDATE and CHARINDEX system functions
#Issue 274: Sybase/MSSQLServer compatibility - Add GETDATE and CHARINDEX system functions
@changelog_1047_li
@changelog_1051_li
#Issue 274: Sybase/MSSQLServer compatibility - swap parameters of CONVERT function.
#Issue 274: Sybase/MSSQLServer compatibility - swap parameters of CONVERT function.
@changelog_1048_li
@changelog_1052_li
#Issue 274: Sybase/MSSQLServer compatibility - support index clause e.g. "select * from test (index table1_index)"
#Issue 274: Sybase/MSSQLServer compatibility - support index clause e.g. "select * from test (index table1_index)"
@changelog_1049_li
@changelog_1053_li
#Fix bug in Optimizing SELECT * FROM A WHERE X=1 OR X=2 OR X=3 into SELECT * FROM A WHERE X IN (1,2,3)
#Fix bug in Optimizing SELECT * FROM A WHERE X=1 OR X=2 OR X=3 into SELECT * FROM A WHERE X IN (1,2,3)
@changelog_1050_li
@changelog_1054_li
#Issue 442: Groovy patch for SourceCompiler (function ALIAS)
#Issue 442: Groovy patch for SourceCompiler (function ALIAS)
@changelog_1051_li
@changelog_1055_li
#Issue 459: Improve LOB documentation
#Issue 459: Improve LOB documentation
@changelog_1052_h2
@changelog_1056_h2
#Version 1.3.171 (2013-03-17)
#Version 1.3.171 (2013-03-17)
@changelog_1053_li
@changelog_1057_li
#Security: the TCP server did not correctly restrict access rights of clients in some cases. This was specially a problem when using the flag "tcpAllowOthers".
#Security: the TCP server did not correctly restrict access rights of clients in some cases. This was specially a problem when using the flag "tcpAllowOthers".
@changelog_1054_li
@changelog_1058_li
#H2 Console: the session timeout can now be configured using the system property "h2.consoleTimeout".
#H2 Console: the session timeout can now be configured using the system property "h2.consoleTimeout".
@changelog_1055_li
@changelog_1059_li
#Issue 431: Improved compatibility with MySQL: support for "ENGINE=InnoDB charset=UTF8" when creating a table.
#Issue 431: Improved compatibility with MySQL: support for "ENGINE=InnoDB charset=UTF8" when creating a table.
@changelog_1056_li
@changelog_1060_li
#Issue 249: Improved compatibility with MySQL in the MySQL mode: now the methods DatabaseMetaData methods stores*Case*Identifiers return the same as MySQL when using the MySQL mode.
#Issue 249: Improved compatibility with MySQL in the MySQL mode: now the methods DatabaseMetaData methods stores*Case*Identifiers return the same as MySQL when using the MySQL mode.
@changelog_1057_li
@changelog_1061_li
#Issue 434: H2 Console didn't work in the Chrome browser due to a wrong viewport argument.
#Issue 434: H2 Console didn't work in the Chrome browser due to a wrong viewport argument.
@changelog_1058_li
@changelog_1062_li
#There was a possibility that the .lock.db file was not deleted when the database was closed, which could slow down opening the database.
#There was a possibility that the .lock.db file was not deleted when the database was closed, which could slow down opening the database.
@changelog_1059_li
@changelog_1063_li
#The SQL script generated by the "script" command contained inconsistent newlines on Windows.
#The SQL script generated by the "script" command contained inconsistent newlines on Windows.
@changelog_1060_li
@changelog_1064_li
#When using trace level 4 (SLF4J) in the server mode, a directory "trace.db" and an empty file was created on the client side. This is no longer made.
#When using trace level 4 (SLF4J) in the server mode, a directory "trace.db" and an empty file was created on the client side. This is no longer made.
@changelog_1061_li
@changelog_1065_li
#Optimize IN(...) queries: there was a bug in version 1.3.170 if the type of the left hand side didn't match the type of the right hand side. Fixed.
#Optimize IN(...) queries: there was a bug in version 1.3.170 if the type of the left hand side didn't match the type of the right hand side. Fixed.
@changelog_1062_li
@changelog_1066_li
#Optimize IN(...) queries: there was a bug in version 1.3.170 for comparison of the type "X IN(NULL, NULL)". Fixed.
#Optimize IN(...) queries: there was a bug in version 1.3.170 for comparison of the type "X IN(NULL, NULL)". Fixed.
@changelog_1063_li
@changelog_1067_li
#Timestamps with timezone that were passed as a string were not always converted correctly. For example "2012-11-06T23:00:00.000Z" was converted to "2012-11-06" instead of to "2012-11-07" in the timezone CET. Thanks a lot to Steve Hruda for reporting the problem!
#Timestamps with timezone that were passed as a string were not always converted correctly. For example "2012-11-06T23:00:00.000Z" was converted to "2012-11-06" instead of to "2012-11-07" in the timezone CET. Thanks a lot to Steve Hruda for reporting the problem!
@changelog_1064_li
@changelog_1068_li
#New table engine "org.h2.mvstore.db.MVTableEngine" that internally uses the MVStore to persist data. To try it out, append ";DEFAULT_TABLE_ENGINE=org.h2.mvstore.db.MVTableEngine" to the database URL. This is still very experimental, and many features are not supported yet. The data is stored in a file with the suffix ".mv.db".
#New table engine "org.h2.mvstore.db.MVTableEngine" that internally uses the MVStore to persist data. To try it out, append ";DEFAULT_TABLE_ENGINE=org.h2.mvstore.db.MVTableEngine" to the database URL. This is still very experimental, and many features are not supported yet. The data is stored in a file with the suffix ".mv.db".
@changelog_1065_li
@changelog_1069_li
#New connection setting "DEFAULT_TABLE_ENGINE" to use a specific table engine if none is set explicitly. This is to simplify testing the MVStore table engine.
#New connection setting "DEFAULT_TABLE_ENGINE" to use a specific table engine if none is set explicitly. This is to simplify testing the MVStore table engine.
@changelog_1066_li
@changelog_1070_li
#MVStore: encrypted stores are now supported. Only standardized algorithms are used: PBKDF2, SHA-256, XTS-AES, AES-128.
#MVStore: encrypted stores are now supported. Only standardized algorithms are used: PBKDF2, SHA-256, XTS-AES, AES-128.
@changelog_1067_li
@changelog_1071_li
#MVStore: improved API thanks to Simo Tripodi.
#MVStore: improved API thanks to Simo Tripodi.
@changelog_1068_li
@changelog_1072_li
#MVStore: maps can now be renamed.
#MVStore: maps can now be renamed.
@changelog_1069_li
@changelog_1073_li
#MVStore: store the file header also at the end of each chunk, which results in a further reduced number of write operations.
#MVStore: store the file header also at the end of each chunk, which results in a further reduced number of write operations.
@changelog_1070_li
@changelog_1074_li
#MVStore: a map implementation that supports concurrent operations.
#MVStore: a map implementation that supports concurrent operations.
@changelog_1071_li
@changelog_1075_li
#MVStore: unified exception handling; the version is included in the messages.
#MVStore: unified exception handling; the version is included in the messages.
@changelog_1072_li
@changelog_1076_li
#MVStore: old data is now retained for 45 seconds by default.
#MVStore: old data is now retained for 45 seconds by default.
@changelog_1073_li
@changelog_1077_li
#MVStore: compress is now disabled by default, and can be enabled on request.
#MVStore: compress is now disabled by default, and can be enabled on request.
@changelog_1074_li
@changelog_1078_li
#Support ALTER TABLE ADD ... AFTER. Patch from Andrew Gaul (argaul at gmail.com). Fixes issue 401.
#Support ALTER TABLE ADD ... AFTER. Patch from Andrew Gaul (argaul at gmail.com). Fixes issue 401.
@changelog_1075_li
@changelog_1079_li
#Improved OSGi support. H2 now registers itself as a DataSourceFactory service. Fixes issue 365.
#Improved OSGi support. H2 now registers itself as a DataSourceFactory service. Fixes issue 365.
@changelog_1076_li
@changelog_1080_li
#Add a DISK_SPACE_USED system function. Fixes issue 270.
#Add a DISK_SPACE_USED system function. Fixes issue 270.
@changelog_1077_li
@changelog_1081_li
#Fix a compile-time ambiguity when compiling with JDK7, thanks to a patch from Lukas Eder.
#Fix a compile-time ambiguity when compiling with JDK7, thanks to a patch from Lukas Eder.
@changelog_1078_li
@changelog_1082_li
#Supporting dropping an index for Lucene full-text indexes.
#Supporting dropping an index for Lucene full-text indexes.
@changelog_1079_li
@changelog_1083_li
#Optimized performance for SELECT ... ORDER BY X LIMIT Y OFFSET Z queries for in-memory databases using partial sort (by Sergi Vladykin).
#Optimized performance for SELECT ... ORDER BY X LIMIT Y OFFSET Z queries for in-memory databases using partial sort (by Sergi Vladykin).
@changelog_1080_li
@changelog_1084_li
#Experimental off-heap memory storage engine "nioMemFS:" and "nioMemLZF:", suggestion from Mark Addleman.
#Experimental off-heap memory storage engine "nioMemFS:" and "nioMemLZF:", suggestion from Mark Addleman.
@changelog_1081_li
@changelog_1085_li
#Issue 438: JdbcDatabaseMetaData.getSchemas() is no longer supported as of 1.3.169.
#Issue 438: JdbcDatabaseMetaData.getSchemas() is no longer supported as of 1.3.169.
@changelog_1082_li
@changelog_1086_li
#MySQL compatibility: support for ALTER TABLE tableName MODIFY [COLUMN] columnName columnDef. Patch from Ville Koskela.
#MySQL compatibility: support for ALTER TABLE tableName MODIFY [COLUMN] columnName columnDef. Patch from Ville Koskela.
@changelog_1083_li
@changelog_1087_li
#Issue 404: SHOW COLUMNS FROM tableName does not work with ALLOW_LITERALS=NUMBERS.
#Issue 404: SHOW COLUMNS FROM tableName does not work with ALLOW_LITERALS=NUMBERS.
@changelog_1084_li
@changelog_1088_li
#Throw an explicit error to make it clear we don't support the TRIGGER combination of SELECT and FOR EACH ROW.
#Throw an explicit error to make it clear we don't support the TRIGGER combination of SELECT and FOR EACH ROW.
@changelog_1085_li
@changelog_1089_li
#Issue 439: Utils.sortTopN does not handle single-element arrays.
#Issue 439: Utils.sortTopN does not handle single-element arrays.
@changelog_1086_h2
@changelog_1090_h2
#Version 1.3.170 (2012-11-30)
#Version 1.3.170 (2012-11-30)
@changelog_1087_li
@changelog_1091_li
#Issue 407: The TriggerAdapter didn't work with CLOB and BLOB columns.
#Issue 407: The TriggerAdapter didn't work with CLOB and BLOB columns.
@changelog_1088_li
@changelog_1092_li
#PostgreSQL compatibility: support for data types BIGSERIAL and SERIAL as an alias for AUTO_INCREMENT.
#PostgreSQL compatibility: support for data types BIGSERIAL and SERIAL as an alias for AUTO_INCREMENT.
@changelog_1089_li
@changelog_1093_li
#Issue 417: H2 Console: the web session timeout didn't work, resulting in a memory leak. This was only a problem if the H2 Console was run for a long time and many sessions were opened.
#Issue 417: H2 Console: the web session timeout didn't work, resulting in a memory leak. This was only a problem if the H2 Console was run for a long time and many sessions were opened.
@changelog_1090_li
@changelog_1094_li
#Issue 412: Running the Server tool with just the option "-browser" will now log a warning.
#Issue 412: Running the Server tool with just the option "-browser" will now log a warning.
@changelog_1091_li
@changelog_1095_li
#Issue 411: CloseWatcher registration was not concurrency-safe.
#Issue 411: CloseWatcher registration was not concurrency-safe.
@changelog_1092_li
@changelog_1096_li
#MySQL compatibility: support for CONCAT_WS. Thanks a lot to litailang for the patch!
#MySQL compatibility: support for CONCAT_WS. Thanks a lot to litailang for the patch!
@changelog_1093_li
@changelog_1097_li
#PostgreSQL compatibility: support for EXTRACT(WEEK FROM dateColumn). Thanks to Prashant Bhat for the patch!
#PostgreSQL compatibility: support for EXTRACT(WEEK FROM dateColumn). Thanks to Prashant Bhat for the patch!
@changelog_1094_li
@changelog_1098_li
#Fix for a bug where we would sometimes use the wrong unique constraint to validate foreign key constraints.
#Fix for a bug where we would sometimes use the wrong unique constraint to validate foreign key constraints.
@changelog_1095_li
@changelog_1099_li
#Support BOM at the beginning of files for the RUNSCRIPT command
#Support BOM at the beginning of files for the RUNSCRIPT command
@changelog_1096_li
@changelog_1100_li
#Fix in calling SET @X = IDENTITY() where it would return NULL incorrectly
#Fix in calling SET @X = IDENTITY() where it would return NULL incorrectly
@changelog_1097_li
@changelog_1101_li
#Fix ABBA deadlock between adding a constraint and the H2-Log-Writer thread.
#Fix ABBA deadlock between adding a constraint and the H2-Log-Writer thread.
@changelog_1098_li
@changelog_1102_li
#Optimize IN(...) queries where the values are constant and of the same type.
#Optimize IN(...) queries where the values are constant and of the same type.
@changelog_1099_li
@changelog_1103_li
#Restore tool: the parameter "quiet" was not used and is now removed.
#Restore tool: the parameter "quiet" was not used and is now removed.
@changelog_1100_li
@changelog_1104_li
#Fix ConcurrentModificationException when creating tables and executing SHOW TABLES in parallel. Reported by Viktor Voytovych.
#Fix ConcurrentModificationException when creating tables and executing SHOW TABLES in parallel. Reported by Viktor Voytovych.
@changelog_1101_li
@changelog_1105_li
#Serialization is now pluggable using the system property "h2.javaObjectSerializer". Thanks to Sergi Vladykin for the patch!
#Serialization is now pluggable using the system property "h2.javaObjectSerializer". Thanks to Sergi Vladykin for the patch!
@changelog_1102_h2
@changelog_1106_h2
#Version 1.3.169 (2012-09-09)
#Version 1.3.169 (2012-09-09)
@changelog_1103_li
@changelog_1107_li
#The default jar file is now compiled for Java 6.
#The default jar file is now compiled for Java 6.
@changelog_1104_li
@changelog_1108_li
#The new jar file will probably not end up in the central Maven repository in the next few weeks because Sonatype has disabled automatic synchronization from SourceForge (which they call 'legacy sync' now). It will probably take some time until this is sorted out. The H2 jar files are deployed to http://h2database.com/m2-repo/com/h2database/h2/maven-metadata.xml and http://hsql.sourceforge.net/m2-repo/com/h2database/h2/maven-metadata.xml as usual.
#The new jar file will probably not end up in the central Maven repository in the next few weeks because Sonatype has disabled automatic synchronization from SourceForge (which they call 'legacy sync' now). It will probably take some time until this is sorted out. The H2 jar files are deployed to http://h2database.com/m2-repo/com/h2database/h2/maven-metadata.xml and http://hsql.sourceforge.net/m2-repo/com/h2database/h2/maven-metadata.xml as usual.
@changelog_1105_li
@changelog_1109_li
#A part of the documentation and the H2 Console has been changed to support the Apple retina display.
#A part of the documentation and the H2 Console has been changed to support the Apple retina display.
@changelog_1106_li
@changelog_1110_li
#The CreateCluster tool could not be used if the source database contained a CLOB or BLOB. The root cause was that the TCP server did not synchronize on the session, which caused a problem when using the exclusive mode.
#The CreateCluster tool could not be used if the source database contained a CLOB or BLOB. The root cause was that the TCP server did not synchronize on the session, which caused a problem when using the exclusive mode.
@changelog_1107_li
@changelog_1111_li
#Statement.getQueryTimeout(): only the first call to this method will query the database. If the query timeout was changed in another way than calling setQueryTimeout, this method will always return the last value. This was changed because Hibernate calls getQueryTimeout() a lot.
#Statement.getQueryTimeout(): only the first call to this method will query the database. If the query timeout was changed in another way than calling setQueryTimeout, this method will always return the last value. This was changed because Hibernate calls getQueryTimeout() a lot.
@changelog_1108_li
@changelog_1112_li
#Issue 416: PreparedStatement.setNString throws AbstractMethodError. All implemented JDBC 4 methods that don't break compatibility with Java 5 are now included in the default jar file.
#Issue 416: PreparedStatement.setNString throws AbstractMethodError. All implemented JDBC 4 methods that don't break compatibility with Java 5 are now included in the default jar file.
@changelog_1109_li
@changelog_1113_li
#Issue 414: for some functions, the parameters were evaluated twice (for example "char(nextval(..))" ran "nextval(..)" twice).
#Issue 414: for some functions, the parameters were evaluated twice (for example "char(nextval(..))" ran "nextval(..)" twice).
@changelog_1110_li
@changelog_1114_li
#The ResultSetMetaData methods getSchemaName and getTableName could return null instead of "" (an empty string) as specified in the JDBC API.
#The ResultSetMetaData methods getSchemaName and getTableName could return null instead of "" (an empty string) as specified in the JDBC API.
@changelog_1111_li
@changelog_1115_li
#Added compatibility for "SET NAMES" query in MySQL compatibility mode.
#Added compatibility for "SET NAMES" query in MySQL compatibility mode.
@changelog_1112_h2
@changelog_1116_h2
#Version 1.3.168 (2012-07-13)
#Version 1.3.168 (2012-07-13)
@changelog_1113_li
@changelog_1117_li
#The message "Transaction log could not be truncated" was sometimes written to the .trace.db file even if there was no problem truncating the transaction log.
#The message "Transaction log could not be truncated" was sometimes written to the .trace.db file even if there was no problem truncating the transaction log.
@changelog_1114_li
@changelog_1118_li
#New system property "h2.serializeJavaObject" (default: true) that allows to disable serializing Java objects, so that the objects compareTo and toString methods can be used.
#New system property "h2.serializeJavaObject" (default: true) that allows to disable serializing Java objects, so that the objects compareTo and toString methods can be used.
@changelog_1115_li
@changelog_1119_li
#Dylan has translated the H2 Console tool to Korean. Thanks a lot!
#Dylan has translated the H2 Console tool to Korean. Thanks a lot!
@changelog_1116_li
@changelog_1120_li
#Executing the statement CREATE INDEX IF ALREADY EXISTS if the index already exists no longer fails for a read only database.
#Executing the statement CREATE INDEX IF ALREADY EXISTS if the index already exists no longer fails for a read only database.
@changelog_1117_li
@changelog_1121_li
#MVCC: concurrently updating a row could result in the row to appear deleted in the second connection, if there are multiple unique indexes (or a primary key and at least one unique index). Thanks a lot to Teruo for the patch!
#MVCC: concurrently updating a row could result in the row to appear deleted in the second connection, if there are multiple unique indexes (or a primary key and at least one unique index). Thanks a lot to Teruo for the patch!
@changelog_1118_li
@changelog_1122_li
#Fulltext search: in-memory Lucene indexes are now supported.
#Fulltext search: in-memory Lucene indexes are now supported.
@changelog_1119_li
@changelog_1123_li
#Fulltext search: UUID primary keys are now supported.
#Fulltext search: UUID primary keys are now supported.
@changelog_1120_li
@changelog_1124_li
#Apache Tomcat 7.x will now longer log a warning when unloading the web application, if using a connection pool.
#Apache Tomcat 7.x will now longer log a warning when unloading the web application, if using a connection pool.
@changelog_1121_li
@changelog_1125_li
#H2 Console: support the Midori browser (for Debian / Raspberry Pi)
#H2 Console: support the Midori browser (for Debian / Raspberry Pi)
@changelog_1122_li
@changelog_1126_li
#When opening a remote session, don't open a temporary file if the trace level is set to zero
#When opening a remote session, don't open a temporary file if the trace level is set to zero
@changelog_1123_li
@changelog_1127_li
#Use HMAC for authenticating remote LOB id's, removing the need for maintaining a cache, and removing the limit on the number of LOBs per result set.
#Use HMAC for authenticating remote LOB id's, removing the need for maintaining a cache, and removing the limit on the number of LOBs per result set.
@changelog_1124_li
@changelog_1128_li
#H2 Console: HTML and XML documents can now be edited in an updatable result set. There is (limited) support for editing multi-line documents.
#H2 Console: HTML and XML documents can now be edited in an updatable result set. There is (limited) support for editing multi-line documents.
@changelog_1125_h2
@changelog_1129_h2
#Version 1.3.167 (2012-05-23)
#Version 1.3.167 (2012-05-23)
@changelog_1126_li
@changelog_1130_li
#H2 Console: when editing a row, an empty varchar column was replaced with a single space.
#H2 Console: when editing a row, an empty varchar column was replaced with a single space.
@changelog_1127_li
@changelog_1131_li
#Lukas Eder has updated the jOOQ documentation.
#Lukas Eder has updated the jOOQ documentation.
@changelog_1128_li
@changelog_1132_li
#Some nested joins could not be executed, for example: select * from (select * from (select * from a) a right join b b) c;
#Some nested joins could not be executed, for example: select * from (select * from (select * from a) a right join b b) c;
@changelog_1129_li
@changelog_1133_li
#MS SQL Server compatibility: ISNULL is now an alias for IFNULL.
#MS SQL Server compatibility: ISNULL is now an alias for IFNULL.
@changelog_1130_li
@changelog_1134_li
#Terrence Huang has completed the translation of the H2 Console tool to Chinese. Thanks a lot!
#Terrence Huang has completed the translation of the H2 Console tool to Chinese. Thanks a lot!
@changelog_1131_li
@changelog_1135_li
#Server mode: the number of CLOB / BLOB values that were cached on the server is now the maximum of: 5 times the SERVER_RESULT_SET_FETCH_SIZE (which is 100 by default), and SysProperties.SERVER_CACHED_OBJECTS.
#Server mode: the number of CLOB / BLOB values that were cached on the server is now the maximum of: 5 times the SERVER_RESULT_SET_FETCH_SIZE (which is 100 by default), and SysProperties.SERVER_CACHED_OBJECTS.
@changelog_1132_li
@changelog_1136_li
#In the trace file, the query execution time was incorrect in some cases, specially for the statement SET TRACE_LEVEL_FILE 2.
#In the trace file, the query execution time was incorrect in some cases, specially for the statement SET TRACE_LEVEL_FILE 2.
@changelog_1133_li
@changelog_1137_li
#The feature LOG_SIZE_LIMIT that was introduced in version 1.3.165 did not always work correctly (specially with regards to multithreading) and has been removed. The message "Transaction log could not be truncated" is still written to the .trace.db file if required.
#The feature LOG_SIZE_LIMIT that was introduced in version 1.3.165 did not always work correctly (specially with regards to multithreading) and has been removed. The message "Transaction log could not be truncated" is still written to the .trace.db file if required.
@changelog_1134_li
@changelog_1138_li
#Then reading from a resource using the prefix "classpath:", the ContextClassLoader is now used if the resource can't be read otherwise.
#Then reading from a resource using the prefix "classpath:", the ContextClassLoader is now used if the resource can't be read otherwise.
@changelog_1135_li
@changelog_1139_li
#DatabaseEventListener now calls setProgress whenever a statement starts and ends.
#DatabaseEventListener now calls setProgress whenever a statement starts and ends.
@changelog_1136_li
@changelog_1140_li
#DatabaseEventListener now calls setProgress periodically while a statement is running.
#DatabaseEventListener now calls setProgress periodically while a statement is running.
@changelog_1137_li
@changelog_1141_li
#The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME.
#The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME.
@changelog_1138_li
@changelog_1142_li
#Issue 378: when using views, the wrong values were bound to a parameter in some cases.
#Issue 378: when using views, the wrong values were bound to a parameter in some cases.
@changelog_1139_li
@changelog_1143_li
#Terrence Huang has translated the error messages to Chinese. Thanks a lot!
#Terrence Huang has translated the error messages to Chinese. Thanks a lot!
@changelog_1140_li
@changelog_1144_li
#TRUNC was added as an alias for TRUNCATE.
#TRUNC was added as an alias for TRUNCATE.
@changelog_1141_li
@changelog_1145_li
#Small optimisation for accessing result values by column name.
#Small optimisation for accessing result values by column name.
@changelog_1142_li
@changelog_1146_li
#Fix for bug in Statement.getMoreResults(int)
#Fix for bug in Statement.getMoreResults(int)
@changelog_1143_li
@changelog_1147_li
#The SCRIPT statements now supports filtering by schema and table. Thanks a lot to Jacob Qvortrup for providing the patch!
#The SCRIPT statements now supports filtering by schema and table. Thanks a lot to Jacob Qvortrup for providing the patch!
@changelog_1144_h2
@changelog_1148_h2
#Version 1.3.166 (2012-04-08)
#Version 1.3.166 (2012-04-08)
@changelog_1145_li
@changelog_1149_li
#Indexes on column that are larger than half the page size (wide indexes) could sometimes get corrupt, resulting in an ArrayIndexOutOfBoundsException in PageBtree.getRow or "Row not found" in PageBtreeLeaf. Also, such indexes used too much disk space.
#Indexes on column that are larger than half the page size (wide indexes) could sometimes get corrupt, resulting in an ArrayIndexOutOfBoundsException in PageBtree.getRow or "Row not found" in PageBtreeLeaf. Also, such indexes used too much disk space.
@changelog_1146_li
@changelog_1150_li
#Server mode: when retrieving more than 64 rows each containing a CLOB or BLOB, the error message "The object is already closed" was thrown.
#Server mode: when retrieving more than 64 rows each containing a CLOB or BLOB, the error message "The object is already closed" was thrown.
@changelog_1147_li
@changelog_1151_li
#ConvertTraceFile: the time in the trace file is now parsed as a long.
#ConvertTraceFile: the time in the trace file is now parsed as a long.
@changelog_1148_li
@changelog_1152_li
#Invalid connection settings are now detected.
#Invalid connection settings are now detected.
@changelog_1149_li
@changelog_1153_li
#Issue 387: WHERE condition getting pushed into sub-query with LIMIT.
#Issue 387: WHERE condition getting pushed into sub-query with LIMIT.
@changelog_1150_h2
@changelog_1154_h2
#Version 1.3.165 (2012-03-18)
#Version 1.3.165 (2012-03-18)
@changelog_1151_li
@changelog_1155_li
#Better string representation for decimal values (for example 0.00000000 instead of 0E-26).
#Better string representation for decimal values (for example 0.00000000 instead of 0E-26).
@changelog_1152_li
@changelog_1156_li
#Prepared statements could only be re-used if the same data types were used the second time they were executed.
#Prepared statements could only be re-used if the same data types were used the second time they were executed.
@changelog_1153_li
@changelog_1157_li
#In error messages about referential constraint violation, the values are now included.
#In error messages about referential constraint violation, the values are now included.
@changelog_1154_li
@changelog_1158_li
#SCRIPT and RUNSCRIPT: the password can now be set using a prepared statement. Previously, it was required to be a literal in the SQL statement.
#SCRIPT and RUNSCRIPT: the password can now be set using a prepared statement. Previously, it was required to be a literal in the SQL statement.
@changelog_1155_li
@changelog_1159_li
#MySQL compatibility: SUBSTR with a negative start index now works like MySQL.
#MySQL compatibility: SUBSTR with a negative start index now works like MySQL.
@changelog_1156_li
@changelog_1160_li
#When enabling autocommit, the transaction is now committed (as required by the JDBC API).
#When enabling autocommit, the transaction is now committed (as required by the JDBC API).
@changelog_1157_li
@changelog_1161_li
#The shell script <code>h2.sh</code> did not work with spaces in the path. It also works now with quoted spaces in the argument list. Thanks a lot to Shimizu Fumiyuki for the patch!
#The shell script <code>h2.sh</code> did not work with spaces in the path. It also works now with quoted spaces in the argument list. Thanks a lot to Shimizu Fumiyuki for the patch!
@changelog_1158_li
@changelog_1162_li
#If the transaction log could not be truncated because of an uncommitted transaction, now "Transaction log could not be truncated" is written to the .trace.db file. Before, the database file was growing and it was hard to find out what the root cause was. To avoid the database file from growing, a new feature to automatically rollback the oldest transaction is available now. To enable it, append ;LOG_SIZE_LIMIT=32 to the database URL (in that case, the oldest session is rolled back if the transaction log is 32 MB).
#If the transaction log could not be truncated because of an uncommitted transaction, now "Transaction log could not be truncated" is written to the .trace.db file. Before, the database file was growing and it was hard to find out what the root cause was. To avoid the database file from growing, a new feature to automatically rollback the oldest transaction is available now. To enable it, append ;LOG_SIZE_LIMIT=32 to the database URL (in that case, the oldest session is rolled back if the transaction log is 32 MB).
@changelog_1159_li
@changelog_1163_li
#ALTER TABLE ADD can now add more than one column at a time.
#ALTER TABLE ADD can now add more than one column at a time.
@changelog_1160_li
@changelog_1164_li
#Issue 380: ALTER TABLE ADD FOREIGN KEY with an explicit index didn't verify the index can be used, which would lead to a NullPointerException later on.
#Issue 380: ALTER TABLE ADD FOREIGN KEY with an explicit index didn't verify the index can be used, which would lead to a NullPointerException later on.
@changelog_1161_li
@changelog_1165_li
#Issue 384: the wrong kind of exception (NullPointerException) was thrown in a UNION query with an incorrect ORDER BY expression.
#Issue 384: the wrong kind of exception (NullPointerException) was thrown in a UNION query with an incorrect ORDER BY expression.
@changelog_1162_li
@changelog_1166_li
#Issue 362: support LIMIT in UPDATE statements.
#Issue 362: support LIMIT in UPDATE statements.
@changelog_1163_li
@changelog_1167_li
#Browser: if no default browser is set, Google Chrome is now used if available. If not available, then Konqueror, Netscape, or Opera is used if available (as before).
#Browser: if no default browser is set, Google Chrome is now used if available. If not available, then Konqueror, Netscape, or Opera is used if available (as before).
@changelog_1164_li
@changelog_1168_li
#CSV tool: new feature to disable writing the column header (option writeColumnHeader).
#CSV tool: new feature to disable writing the column header (option writeColumnHeader).
@changelog_1165_li
@changelog_1169_li
#CSV tool: new feature to preserve the case sensitivity of column names (option caseSensitiveColumnNames).
#CSV tool: new feature to preserve the case sensitivity of column names (option caseSensitiveColumnNames).
@changelog_1166_li
@changelog_1170_li
#PostgreSQL compatibility: LOG(x) is base 10 in the PostgreSQL mode.
#PostgreSQL compatibility: LOG(x) is base 10 in the PostgreSQL mode.
@changelog_1167_h2
@changelog_1171_h2
#Version 1.3.164 (2012-02-03)
#Version 1.3.164 (2012-02-03)
@changelog_1168_li
@changelog_1172_li
#New built-in function ARRAY_CONTAINS.
#New built-in function ARRAY_CONTAINS.
@changelog_1169_li
@changelog_1173_li
#Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
#Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
@changelog_1170_li
@changelog_1174_li
#Trying to convert a VARCHAR to UUID will now fail if the text contains a character that is not a hex digit, '-', or not a whitespace.
#Trying to convert a VARCHAR to UUID will now fail if the text contains a character that is not a hex digit, '-', or not a whitespace.
@changelog_1171_li
@changelog_1175_li
#TriggerAdapter: in "before" triggers, values can be changed using the ResultSet.updateX methods.
#TriggerAdapter: in "before" triggers, values can be changed using the ResultSet.updateX methods.
@changelog_1172_li
@changelog_1176_li
#Creating a table with column data type NULL now works (even if not very useful).
#Creating a table with column data type NULL now works (even if not very useful).
@changelog_1173_li
@changelog_1177_li
#ALTER TABLE ALTER COLUMN no longer copies the data for widening conversions (for example if only the precision was increased) unless necessary.
#ALTER TABLE ALTER COLUMN no longer copies the data for widening conversions (for example if only the precision was increased) unless necessary.
@changelog_1174_li
@changelog_1178_li
#Multi-threaded kernel: concurrently running an online backup and updating the database resulted in a broken (transactionally incorrect) backup file in some cases.
#Multi-threaded kernel: concurrently running an online backup and updating the database resulted in a broken (transactionally incorrect) backup file in some cases.
@changelog_1175_li
@changelog_1179_li
#The script created by SCRIPT DROP did not always work if multiple views existed that depend on each other.
#The script created by SCRIPT DROP did not always work if multiple views existed that depend on each other.
@changelog_1176_li
@changelog_1180_li
#MathUtils.getSecureRandom could log a warning to System.err in case the /dev/random is very slow, and the System.getProperties().toString() returned a string larger than 64 KB.
#MathUtils.getSecureRandom could log a warning to System.err in case the /dev/random is very slow, and the System.getProperties().toString() returned a string larger than 64 KB.
@changelog_1177_li
@changelog_1181_li
#The database file locking mechanism "FS" (;FILE_LOCK=FS) did not work on Linux since version 1.3.161.
#The database file locking mechanism "FS" (;FILE_LOCK=FS) did not work on Linux since version 1.3.161.
@changelog_1178_li
@changelog_1182_li
#Sequences: the functions NEXTVAL and CURRVAL did not work as expected when using quoted, mixed case sequence names.
#Sequences: the functions NEXTVAL and CURRVAL did not work as expected when using quoted, mixed case sequence names.
@changelog_1179_li
@changelog_1183_li
#The constructor for Csv objects is now public, and Csv.getInstance() is now deprecated.
#The constructor for Csv objects is now public, and Csv.getInstance() is now deprecated.
@changelog_1180_li
@changelog_1184_li
#SimpleResultSet: updating a result set is now supported.
#SimpleResultSet: updating a result set is now supported.
@changelog_1181_li
@changelog_1185_li
#Database URL: extra semicolons are not supported.
#Database URL: extra semicolons are not supported.
@changelog_1182_h2
@changelog_1186_h2
#Version 1.3.163 (2011-12-30)
#Version 1.3.163 (2011-12-30)
@changelog_1183_li
@changelog_1187_li
#On out of disk space, the database could get corrupt sometimes, if later write operations succeeded. The same problem happened on other kinds of I/O exceptions (where one or some of the writes fail, but subsequent writes succeed). Now the file is closed on the first unsuccessful write operation, so that later requests fail consistently.
#On out of disk space, the database could get corrupt sometimes, if later write operations succeeded. The same problem happened on other kinds of I/O exceptions (where one or some of the writes fail, but subsequent writes succeed). Now the file is closed on the first unsuccessful write operation, so that later requests fail consistently.
@changelog_1184_li
@changelog_1188_li
#DatabaseEventListener.diskSpaceIsLow() is no longer supported because it can't be guaranteed that it always works correctly.
#DatabaseEventListener.diskSpaceIsLow() is no longer supported because it can't be guaranteed that it always works correctly.
@changelog_1185_li
@changelog_1189_li
#XMLTEXT now supports an optional parameter to escape newlines.
#XMLTEXT now supports an optional parameter to escape newlines.
@changelog_1186_li
@changelog_1190_li
#XMLNODE now support an optional parameter to disable indentation.
#XMLNODE now support an optional parameter to disable indentation.
@changelog_1187_li
@changelog_1191_li
#Csv.write now formats date, time, and timestamp values using java.sql.Date / Time / Timestamp.toString(). Previously, ResultSet.getString() was used, which didn't work well for Oracle.
#Csv.write now formats date, time, and timestamp values using java.sql.Date / Time / Timestamp.toString(). Previously, ResultSet.getString() was used, which didn't work well for Oracle.
@changelog_1188_li
@changelog_1192_li
#The shell script <code>h2.sh</code> can now be run from within a different directory. Thanks a lot to Daniel Serodio for the patch!
#The shell script <code>h2.sh</code> can now be run from within a different directory. Thanks a lot to Daniel Serodio for the patch!
@changelog_1189_li
@changelog_1193_li
#The page size of a persistent database can now be queries using: select * from information_schema.settings where name = 'info.PAGE_SIZE'
#The page size of a persistent database can now be queries using: select * from information_schema.settings where name = 'info.PAGE_SIZE'
@changelog_1190_li
@changelog_1194_li
#In the server mode, BLOB and CLOB objects are no longer closed when the result set is closed (as required by the JDBC spec).
#In the server mode, BLOB and CLOB objects are no longer closed when the result set is closed (as required by the JDBC spec).
@cheatSheet_1000_h1
@cheatSheet_1000_h1
...
@@ -7148,51 +7160,48 @@ H2 データベース エンジン
...
@@ -7148,51 +7160,48 @@ H2 データベース エンジン
# The plan is to use the MVStore as the default storage engine for the H2 database in the future (supporting SQL, JDBC, transactions, MVCC, and so on). This is work in progress. To try it out, append <code>;DEFAULT_TABLE_ENGINE=org.h2.mvstore.db.MVTableEngine</code> to the database URL. In general, functionality and performance should be similar than the current default storage engine (the page store). There are a few features that have not been implemented yet or are not complete:
# The plan is to use the MVStore as the default storage engine for the H2 database in the future (supporting SQL, JDBC, transactions, MVCC, and so on). This is work in progress. To try it out, append <code>;DEFAULT_TABLE_ENGINE=org.h2.mvstore.db.MVTableEngine</code> to the database URL. In general, functionality and performance should be similar than the current default storage engine (the page store). There are a few features that have not been implemented yet or are not complete:
@mvstore_1111_li
@mvstore_1111_li
#Changing the cache size.
#Changing the cache size is currently not supported.
@mvstore_1112_li
@mvstore_1112_li
#Two-phase commit.
#The database metadata is still stored in a <code>.h2.db</code> file, and the <code>.lock.db</code> file is still used to lock a database (long term, the plan is to no longer use those files).
@mvstore_1113_li
@mvstore_1113_li
#The database metadata is still stored in a <code>.h2.db</code> file.
@mvstore_1114_li
#The database file(s) sometimes do not shrink as expected.
#The database file(s) sometimes do not shrink as expected.
@mvstore_1115_h2
@mvstore_1114_h2
#Similar Projects and Differences to Other Storage Engines #必�?�?�件
#Similar Projects and Differences to Other Storage Engines
@mvstore_1116_p
@mvstore_1115_p
# Unlike similar storage engines like LevelDB and Kyoto Cabinet, the MVStore is written in Java and can easily be embedded in a Java and Android application.
# Unlike similar storage engines like LevelDB and Kyoto Cabinet, the MVStore is written in Java and can easily be embedded in a Java and Android application.
@mvstore_1117_p
@mvstore_1116_p
# The MVStore is somewhat similar to the Berkeley DB Java Edition because it is also written in Java, and is also a log structured storage, but the H2 license is more liberal.
# The MVStore is somewhat similar to the Berkeley DB Java Edition because it is also written in Java, and is also a log structured storage, but the H2 license is more liberal.
@mvstore_1118_p
@mvstore_1117_p
# Like SQLite, the MVStore keeps all data in one file. Unlike SQLite, the MVStore uses is a log structured storage. The plan is to make the MVStore both easier to use as well as faster than SQLite. In a recent (very simple) test, the MVStore was about twice as fast as SQLite on Android.
# Like SQLite, the MVStore keeps all data in one file. Unlike SQLite, the MVStore uses is a log structured storage. The plan is to make the MVStore both easier to use as well as faster than SQLite. In a recent (very simple) test, the MVStore was about twice as fast as SQLite on Android.
@mvstore_1119_p
@mvstore_1118_p
# The API of the MVStore is similar to MapDB (previously known as JDBM) from Jan Kotek, and some code is shared between MapDB and JDBM. However, unlike MapDB, the MVStore uses is a log structured storage. The MVStore does not have a record size limit.
# The API of the MVStore is similar to MapDB (previously known as JDBM) from Jan Kotek, and some code is shared between MapDB and JDBM. However, unlike MapDB, the MVStore uses is a log structured storage. The MVStore does not have a record size limit.
@mvstore_1120_h2
@mvstore_1119_h2
#Current State
#Current State
@mvstore_1121_p
@mvstore_1120_p
# The code is still experimental at this stage. The API as well as the behavior may partially change. Features may be added and removed (even thought the main features will stay).
# The code is still experimental at this stage. The API as well as the behavior may partially change. Features may be added and removed (even thought the main features will stay).
@mvstore_1122_h2
@mvstore_1121_h2
必�?�?�件
必�?�?�件
@mvstore_1123_p
@mvstore_1122_p
# The MVStore is included in the latest H2 jar file.
# The MVStore is included in the latest H2 jar file.
@mvstore_1124_p
@mvstore_1123_p
# There are no special requirements to use it. The MVStore should run on any JVM as well as on Android.
# There are no special requirements to use it. The MVStore should run on any JVM as well as on Android.
@mvstore_1125_p
@mvstore_1124_p
# To build just the MVStore (without the database engine), run:
# To build just the MVStore (without the database engine), run:
@mvstore_1126_p
@mvstore_1125_p
# This will create the file <code>bin/h2mvstore-1.3.172.jar</code> (about 130 KB).
# This will create the file <code>bin/h2mvstore-1.3.172.jar</code> (about 130 KB).
@@ -399,7 +399,7 @@ advanced_1397_p=\ This database has the following known limitations\:
...
@@ -399,7 +399,7 @@ advanced_1397_p=\ This database has the following known limitations\:
advanced_1398_li=Database file size limit\:4 TB (using the default page size of 2 KB) or higher (when using a larger page size). This limit is including CLOB and BLOB data.
advanced_1398_li=Database file size limit\:4 TB (using the default page size of 2 KB) or higher (when using a larger page size). This limit is including CLOB and BLOB data.
advanced_1399_li=The maximum file size for FAT or FAT32 file systems is 4 GB. That means when using FAT or FAT32, the limit is 4 GB for the data. This is the limitation of the file system. The database does provide a workaround for this problem, it is to use the file name prefix <code>split\:</code>. In that case files are split into files of 1 GB by default. An example database URL is\:<code>jdbc\:h2\:split\:~/test</code>.
advanced_1399_li=The maximum file size for FAT or FAT32 file systems is 4 GB. That means when using FAT or FAT32, the limit is 4 GB for the data. This is the limitation of the file system. The database does provide a workaround for this problem, it is to use the file name prefix <code>split\:</code>. In that case files are split into files of 1 GB by default. An example database URL is\:<code>jdbc\:h2\:split\:~/test</code>.
advanced_1400_li=The maximum number of rows per table is 2^64.
advanced_1400_li=The maximum number of rows per table is 2^64.
advanced_1401_li=Main memory requirements\:The larger the database, the more main memory is required. With the version 1.1 storage mechanism, the minimum main memory required for a 12 GB database was around 240 MB. With the current page store, the minimum main memory required is much lower, around 1 MB for each 8 GB database file size.
advanced_1401_li=Main memory requirements\:The larger the database, the more main memory is required. With the current storage mechanism (the page store), the minimum main memory required is around 1 MB for each 8 GB database file size.
advanced_1402_li=Limit on the complexity of SQL statements. Statements of the following form will result in a stack overflow exception\:
advanced_1402_li=Limit on the complexity of SQL statements. Statements of the following form will result in a stack overflow exception\:
advanced_1403_li=There is no limit for the following entities, except the memory and storage capacity\:maximum identifier length (table name, column name, and so on); maximum number of tables, columns, indexes, triggers, and other database objects; maximum statement length, number of parameters per statement, tables per statement, expressions in order by, group by, having, and so on; maximum rows per query; maximum columns per table, columns per index, indexes per table, lob columns per table, and so on; maximum row length, index row length, select row length; maximum length of a varchar column, decimal column, literal in a statement.
advanced_1403_li=There is no limit for the following entities, except the memory and storage capacity\:maximum identifier length (table name, column name, and so on); maximum number of tables, columns, indexes, triggers, and other database objects; maximum statement length, number of parameters per statement, tables per statement, expressions in order by, group by, having, and so on; maximum rows per query; maximum columns per table, columns per index, indexes per table, lob columns per table, and so on; maximum row length, index row length, select row length; maximum length of a varchar column, decimal column, literal in a statement.
advanced_1404_li=Querying from the metadata tables is slow if there are many tables (thousands).
advanced_1404_li=Querying from the metadata tables is slow if there are many tables (thousands).
...
@@ -551,190 +551,194 @@ changelog_1003_li=Issue 463\: Driver name and version are now the same in OsgiDa
...
@@ -551,190 +551,194 @@ changelog_1003_li=Issue 463\: Driver name and version are now the same in OsgiDa
changelog_1004_li=JaQu\:The data type VARCHAR is now (again) used for Strings (no longer TEXT, except when explicitly set).
changelog_1004_li=JaQu\:The data type VARCHAR is now (again) used for Strings (no longer TEXT, except when explicitly set).
changelog_1005_li=For in-memory databases, creating an index on a CLOB or BLOB column is no longer supported. This is to simplify the MVTableEngine.
changelog_1005_li=For in-memory databases, creating an index on a CLOB or BLOB column is no longer supported. This is to simplify the MVTableEngine.
changelog_1007_li=Issue 468\:trunc(timestamp) could return the wrong value.
changelog_1007_li=Issue 468\:trunc(timestamp) could return the wrong value (+12 hours), and trunc(number) throw a NullPointerException.
changelog_1008_li=Fixed a deadlock when updating LOB's concurrently. See TestLob.testDeadlock2().
changelog_1008_li=The expression trunc(number) threw a NullPointerException.
changelog_1009_li=Fixed a deadlock related to very large temporary result sets.
changelog_1009_li=Fixed a deadlock when updating LOB's concurrently. See TestLob.testDeadlock2().
changelog_1010_li=Add "-list" command line option to Shell tool so that result-list-mode can be triggered when reading from a file.
changelog_1010_li=Fixed a deadlock related to very large temporary result sets.
changelog_1011_li=Issue 474\:H2 Mysql Compatibility code fails to ignore "COMMENT" in CREATE TABLE, patch from Aaron Azeckoski.
changelog_1011_li=Add "-list" command line option to Shell tool so that result-list-mode can be triggered when reading from a file.
changelog_1012_li=Issue 476\:Broken link in jaqu.html
changelog_1012_li=Issue 474\:H2 MySQL Compatibility code fails to ignore "COMMENT" in CREATE TABLE, patch from Aaron Azeckoski.
changelog_1013_li=Fix potential UTF8 encoding issue in org.h2.store.FileStore, reported by Juerg Spiess.
changelog_1013_li=Issue 476\:Broken link in jaqu.html
changelog_1014_li=Improve error message when check constraint is broken, test case from Gili (cowwoc).
changelog_1014_li=Fix potential UTF8 encoding issue in org.h2.store.FileStore, reported by Juerg Spiess.
changelog_1015_li=Improve error message when we have a unique constraint violation, displays the offending key in the error message.
changelog_1015_li=Improve error message when check constraint is broken, test case from Gili (cowwoc).
changelog_1016_li=Issue 478\:Support for "SHOW TRANSACTION ISOLATION LEVEL", patch from Andrew Franklin.
changelog_1016_li=Improve error message when we have a unique constraint violation, displays the offending key in the error message.
changelog_1017_li=Issue 475\:PgServer\:add support for CancelRequest, patch from Andrew Franklin.
changelog_1017_li=Issue 478\:Support for "SHOW TRANSACTION ISOLATION LEVEL", patch from Andrew Franklin.
changelog_1018_li=Issue 473\:PgServer missing -key option, patch from Andrew Franklin.
changelog_1018_li=Issue 475\:PgServer\:add support for CancelRequest, patch from Andrew Franklin.
changelog_1019_li=Issue 471\:CREATE VIEW does not check user rights, patch from Andrew Franklin.
changelog_1019_li=Issue 473\:PgServer missing -key option, patch from Andrew Franklin.
changelog_1020_li=Issue 477\:PgServer binary transmission of query params is unimplemented, patch from Andrew Franklin.
changelog_1020_li=Issue 471\:CREATE VIEW does not check user rights, patch from Andrew Franklin.
changelog_1021_li=Issue 479\:Support for SUBSTRING without a FROM condition, patch from Andrew Franklin.
changelog_1021_li=Issue 477\:PgServer binary transmission of query params is unimplemented, patch from Andrew Franklin.
changelog_1022_li=Issue 472\:PgServer does not work with any recent Postgres JDBC driver, patch from Andrew Franklin.
changelog_1022_li=Issue 479\:Support for SUBSTRING without a FROM condition, patch from Andrew Franklin.
changelog_1023_li=Add syntax for passing additional parameters into custom TableEngine implementations.
changelog_1023_li=Issue 472\:PgServer does not work with any recent Postgres JDBC driver, patch from Andrew Franklin.
changelog_1024_li=Issue 480\:Bugfix post issue \#475, \#477, patch from Andrew Franklin.
changelog_1024_li=Add syntax for passing additional parameters into custom TableEngine implementations.
changelog_1025_li=Issue 481\:Further extensions to PgServer to support better support PG JDBC, patch from Andrew Franklin.
changelog_1025_li=Issue 480\:Bugfix post issue 475, 477, patch from Andrew Franklin.
changelog_1026_li=Add support for spatial datatype GEOMETRY.
changelog_1026_li=Issue 481\:Further extensions to PgServer to support better support PG JDBC, patch from Andrew Franklin.
changelog_1027_li=Add support for in-memory spatial index.
changelog_1027_li=Add support for spatial datatype GEOMETRY.
changelog_1028_li=change the PageStore\#changeCount field from an int to a long, to cope with databases with very high transaction rates.
changelog_1028_li=Add support for in-memory spatial index.
changelog_1029_h2=Version 1.3.172 (2013-05-25)
changelog_1029_li=change the PageStore\#changeCount field from an int to a long, to cope with databases with very high transaction rates.
changelog_1030_li=Referential integrity\:when adding a referential integrity constraint failed, and if creating the constraint automatically created an index, this index was not removed.
changelog_1030_li=Fix a NullPointerException when attempting to add foreign key reference to a view.
changelog_1031_li=The auto-analyze feature now only reads 1000 rows per table instead of 10000.
changelog_1031_li=Add sufficient ClientInfo support to our javax.sql.Connection implementation to make WebSphere happy.
changelog_1032_li=The optimization for IN(...) queries combined with OR could result in a strange exception of the type "column x must be included in the group by list".
changelog_1032_li=Issue 482\:class LobStorageBackend$LobInputStream does not override the method InputStream.available().
changelog_1033_li=Issue 454\:Use Charset for type-safety.
changelog_1033_h2=Version 1.3.172 (2013-05-25)
changelog_1034_li=Queries with both LIMIT and OFFSET could throw an IllegalArgumentException.
changelog_1034_li=Referential integrity\:when adding a referential integrity constraint failed, and if creating the constraint automatically created an index, this index was not removed.
changelog_1035_li=MVStore\:multiple issues were fixed\:460, 461, 462, 464, 466.
changelog_1035_li=The auto-analyze feature now only reads 1000 rows per table instead of 10000.
changelog_1036_li=MVStore\:larger stores (multiple GB) are now much faster.
changelog_1036_li=The optimization for IN(...) queries combined with OR could result in a strange exception of the type "column x must be included in the group by list".
changelog_1037_li=When using local temporary tables and not dropping them manually before closing the session, and then killing the process could result in a database that couldn't be opened (except when using the recover tool).
changelog_1037_li=Issue 454\:Use Charset for type-safety.
changelog_1038_li=Support TRUNC(timestamp) for improved Oracle compatibility.
changelog_1038_li=Queries with both LIMIT and OFFSET could throw an IllegalArgumentException.
changelog_1039_li=Add support for CREATE TABLE TEST (ID BIGSERIAL) for PostgreSQL compatibility. Patch from Jesse Long.
changelog_1039_li=MVStore\:multiple issues were fixed\:460, 461, 462, 464, 466.
changelog_1040_li=Add new collation command SET BINARY_COLLATION UNSIGNED, helps with people testing BINARY columns in MySQL mode.
changelog_1040_li=MVStore\:larger stores (multiple GB) are now much faster.
changelog_1041_li=Issue 453\:ABBA race conditions in TABLE LINK connection sharing.
changelog_1041_li=When using local temporary tables and not dropping them manually before closing the session, and then killing the process could result in a database that couldn't be opened (except when using the recover tool).
changelog_1042_li=Issue 449\:Postgres Serial data type should not automatically be marked as primary key
changelog_1042_li=Support TRUNC(timestamp) for improved Oracle compatibility.
changelog_1051_li=Issue 274\:Sybase/MSSQLServer compatibility - swap parameters of CONVERT function.
changelog_1052_h2=Version 1.3.171 (2013-03-17)
changelog_1052_li=Issue 274\:Sybase/MSSQLServer compatibility - support index clause e.g. "select * from test (index table1_index)"
changelog_1053_li=Security\:the TCP server did not correctly restrict access rights of clients in some cases. This was specially a problem when using the flag "tcpAllowOthers".
changelog_1053_li=Fix bug in Optimizing SELECT * FROM A WHERE X\=1 OR X\=2 OR X\=3 into SELECT * FROM A WHERE X IN (1,2,3)
changelog_1054_li=H2 Console\:the session timeout can now be configured using the system property "h2.consoleTimeout".
changelog_1054_li=Issue 442\:Groovy patch for SourceCompiler (function ALIAS)
changelog_1055_li=Issue 431\:Improved compatibility with MySQL\:support for "ENGINE\=InnoDB charset\=UTF8" when creating a table.
changelog_1056_li=Issue 249\:Improved compatibility with MySQL in the MySQL mode\:now the methods DatabaseMetaData methods stores*Case*Identifiers return the same as MySQL when using the MySQL mode.
changelog_1056_h2=Version 1.3.171 (2013-03-17)
changelog_1057_li=Issue 434\:H2 Console didn't work in the Chrome browser due to a wrong viewport argument.
changelog_1057_li=Security\:the TCP server did not correctly restrict access rights of clients in some cases. This was specially a problem when using the flag "tcpAllowOthers".
changelog_1058_li=There was a possibility that the .lock.db file was not deleted when the database was closed, which could slow down opening the database.
changelog_1058_li=H2 Console\:the session timeout can now be configured using the system property "h2.consoleTimeout".
changelog_1059_li=The SQL script generated by the "script" command contained inconsistent newlines on Windows.
changelog_1059_li=Issue 431\:Improved compatibility with MySQL\:support for "ENGINE\=InnoDB charset\=UTF8" when creating a table.
changelog_1060_li=When using trace level 4 (SLF4J) in the server mode, a directory "trace.db" and an empty file was created on the client side. This is no longer made.
changelog_1060_li=Issue 249\:Improved compatibility with MySQL in the MySQL mode\:now the methods DatabaseMetaData methods stores*Case*Identifiers return the same as MySQL when using the MySQL mode.
changelog_1061_li=Optimize IN(...) queries\:there was a bug in version 1.3.170 if the type of the left hand side didn't match the type of the right hand side. Fixed.
changelog_1061_li=Issue 434\:H2 Console didn't work in the Chrome browser due to a wrong viewport argument.
changelog_1062_li=Optimize IN(...) queries\:there was a bug in version 1.3.170 for comparison of the type "X IN(NULL, NULL)". Fixed.
changelog_1062_li=There was a possibility that the .lock.db file was not deleted when the database was closed, which could slow down opening the database.
changelog_1063_li=Timestamps with timezone that were passed as a string were not always converted correctly. For example "2012-11-06T23\:00\:00.000Z" was converted to "2012-11-06" instead of to "2012-11-07" in the timezone CET. Thanks a lot to Steve Hruda for reporting the problem\!
changelog_1063_li=The SQL script generated by the "script" command contained inconsistent newlines on Windows.
changelog_1064_li=New table engine "org.h2.mvstore.db.MVTableEngine" that internally uses the MVStore to persist data. To try it out, append ";DEFAULT_TABLE_ENGINE\=org.h2.mvstore.db.MVTableEngine" to the database URL. This is still very experimental, and many features are not supported yet. The data is stored in a file with the suffix ".mv.db".
changelog_1064_li=When using trace level 4 (SLF4J) in the server mode, a directory "trace.db" and an empty file was created on the client side. This is no longer made.
changelog_1065_li=New connection setting "DEFAULT_TABLE_ENGINE" to use a specific table engine if none is set explicitly. This is to simplify testing the MVStore table engine.
changelog_1065_li=Optimize IN(...) queries\:there was a bug in version 1.3.170 if the type of the left hand side didn't match the type of the right hand side. Fixed.
changelog_1066_li=MVStore\:encrypted stores are now supported. Only standardized algorithms are used\:PBKDF2, SHA-256, XTS-AES, AES-128.
changelog_1066_li=Optimize IN(...) queries\:there was a bug in version 1.3.170 for comparison of the type "X IN(NULL, NULL)". Fixed.
changelog_1067_li=MVStore\:improved API thanks to Simo Tripodi.
changelog_1067_li=Timestamps with timezone that were passed as a string were not always converted correctly. For example "2012-11-06T23\:00\:00.000Z" was converted to "2012-11-06" instead of to "2012-11-07" in the timezone CET. Thanks a lot to Steve Hruda for reporting the problem\!
changelog_1068_li=MVStore\:maps can now be renamed.
changelog_1068_li=New table engine "org.h2.mvstore.db.MVTableEngine" that internally uses the MVStore to persist data. To try it out, append ";DEFAULT_TABLE_ENGINE\=org.h2.mvstore.db.MVTableEngine" to the database URL. This is still very experimental, and many features are not supported yet. The data is stored in a file with the suffix ".mv.db".
changelog_1069_li=MVStore\:store the file header also at the end of each chunk, which results in a further reduced number of write operations.
changelog_1069_li=New connection setting "DEFAULT_TABLE_ENGINE" to use a specific table engine if none is set explicitly. This is to simplify testing the MVStore table engine.
changelog_1070_li=MVStore\:a map implementation that supports concurrent operations.
changelog_1070_li=MVStore\:encrypted stores are now supported. Only standardized algorithms are used\:PBKDF2, SHA-256, XTS-AES, AES-128.
changelog_1071_li=MVStore\:unified exception handling; the version is included in the messages.
changelog_1071_li=MVStore\:improved API thanks to Simo Tripodi.
changelog_1072_li=MVStore\:old data is now retained for 45 seconds by default.
changelog_1072_li=MVStore\:maps can now be renamed.
changelog_1073_li=MVStore\:compress is now disabled by default, and can be enabled on request.
changelog_1073_li=MVStore\:store the file header also at the end of each chunk, which results in a further reduced number of write operations.
changelog_1074_li=Support ALTER TABLE ADD ... AFTER. Patch from Andrew Gaul (argaul at gmail.com). Fixes issue 401.
changelog_1074_li=MVStore\:a map implementation that supports concurrent operations.
changelog_1075_li=Improved OSGi support. H2 now registers itself as a DataSourceFactory service. Fixes issue 365.
changelog_1075_li=MVStore\:unified exception handling; the version is included in the messages.
changelog_1076_li=Add a DISK_SPACE_USED system function. Fixes issue 270.
changelog_1076_li=MVStore\:old data is now retained for 45 seconds by default.
changelog_1077_li=Fix a compile-time ambiguity when compiling with JDK7, thanks to a patch from Lukas Eder.
changelog_1077_li=MVStore\:compress is now disabled by default, and can be enabled on request.
changelog_1078_li=Supporting dropping an index for Lucene full-text indexes.
changelog_1078_li=Support ALTER TABLE ADD ... AFTER. Patch from Andrew Gaul (argaul at gmail.com). Fixes issue 401.
changelog_1079_li=Optimized performance for SELECT ... ORDER BY X LIMIT Y OFFSET Z queries for in-memory databases using partial sort (by Sergi Vladykin).
changelog_1079_li=Improved OSGi support. H2 now registers itself as a DataSourceFactory service. Fixes issue 365.
changelog_1080_li=Experimental off-heap memory storage engine "nioMemFS\:" and "nioMemLZF\:", suggestion from Mark Addleman.
changelog_1080_li=Add a DISK_SPACE_USED system function. Fixes issue 270.
changelog_1081_li=Issue 438\: JdbcDatabaseMetaData.getSchemas() is no longer supported as of 1.3.169.
changelog_1081_li=Fix a compile-time ambiguity when compiling with JDK7, thanks to a patch from Lukas Eder.
changelog_1082_li=MySQL compatibility\: support for ALTER TABLE tableName MODIFY [COLUMN] columnName columnDef. Patch from Ville Koskela.
changelog_1082_li=Supporting dropping an index for Lucene full-text indexes.
changelog_1083_li=Issue 404\: SHOW COLUMNS FROM tableName does not work with ALLOW_LITERALS\=NUMBERS.
changelog_1083_li=Optimized performance for SELECT ... ORDER BY X LIMIT Y OFFSET Z queries for in-memory databases using partial sort (by Sergi Vladykin).
changelog_1084_li=Throw an explicit error to make it clear we don't support the TRIGGER combination of SELECT and FOR EACH ROW.
changelog_1084_li=Experimental off-heap memory storage engine "nioMemFS\:" and "nioMemLZF\:", suggestion from Mark Addleman.
changelog_1085_li=Issue 439\: Utils.sortTopN does not handle single-element arrays.
changelog_1085_li=Issue 438\: JdbcDatabaseMetaData.getSchemas() is no longer supported as of 1.3.169.
changelog_1086_h2=Version 1.3.170 (2012-11-30)
changelog_1086_li=MySQL compatibility\: support for ALTER TABLE tableName MODIFY [COLUMN] columnName columnDef. Patch from Ville Koskela.
changelog_1087_li=Issue 407\: The TriggerAdapter didn't work with CLOB and BLOB columns.
changelog_1087_li=Issue 404\: SHOW COLUMNS FROM tableName does not work with ALLOW_LITERALS\=NUMBERS.
changelog_1088_li=PostgreSQL compatibility\: support for data types BIGSERIAL and SERIAL as an alias for AUTO_INCREMENT.
changelog_1088_li=Throw an explicit error to make it clear we don't support the TRIGGER combination of SELECT and FOR EACH ROW.
changelog_1089_li=Issue 417\: H2 Console\: the web session timeout didn't work, resulting in a memory leak. This was only a problem if the H2 Console was run for a long time and many sessions were opened.
changelog_1089_li=Issue 439\: Utils.sortTopN does not handle single-element arrays.
changelog_1090_li=Issue 412\: Running the Server tool with just the option "-browser" will now log a warning.
changelog_1090_h2=Version 1.3.170 (2012-11-30)
changelog_1091_li=Issue 411\:CloseWatcher registration was not concurrency-safe.
changelog_1091_li=Issue 407\: The TriggerAdapter didn't work with CLOB and BLOB columns.
changelog_1092_li=MySQL compatibility\:support for CONCAT_WS. Thanks a lot to litailang for the patch\!
changelog_1092_li=PostgreSQL compatibility\: support for data types BIGSERIAL and SERIAL as an alias for AUTO_INCREMENT.
changelog_1093_li=PostgreSQL compatibility\:support for EXTRACT(WEEK FROM dateColumn). Thanks to Prashant Bhat for the patch\!
changelog_1093_li=Issue 417\: H2 Console\: the web session timeout didn't work, resulting in a memory leak. This was only a problem if the H2 Console was run for a long time and many sessions were opened.
changelog_1094_li=Fix for a bug where we would sometimes use the wrong unique constraint to validate foreign key constraints.
changelog_1094_li=Issue 412\: Running the Server tool with just the option "-browser" will now log a warning.
changelog_1095_li=Support BOM at the beginning of files for the RUNSCRIPT command
changelog_1095_li=Issue 411\:CloseWatcher registration was not concurrency-safe.
changelog_1096_li=Fix in calling SET @X \=IDENTITY() where it would return NULL incorrectly
changelog_1096_li=MySQL compatibility\:support for CONCAT_WS. Thanks a lot to litailang for the patch\!
changelog_1097_li=Fix ABBA deadlock between adding a constraint and the H2-Log-Writer thread.
changelog_1097_li=PostgreSQL compatibility\:support for EXTRACT(WEEK FROM dateColumn). Thanks to Prashant Bhat for the patch\!
changelog_1098_li=Optimize IN(...) queries where the values are constant and of the same type.
changelog_1098_li=Fix for a bug where we would sometimes use the wrong unique constraint to validate foreign key constraints.
changelog_1099_li=Restore tool\:the parameter "quiet" was not used and is now removed.
changelog_1099_li=Support BOM at the beginning of files for the RUNSCRIPT command
changelog_1100_li=Fix ConcurrentModificationException when creating tables and executing SHOW TABLES in parallel. Reported by Viktor Voytovych.
changelog_1100_li=Fix in calling SET @X \=IDENTITY() where it would return NULL incorrectly
changelog_1101_li=Serialization is now pluggable using the system property "h2.javaObjectSerializer". Thanks to Sergi Vladykin for the patch\!
changelog_1101_li=Fix ABBA deadlock between adding a constraint and the H2-Log-Writer thread.
changelog_1102_h2=Version 1.3.169 (2012-09-09)
changelog_1102_li=Optimize IN(...) queries where the values are constant and of the same type.
changelog_1103_li=The default jar file is now compiled for Java 6.
changelog_1103_li=Restore tool\:the parameter "quiet" was not used and is now removed.
changelog_1104_li=The new jar file will probably not end up in the central Maven repository in the next few weeks because Sonatype has disabled automatic synchronization from SourceForge (which they call 'legacy sync' now). It will probably take some time until this is sorted out. The H2 jar files are deployed to http\://h2database.com/m2-repo/com/h2database/h2/maven-metadata.xml and http\://hsql.sourceforge.net/m2-repo/com/h2database/h2/maven-metadata.xml as usual.
changelog_1104_li=Fix ConcurrentModificationException when creating tables and executing SHOW TABLES in parallel. Reported by Viktor Voytovych.
changelog_1105_li=A part of the documentation and the H2 Console has been changed to support the Apple retina display.
changelog_1105_li=Serialization is now pluggable using the system property "h2.javaObjectSerializer". Thanks to Sergi Vladykin for the patch\!
changelog_1106_li=The CreateCluster tool could not be used if the source database contained a CLOB or BLOB. The root cause was that the TCP server did not synchronize on the session, which caused a problem when using the exclusive mode.
changelog_1106_h2=Version 1.3.169 (2012-09-09)
changelog_1107_li=Statement.getQueryTimeout()\:only the first call to this method will query the database. If the query timeout was changed in another way than calling setQueryTimeout, this method will always return the last value. This was changed because Hibernate calls getQueryTimeout() a lot.
changelog_1107_li=The default jar file is now compiled for Java 6.
changelog_1108_li=Issue 416\:PreparedStatement.setNString throws AbstractMethodError. All implemented JDBC 4 methods that don't break compatibility with Java 5 are now included in the default jar file.
changelog_1108_li=The new jar file will probably not end up in the central Maven repository in the next few weeks because Sonatype has disabled automatic synchronization from SourceForge (which they call 'legacy sync' now). It will probably take some time until this is sorted out. The H2 jar files are deployed to http\://h2database.com/m2-repo/com/h2database/h2/maven-metadata.xml and http\://hsql.sourceforge.net/m2-repo/com/h2database/h2/maven-metadata.xml as usual.
changelog_1109_li=Issue 414\:for some functions, the parameters were evaluated twice (for example "char(nextval(..))" ran "nextval(..)" twice).
changelog_1109_li=A part of the documentation and the H2 Console has been changed to support the Apple retina display.
changelog_1110_li=The ResultSetMetaData methods getSchemaName and getTableName could return null instead of "" (an empty string) as specified in the JDBC API.
changelog_1110_li=The CreateCluster tool could not be used if the source database contained a CLOB or BLOB. The root cause was that the TCP server did not synchronize on the session, which caused a problem when using the exclusive mode.
changelog_1111_li=Added compatibility for "SET NAMES" query in MySQL compatibility mode.
changelog_1111_li=Statement.getQueryTimeout()\:only the first call to this method will query the database. If the query timeout was changed in another way than calling setQueryTimeout, this method will always return the last value. This was changed because Hibernate calls getQueryTimeout() a lot.
changelog_1112_h2=Version 1.3.168 (2012-07-13)
changelog_1112_li=Issue 416\:PreparedStatement.setNString throws AbstractMethodError. All implemented JDBC 4 methods that don't break compatibility with Java 5 are now included in the default jar file.
changelog_1113_li=The message "Transaction log could not be truncated" was sometimes written to the .trace.db file even if there was no problem truncating the transaction log.
changelog_1113_li=Issue 414\:for some functions, the parameters were evaluated twice (for example "char(nextval(..))" ran "nextval(..)" twice).
changelog_1114_li=New system property "h2.serializeJavaObject" (default\:true) that allows to disable serializing Java objects, so that the objects compareTo and toString methods can be used.
changelog_1114_li=The ResultSetMetaData methods getSchemaName and getTableName could return null instead of "" (an empty string) as specified in the JDBC API.
changelog_1115_li=Dylan has translated the H2 Console tool to Korean. Thanks a lot\!
changelog_1115_li=Added compatibility for "SET NAMES" query in MySQL compatibility mode.
changelog_1116_li=Executing the statement CREATE INDEX IF ALREADY EXISTS if the index already exists no longer fails for a read only database.
changelog_1116_h2=Version 1.3.168 (2012-07-13)
changelog_1117_li=MVCC\:concurrently updating a row could result in the row to appear deleted in the second connection, if there are multiple unique indexes (or a primary key and at least one unique index). Thanks a lot to Teruo for the patch\!
changelog_1117_li=The message "Transaction log could not be truncated" was sometimes written to the .trace.db file even if there was no problem truncating the transaction log.
changelog_1118_li=Fulltext search\:in-memory Lucene indexes are now supported.
changelog_1118_li=New system property "h2.serializeJavaObject" (default\:true) that allows to disable serializing Java objects, so that the objects compareTo and toString methods can be used.
changelog_1119_li=Fulltext search\:UUID primary keys are now supported.
changelog_1119_li=Dylan has translated the H2 Console tool to Korean. Thanks a lot\!
changelog_1120_li=Apache Tomcat 7.x will now longer log a warning when unloading the web application, if using a connection pool.
changelog_1120_li=Executing the statement CREATE INDEX IF ALREADY EXISTS if the index already exists no longer fails for a read only database.
changelog_1121_li=H2 Console\:support the Midori browser (for Debian / Raspberry Pi)
changelog_1121_li=MVCC\:concurrently updating a row could result in the row to appear deleted in the second connection, if there are multiple unique indexes (or a primary key and at least one unique index). Thanks a lot to Teruo for the patch\!
changelog_1122_li=When opening a remote session, don't open a temporary file if the trace level is set to zero
changelog_1122_li=Fulltext search\:in-memory Lucene indexes are now supported.
changelog_1123_li=Use HMAC for authenticating remote LOB id's, removing the need for maintaining a cache, and removing the limit on the number of LOBs per result set.
changelog_1123_li=Fulltext search\:UUID primary keys are now supported.
changelog_1124_li=H2 Console\:HTML and XML documents can now be edited in an updatable result set. There is (limited) support for editing multi-line documents.
changelog_1124_li=Apache Tomcat 7.x will now longer log a warning when unloading the web application, if using a connection pool.
changelog_1125_h2=Version 1.3.167 (2012-05-23)
changelog_1125_li=H2 Console\:support the Midori browser (for Debian / Raspberry Pi)
changelog_1126_li=H2 Console\:when editing a row, an empty varchar column was replaced with a single space.
changelog_1126_li=When opening a remote session, don't open a temporary file if the trace level is set to zero
changelog_1127_li=Lukas Eder has updated the jOOQ documentation.
changelog_1127_li=Use HMAC for authenticating remote LOB id's, removing the need for maintaining a cache, and removing the limit on the number of LOBs per result set.
changelog_1128_li=Some nested joins could not be executed, for example\:select * from (select * from (select * from a) a right join b b) c;
changelog_1128_li=H2 Console\:HTML and XML documents can now be edited in an updatable result set. There is (limited) support for editing multi-line documents.
changelog_1129_li=MS SQL Server compatibility\:ISNULL is now an alias for IFNULL.
changelog_1129_h2=Version 1.3.167 (2012-05-23)
changelog_1130_li=Terrence Huang has completed the translation of the H2 Console tool to Chinese. Thanks a lot\!
changelog_1130_li=H2 Console\:when editing a row, an empty varchar column was replaced with a single space.
changelog_1131_li=Server mode\:the number of CLOB / BLOB values that were cached on the server is now the maximum of\:5 times the SERVER_RESULT_SET_FETCH_SIZE (which is 100 by default), and SysProperties.SERVER_CACHED_OBJECTS.
changelog_1131_li=Lukas Eder has updated the jOOQ documentation.
changelog_1132_li=In the trace file, the query execution time was incorrect in some cases, specially for the statement SET TRACE_LEVEL_FILE 2.
changelog_1132_li=Some nested joins could not be executed, for example\:select * from (select * from (select * from a) a right join b b) c;
changelog_1133_li=The feature LOG_SIZE_LIMIT that was introduced in version 1.3.165 did not always work correctly (specially with regards to multithreading) and has been removed. The message "Transaction log could not be truncated" is still written to the .trace.db file if required.
changelog_1133_li=MS SQL Server compatibility\:ISNULL is now an alias for IFNULL.
changelog_1134_li=Then reading from a resource using the prefix "classpath\:", the ContextClassLoader is now used if the resource can't be read otherwise.
changelog_1134_li=Terrence Huang has completed the translation of the H2 Console tool to Chinese. Thanks a lot\!
changelog_1135_li=DatabaseEventListener now calls setProgress whenever a statement starts and ends.
changelog_1135_li=Server mode\:the number of CLOB / BLOB values that were cached on the server is now the maximum of\:5 times the SERVER_RESULT_SET_FETCH_SIZE (which is 100 by default), and SysProperties.SERVER_CACHED_OBJECTS.
changelog_1136_li=DatabaseEventListener now calls setProgress periodically while a statement is running.
changelog_1136_li=In the trace file, the query execution time was incorrect in some cases, specially for the statement SET TRACE_LEVEL_FILE 2.
changelog_1137_li=The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME.
changelog_1137_li=The feature LOG_SIZE_LIMIT that was introduced in version 1.3.165 did not always work correctly (specially with regards to multithreading) and has been removed. The message "Transaction log could not be truncated" is still written to the .trace.db file if required.
changelog_1138_li=Issue 378\: when using views, the wrong values were bound to a parameter in some cases.
changelog_1138_li=Then reading from a resource using the prefix "classpath\:", the ContextClassLoader is now used if the resource can't be read otherwise.
changelog_1139_li=Terrence Huang has translated the error messages to Chinese. Thanks a lot\!
changelog_1139_li=DatabaseEventListener now calls setProgress whenever a statement starts and ends.
changelog_1140_li=TRUNC was added as an alias for TRUNCATE.
changelog_1140_li=DatabaseEventListener now calls setProgress periodically while a statement is running.
changelog_1141_li=Small optimisation for accessing result values by column name.
changelog_1141_li=The table INFORMATION_SCHEMA.FUNCTION_ALIASES now includes a column TYPE_NAME.
changelog_1142_li=Fix for bug in Statement.getMoreResults(int)
changelog_1142_li=Issue 378\: when using views, the wrong values were bound to a parameter in some cases.
changelog_1143_li=The SCRIPT statements now supports filtering by schema and table. Thanks a lot to Jacob Qvortrup for providing the patch\!
changelog_1143_li=Terrence Huang has translated the error messages to Chinese. Thanks a lot\!
changelog_1144_h2=Version 1.3.166 (2012-04-08)
changelog_1144_li=TRUNC was added as an alias for TRUNCATE.
changelog_1145_li=Indexes on column that are larger than half the page size (wide indexes) could sometimes get corrupt, resulting in an ArrayIndexOutOfBoundsException in PageBtree.getRow or "Row not found" in PageBtreeLeaf. Also, such indexes used too much disk space.
changelog_1145_li=Small optimisation for accessing result values by column name.
changelog_1146_li=Server mode\:when retrieving more than 64 rows each containing a CLOB or BLOB, the error message "The object is already closed" was thrown.
changelog_1146_li=Fix for bug in Statement.getMoreResults(int)
changelog_1147_li=ConvertTraceFile\:the time in the trace file is now parsed as a long.
changelog_1147_li=The SCRIPT statements now supports filtering by schema and table. Thanks a lot to Jacob Qvortrup for providing the patch\!
changelog_1148_li=Invalid connection settings are now detected.
changelog_1148_h2=Version 1.3.166 (2012-04-08)
changelog_1149_li=Issue 387\:WHERE condition getting pushed into sub-query with LIMIT.
changelog_1149_li=Indexes on column that are larger than half the page size (wide indexes) could sometimes get corrupt, resulting in an ArrayIndexOutOfBoundsException in PageBtree.getRow or "Row not found" in PageBtreeLeaf. Also, such indexes used too much disk space.
changelog_1150_h2=Version 1.3.165 (2012-03-18)
changelog_1150_li=Server mode\:when retrieving more than 64 rows each containing a CLOB or BLOB, the error message "The object is already closed" was thrown.
changelog_1151_li=Better string representation for decimal values (for example 0.00000000 instead of 0E-26).
changelog_1151_li=ConvertTraceFile\:the time in the trace file is now parsed as a long.
changelog_1152_li=Prepared statements could only be re-used if the same data types were used the second time they were executed.
changelog_1152_li=Invalid connection settings are now detected.
changelog_1153_li=In error messages about referential constraint violation, the values are now included.
changelog_1153_li=Issue 387\:WHERE condition getting pushed into sub-query with LIMIT.
changelog_1154_li=SCRIPT and RUNSCRIPT\:the password can now be set using a prepared statement. Previously, it was required to be a literal in the SQL statement.
changelog_1154_h2=Version 1.3.165 (2012-03-18)
changelog_1155_li=MySQL compatibility\:SUBSTR with a negative start index now works like MySQL.
changelog_1155_li=Better string representation for decimal values (for example 0.00000000 instead of 0E-26).
changelog_1156_li=When enabling autocommit, the transaction is now committed (as required by the JDBC API).
changelog_1156_li=Prepared statements could only be re-used if the same data types were used the second time they were executed.
changelog_1157_li=The shell script <code>h2.sh</code> did not work with spaces in the path. It also works now with quoted spaces in the argument list. Thanks a lot to Shimizu Fumiyuki for the patch\!
changelog_1157_li=In error messages about referential constraint violation, the values are now included.
changelog_1158_li=If the transaction log could not be truncated because of an uncommitted transaction, now "Transaction log could not be truncated" is written to the .trace.db file. Before, the database file was growing and it was hard to find out what the root cause was. To avoid the database file from growing, a new feature to automatically rollback the oldest transaction is available now. To enable it, append ;LOG_SIZE_LIMIT\=32 to the database URL (in that case, the oldest session is rolled back if the transaction log is 32 MB).
changelog_1158_li=SCRIPT and RUNSCRIPT\:the password can now be set using a prepared statement. Previously, it was required to be a literal in the SQL statement.
changelog_1159_li=ALTER TABLE ADD can now add more than one column at a time.
changelog_1159_li=MySQL compatibility\:SUBSTR with a negative start index now works like MySQL.
changelog_1160_li=Issue 380\:ALTER TABLE ADD FOREIGN KEY with an explicit index didn't verify the index can be used, which would lead to a NullPointerException later on.
changelog_1160_li=When enabling autocommit, the transaction is now committed (as required by the JDBC API).
changelog_1161_li=Issue 384\:the wrong kind of exception (NullPointerException) was thrown in a UNION query with an incorrect ORDER BY expression.
changelog_1161_li=The shell script <code>h2.sh</code> did not work with spaces in the path. It also works now with quoted spaces in the argument list. Thanks a lot to Shimizu Fumiyuki for the patch\!
changelog_1162_li=Issue 362\:support LIMIT in UPDATE statements.
changelog_1162_li=If the transaction log could not be truncated because of an uncommitted transaction, now "Transaction log could not be truncated" is written to the .trace.db file. Before, the database file was growing and it was hard to find out what the root cause was. To avoid the database file from growing, a new feature to automatically rollback the oldest transaction is available now. To enable it, append ;LOG_SIZE_LIMIT\=32 to the database URL (in that case, the oldest session is rolled back if the transaction log is 32 MB).
changelog_1163_li=Browser\:if no default browser is set, Google Chrome is now used if available. If not available, then Konqueror, Netscape, or Opera is used if available (as before).
changelog_1163_li=ALTER TABLE ADD can now add more than one column at a time.
changelog_1164_li=CSV tool\:new feature to disable writing the column header (option writeColumnHeader).
changelog_1164_li=Issue 380\:ALTER TABLE ADD FOREIGN KEY with an explicit index didn't verify the index can be used, which would lead to a NullPointerException later on.
changelog_1165_li=CSV tool\:new feature to preserve the case sensitivity of column names (option caseSensitiveColumnNames).
changelog_1165_li=Issue 384\:the wrong kind of exception (NullPointerException) was thrown in a UNION query with an incorrect ORDER BY expression.
changelog_1166_li=PostgreSQL compatibility\:LOG(x) is base 10 in the PostgreSQL mode.
changelog_1166_li=Issue 362\:support LIMIT in UPDATE statements.
changelog_1167_h2=Version 1.3.164 (2012-02-03)
changelog_1167_li=Browser\:if no default browser is set, Google Chrome is now used if available. If not available, then Konqueror, Netscape, or Opera is used if available (as before).
changelog_1168_li=New built-in function ARRAY_CONTAINS.
changelog_1168_li=CSV tool\:new feature to disable writing the column header (option writeColumnHeader).
changelog_1169_li=Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
changelog_1169_li=CSV tool\:new feature to preserve the case sensitivity of column names (option caseSensitiveColumnNames).
changelog_1170_li=Trying to convert a VARCHAR to UUID will now fail if the text contains a character that is not a hex digit, '-', or not a whitespace.
changelog_1170_li=PostgreSQL compatibility\:LOG(x) is base 10 in the PostgreSQL mode.
changelog_1171_li=TriggerAdapter\:in "before" triggers, values can be changed using the ResultSet.updateX methods.
changelog_1171_h2=Version 1.3.164 (2012-02-03)
changelog_1172_li=Creating a table with column data type NULL now works (even if not very useful).
changelog_1172_li=New built-in function ARRAY_CONTAINS.
changelog_1173_li=ALTER TABLE ALTER COLUMN no longer copies the data for widening conversions (for example if only the precision was increased) unless necessary.
changelog_1173_li=Some DatabaseMetaData methods didn't work when using ALLOW_LITERALS NONE.
changelog_1174_li=Multi-threaded kernel\:concurrently running an online backup and updating the database resulted in a broken (transactionally incorrect) backup file in some cases.
changelog_1174_li=Trying to convert a VARCHAR to UUID will now fail if the text contains a character that is not a hex digit, '-', or not a whitespace.
changelog_1175_li=The script created by SCRIPT DROP did not always work if multiple views existed that depend on each other.
changelog_1175_li=TriggerAdapter\:in "before" triggers, values can be changed using the ResultSet.updateX methods.
changelog_1176_li=MathUtils.getSecureRandom could log a warning to System.err in case the /dev/random is very slow, and the System.getProperties().toString() returned a string larger than 64 KB.
changelog_1176_li=Creating a table with column data type NULL now works (even if not very useful).
changelog_1177_li=The database file locking mechanism "FS" (;FILE_LOCK\=FS) did not work on Linux since version 1.3.161.
changelog_1177_li=ALTER TABLE ALTER COLUMN no longer copies the data for widening conversions (for example if only the precision was increased) unless necessary.
changelog_1178_li=Sequences\:the functions NEXTVAL and CURRVAL did not work as expected when using quoted, mixed case sequence names.
changelog_1178_li=Multi-threaded kernel\:concurrently running an online backup and updating the database resulted in a broken (transactionally incorrect) backup file in some cases.
changelog_1179_li=The constructor for Csv objects is now public, and Csv.getInstance() is now deprecated.
changelog_1179_li=The script created by SCRIPT DROP did not always work if multiple views existed that depend on each other.
changelog_1180_li=SimpleResultSet\:updating a result set is now supported.
changelog_1180_li=MathUtils.getSecureRandom could log a warning to System.err in case the /dev/random is very slow, and the System.getProperties().toString() returned a string larger than 64 KB.
changelog_1181_li=Database URL\:extra semicolons are not supported.
changelog_1181_li=The database file locking mechanism "FS" (;FILE_LOCK\=FS) did not work on Linux since version 1.3.161.
changelog_1182_h2=Version 1.3.163 (2011-12-30)
changelog_1182_li=Sequences\:the functions NEXTVAL and CURRVAL did not work as expected when using quoted, mixed case sequence names.
changelog_1183_li=On out of disk space, the database could get corrupt sometimes, if later write operations succeeded. The same problem happened on other kinds of I/O exceptions (where one or some of the writes fail, but subsequent writes succeed). Now the file is closed on the first unsuccessful write operation, so that later requests fail consistently.
changelog_1183_li=The constructor for Csv objects is now public, and Csv.getInstance() is now deprecated.
changelog_1184_li=DatabaseEventListener.diskSpaceIsLow() is no longer supported because it can't be guaranteed that it always works correctly.
changelog_1184_li=SimpleResultSet\:updating a result set is now supported.
changelog_1185_li=XMLTEXT now supports an optional parameter to escape newlines.
changelog_1185_li=Database URL\:extra semicolons are not supported.
changelog_1186_li=XMLNODE now support an optional parameter to disable indentation.
changelog_1186_h2=Version 1.3.163 (2011-12-30)
changelog_1187_li=Csv.write now formats date, time, and timestamp values using java.sql.Date / Time / Timestamp.toString(). Previously, ResultSet.getString() was used, which didn't work well for Oracle.
changelog_1187_li=On out of disk space, the database could get corrupt sometimes, if later write operations succeeded. The same problem happened on other kinds of I/O exceptions (where one or some of the writes fail, but subsequent writes succeed). Now the file is closed on the first unsuccessful write operation, so that later requests fail consistently.
changelog_1188_li=The shell script <code>h2.sh</code> can now be run from within a different directory. Thanks a lot to Daniel Serodio for the patch\!
changelog_1188_li=DatabaseEventListener.diskSpaceIsLow() is no longer supported because it can't be guaranteed that it always works correctly.
changelog_1189_li=The page size of a persistent database can now be queries using\:select * from information_schema.settings where name \='info.PAGE_SIZE'
changelog_1189_li=XMLTEXT now supports an optional parameter to escape newlines.
changelog_1190_li=In the server mode, BLOB and CLOB objects are no longer closed when the result set is closed (as required by the JDBC spec).
changelog_1190_li=XMLNODE now support an optional parameter to disable indentation.
changelog_1191_li=Csv.write now formats date, time, and timestamp values using java.sql.Date / Time / Timestamp.toString(). Previously, ResultSet.getString() was used, which didn't work well for Oracle.
changelog_1192_li=The shell script <code>h2.sh</code> can now be run from within a different directory. Thanks a lot to Daniel Serodio for the patch\!
changelog_1193_li=The page size of a persistent database can now be queries using\:select * from information_schema.settings where name \='info.PAGE_SIZE'
changelog_1194_li=In the server mode, BLOB and CLOB objects are no longer closed when the result set is closed (as required by the JDBC spec).
mvstore_1108_li=\ if the object is modified concurrently.
mvstore_1108_li=\ if the object is modified concurrently.
mvstore_1109_h3=Table Engine for H2
mvstore_1109_h3=Table Engine for H2
mvstore_1110_p=\ The plan is to use the MVStore as the default storage engine for the H2 database in the future (supporting SQL, JDBC, transactions, MVCC, and so on). This is work in progress. To try it out, append <code>;DEFAULT_TABLE_ENGINE\=org.h2.mvstore.db.MVTableEngine</code> to the database URL. In general, functionality and performance should be similar than the current default storage engine (the page store). There are a few features that have not been implemented yet or are not complete\:
mvstore_1110_p=\ The plan is to use the MVStore as the default storage engine for the H2 database in the future (supporting SQL, JDBC, transactions, MVCC, and so on). This is work in progress. To try it out, append <code>;DEFAULT_TABLE_ENGINE\=org.h2.mvstore.db.MVTableEngine</code> to the database URL. In general, functionality and performance should be similar than the current default storage engine (the page store). There are a few features that have not been implemented yet or are not complete\:
mvstore_1111_li=Changing the cache size.
mvstore_1111_li=Changing the cache size is currently not supported.
mvstore_1112_li=Two-phase commit.
mvstore_1112_li=The database metadata is still stored in a <code>.h2.db</code> file, and the <code>.lock.db</code> file is still used to lock a database (long term, the plan is to no longer use those files).
mvstore_1113_li=The database metadata is still stored in a <code>.h2.db</code> file.
mvstore_1113_li=The database file(s) sometimes do not shrink as expected.
mvstore_1114_li=The database file(s) sometimes do not shrink as expected.
mvstore_1114_h2=Similar Projects and Differences to Other Storage Engines
mvstore_1115_h2=Similar Projects and Differences to Other Storage Engines
mvstore_1115_p=\ Unlike similar storage engines like LevelDB and Kyoto Cabinet, the MVStore is written in Java and can easily be embedded in a Java and Android application.
mvstore_1116_p=\ Unlike similar storage engines like LevelDB and Kyoto Cabinet, the MVStore is written in Java and can easily be embedded in a Java and Android application.
mvstore_1116_p=\ The MVStore is somewhat similar to the Berkeley DB Java Edition because it is also written in Java, and is also a log structured storage, but the H2 license is more liberal.
mvstore_1117_p=\ The MVStore is somewhat similar to the Berkeley DB Java Edition because it is also written in Java, and is also a log structured storage, but the H2 license is more liberal.
mvstore_1117_p=\ Like SQLite, the MVStore keeps all data in one file. Unlike SQLite, the MVStore uses is a log structured storage. The plan is to make the MVStore both easier to use as well as faster than SQLite. In a recent (very simple) test, the MVStore was about twice as fast as SQLite on Android.
mvstore_1118_p=\ Like SQLite, the MVStore keeps all data in one file. Unlike SQLite, the MVStore uses is a log structured storage. The plan is to make the MVStore both easier to use as well as faster than SQLite. In a recent (very simple) test, the MVStore was about twice as fast as SQLite on Android.
mvstore_1118_p=\ The API of the MVStore is similar to MapDB (previously known as JDBM) from Jan Kotek, and some code is shared between MapDB and JDBM. However, unlike MapDB, the MVStore uses is a log structured storage. The MVStore does not have a record size limit.
mvstore_1119_p=\ The API of the MVStore is similar to MapDB (previously known as JDBM) from Jan Kotek, and some code is shared between MapDB and JDBM. However, unlike MapDB, the MVStore uses is a log structured storage. The MVStore does not have a record size limit.
mvstore_1119_h2=Current State
mvstore_1120_h2=Current State
mvstore_1120_p=\ The code is still experimental at this stage. The API as well as the behavior may partially change. Features may be added and removed (even thought the main features will stay).
mvstore_1121_p=\ The code is still experimental at this stage. The API as well as the behavior may partially change. Features may be added and removed (even thought the main features will stay).
mvstore_1121_h2=Requirements
mvstore_1122_h2=Requirements
mvstore_1122_p=\ The MVStore is included in the latest H2 jar file.
mvstore_1123_p=\ The MVStore is included in the latest H2 jar file.
mvstore_1123_p=\ There are no special requirements to use it. The MVStore should run on any JVM as well as on Android.
mvstore_1124_p=\ There are no special requirements to use it. The MVStore should run on any JVM as well as on Android.
mvstore_1124_p=\ To build just the MVStore (without the database engine), run\:
mvstore_1125_p=\ To build just the MVStore (without the database engine), run\:
mvstore_1125_p=\ This will create the file <code>bin/h2mvstore-1.3.172.jar</code> (about 130 KB).
mvstore_1126_p=\ This will create the file <code>bin/h2mvstore-1.3.172.jar</code> (about 130 KB).
