To create the file <code>h2client.jar</code>, go to the directory <code>h2</code> and execute the following command:
@build_1045_h2
@build_1045_h3
Using Lucene 2 / 3
@build_1046_p
Both Apache Lucene 2 and Lucene 3 are supported. Currently Apache Lucene version 2.x is used by default for H2 version 1.2.x, and Lucene version 3.x is used by default for H2 version 1.3.x. To use a different version of Lucene when compiling, it needs to be specified as follows:
@build_1047_h2
Using Maven 2
@build_1046_h3
@build_1048_h3
Using a Central Repository
@build_1047_p
@build_1049_p
You can include the database in your Maven 2 project as a dependency. Example:
@build_1048_p
@build_1050_p
New versions of this database are first uploaded to http://hsql.sourceforge.net/m2-repo/ and then automatically synchronized with the main Maven repository; however after a new release it may take a few hours before they are available there.
@build_1049_h3
@build_1051_h3
Using Snapshot Version
@build_1050_p
@build_1052_p
To build a <code>h2-*-SNAPSHOT.jar</code> file and upload it the to the local Maven 2 repository, execute the following command:
@build_1051_p
@build_1053_p
Afterwards, you can include the database in your Maven 2 project as a dependency:
@build_1052_h2
@build_1054_h2
Translating
@build_1053_p
@build_1055_p
The translation of this software is split into the following parts:
To translate the H2 Console, start it and select Preferences / Translate. After you are done, send the translated <code>*.prop</code> file to the Google Group. The web site is currently translated using Google.
@build_1057_h2
@build_1059_h2
Providing Patches
@build_1058_p
@build_1060_p
If you like to provide patches, please consider the following guidelines to simplify merging them:
@build_1059_li
@build_1061_li
Only use Java 1.5 features (do not use Java 1.6) (see <a href="#environment">Environment</a>).
@build_1060_li
@build_1062_li
Follow the coding style used in the project, and use Checkstyle (see above) to verify. For example, do not use tabs (use spaces instead). The checkstyle configuration is in <code>src/installer/checkstyle.xml</code>.
@build_1061_li
@build_1063_li
A template of the Eclipse settings are in <code>src/installer/eclipse.settings/*</code>. If you want to use them, you need to copy them to the <code>.settings</code> directory. The formatting options (<code>eclipseCodeStyle</code>) are also included.
@build_1062_li
@build_1064_li
Please provide test cases and integrate them into the test suite. For Java level tests, see <code>src/test/org/h2/test/TestAll.java</code>. For SQL level tests, see <code>src/test/org/h2/test/test.in.txt</code> or <code>testSimple.in.txt</code>.
@build_1063_li
@build_1065_li
The test cases should cover at least 90% of the changed and new code; use a code coverage tool to verify that (see above). or use the build target <code>coverage</code>.
@build_1064_li
@build_1066_li
Verify that you did not break other features: run the test cases by executing <code>build test</code>.
@build_1065_li
@build_1067_li
Provide end user documentation if required (<code>src/docsrc/html/*</code>).
@build_1066_li
@build_1068_li
Document grammar changes in <code>src/docsrc/help/help.csv</code>
@build_1067_li
@build_1069_li
Provide a change log entry (<code>src/docsrc/html/changelog.html</code>).
@build_1068_li
@build_1070_li
Verify the spelling using <code>build spellcheck</code>. If required add the new words to <code>src/tools/org/h2/build/doc/dictionary.txt</code>.
@build_1069_li
@build_1071_li
Run <code>src/installer/buildRelease</code> to find and fix formatting errors.
@build_1070_li
@build_1072_li
Verify the formatting using <code>build docs</code> and <code>build javadoc</code>.
@build_1071_li
@build_1073_li
Submit patches as <code>.patch</code> files (compressed if big). To create a patch using Eclipse, use Team / Create Patch.
@build_1072_p
@build_1074_p
For legal reasons, patches need to be public in the form of an email to the <a href="http://groups.google.com/group/h2-database">group</a>, or in the form of an <a href="http://code.google.com/p/h2database/issues/list">issue report or attachment</a>. Significant contributions need to include the following statement:
@build_1073_p
@build_1075_p
"I wrote the code, it's mine, and I'm contributing it to H2 for distribution multiple-licensed under the H2 License, version 1.0, and under the Eclipse Public License, version 1.0 (http://h2database.com/html/license.html)."
@build_1074_h2
@build_1076_h2
Reporting Problems or Requests
@build_1075_p
@build_1077_p
Please consider the following checklist if you have a question, want to report a problem, or if you have a feature request:
@build_1076_li
@build_1078_li
Feature requests are always welcome, even if the feature is already on the <a href="roadmap.html">roadmap</a>. Your mail will help prioritize feature requests. If you urgently need a feature, consider <a href="#providing_patches">providing a patch</a>.
@build_1077_li
@build_1079_li
Before posting problems, check the <a href="faq.html">FAQ</a> and do a <a href="http://google.com">Google search</a>.
@build_1078_li
@build_1080_li
When got an unexpected exception, please try the <a href="sourceError.html">Error Analyzer tool</a>. If this doesn't help, please report the problem, including the complete error message and stack trace, and the root cause stack trace(s).
@build_1079_li
@build_1081_li
When sending source code, please use a public web clipboard such as <a href="http://pastebin.com">Pastebin</a>, <a href="http://cl1p.net">Cl1p</a>, or <a href="http://www.mysticpaste.com/new">Mystic Paste</a> to avoid formatting problems. Please keep test cases as simple and short as possible, but so that the problem can still be reproduced. As a template, use: <a href="http://h2database.googlecode.com/svn/trunk/h2/src/test/org/h2/samples/HelloWorld.java">HelloWorld.java</a>. Method that simply call other methods should be avoided, as well as unnecessary exception handling. Please use the JDBC API and no external tools or libraries. The test should include all required initialization code, and should be started with the main method.
@build_1080_li
@build_1082_li
For large attachments, use a public temporary storage such as <a href="http://rapidshare.com">Rapidshare</a>.
@build_1081_li
@build_1083_li
Google Group versus issue tracking: Use the <a href="http://groups.google.com/group/h2-database">Google Group</a> for questions or if you are not sure it's a bug. If you are sure it's a bug, you can create an <a href="http://code.google.com/p/h2database/issues/list">issue</a>, but you don't need to (sending an email to the group is enough). Please note that only few people monitor the issue tracking system.
@build_1082_li
@build_1084_li
For out-of-memory problems, please analyze the problem yourself first, for example using the command line option <code>-XX:+HeapDumpOnOutOfMemoryError</code> and a memory analysis tool such as the <a href="http://www.eclipse.org/mat">Eclipse Memory Analyzer (MAT)</a>.
@build_1083_li
@build_1085_li
It may take a few days to get an answers. Please do not double post.
@build_1084_h2
@build_1086_h2
Automated Build
@build_1085_p
@build_1087_p
This build process is automated and runs regularly. The build process includes running the tests and code coverage, using the command line <code>./build.sh clean jar coverage -Dh2.ftpPassword=... uploadBuild</code>. The last results are available here:
@build_1086_a
@build_1088_a
Test Output
@build_1087_a
@build_1089_a
Code Coverage Summary
@build_1088_a
@build_1090_a
Code Coverage Details (download, 1.3 MB)
@build_1089_a
@build_1091_a
Build Newsfeed
@build_1090_a
@build_1092_a
Latest Jar File (download, 1 MB)
@build_1091_h2
@build_1093_h2
Generating Railroad Diagrams
@build_1092_p
@build_1094_p
The railroad diagrams are HTML, formatted as nested tables. The diagrams are generated as follows:
@build_1093_li
@build_1095_li
The BNF parser (<code>org.h2.bnf.Bnf</code>) reads and parses the BNF from the file <code>help.csv</code>.
@build_1094_li
@build_1096_li
The page parser (<code>org.h2.server.web.PageParser</code>) reads the template HTML file and fills in the diagrams.
@build_1095_li
@build_1097_li
The rail images (one straight, four junctions, two turns) are generated using a simple Java application.
@build_1096_p
@build_1098_p
To generate railroad diagrams for other grammars, see the package <code>org.h2.jcr</code>. This package is used to generate the SQL-2 railroad diagrams for the JCR 2.0 specification.
@changelog_1000_h1
...
...
@@ -1523,1359 +1529,1368 @@ Change Log
Next Version (unreleased)
@changelog_1002_li
JMX (the Java management extension) is now supported. Issue 253.
Improved date / time arithmetics. Now supported are multiplying and dividing a time with / by a number, adding and subtracting a time to / from a time or date, subtracting a time or timestamp from a timestamp.
@changelog_1003_li
Creating a comment on a column didn't work if the schema name was equal the database name.
The Ant build script has been removed because it is no longer up to date.
@changelog_1004_li
When using multi-version concurrency, re-running a prepared statement with the same parameters would sometimes give the same result even if another connection committed a change (the previous result was sometimes re-used incorrectly).
Nested outer joins without brackets were not working as expected. Example: select * from a inner join b inner join c on c.id = b.id on b.id = a.id;
@changelog_1005_li
When using SELECT_FOR_UPDATE_MVCC (lock only the selected rows when using MVCC), the selected rows were sometimes not locked correctly.
JMX (the Java management extension) is now supported. Issue 253.
@changelog_1006_li
When using Lucene 3, the index files were not always closed when the database was closed.
Creating a comment on a column didn't work if the schema name was equal the database name.
@changelog_1007_li
Concurrently preparing a statement and altering a table could throw a table not found exception.
When using multi-version concurrency, re-running a prepared statement with the same parameters would sometimes give the same result even if another connection committed a change (the previous result was sometimes re-used incorrectly).
@changelog_1008_li
When concurrently preparing many statements with a subquery, in some cases the query didn't run (Column "..." must be in the GROUP BY list).
When using SELECT_FOR_UPDATE_MVCC (lock only the selected rows when using MVCC), the selected rows were sometimes not locked correctly.
@changelog_1009_li
CallableStatement: now the syntax "{? = CALL...}" is supported as well.
When using Lucene 3, the index files were not always closed when the database was closed.
@changelog_1010_li
Lob in databases: two small BLOB or CLOB values were always considered equal. This also affected unique indexes.
Concurrently preparing a statement and altering a table could throw a table not found exception.
@changelog_1011_li
The shutdown hook is (re-) enabled by default even for H2 version 1.3.x.
When concurrently preparing many statements with a subquery, in some cases the query didn't run (Column "..." must be in the GROUP BY list).
@changelog_1012_li
When creating a database from a recovery script, the same user can now be used (CREATE USER now always includes IF EXISTS).
CallableStatement: now the syntax "{? = CALL...}" is supported as well.
@changelog_1013_li
Lob in databases: two small BLOB or CLOB values were always considered equal. This also affected unique indexes.
@changelog_1014_li
The shutdown hook is (re-) enabled by default even for H2 version 1.3.x.
@changelog_1015_li
When creating a database from a recovery script, the same user can now be used (CREATE USER now always includes IF EXISTS).
@changelog_1016_li
The H2 Console now prints a status message if started with parameters.
@changelog_1014_h2
@changelog_1017_h2
Version 1.3.146 Beta (2010-11-08)
@changelog_1015_li
@changelog_1018_li
This is a beta version. The next version will be 1.2.147. The differences between 1.2.x and 1.3.x are:
@changelog_1016_li
@changelog_1019_li
In version 1.3.x, h2.lobInDatabase (store CLOB and BLOB in the database file) is enabled by default.
@changelog_1017_li
@changelog_1020_li
In version 1.3.x, ANALYZE_AUTO is 2000 (automatic ANALYZE).
@changelog_1018_li
@changelog_1021_li
In version 1.3.x, DB_CLOSE_ON_EXIT (the shutdown hook) is disabled by default.
@changelog_1019_li
@changelog_1022_li
In version 1.3.x, DROP_RESTRICT (default action for DROP is RESTRICT) is enabled.
@changelog_1020_li
@changelog_1023_li
In version 1.3.x, FUNCTIONS_IN_SCHEMA (allow to store functions in a schema) is enabled.
@changelog_1021_li
@changelog_1024_li
In version 1.3.x, LARGE_TRANSACTIONS (support for very large transactions) is enabled. Changes to tables without a primary key can be buffered to disk.
@changelog_1022_li
@changelog_1025_li
In version 1.3.x, MAX_MEMORY_ROWS_DISTINCT is set to a 10000.
@changelog_1023_li
@changelog_1026_li
In version 1.3.x, NESTED_JOINS (nested joins and right outer joins) is enabled.
@changelog_1024_li
@changelog_1027_li
In version 1.3.x, OPTIMIZE_INSERT_FROM_SELECT (speed up CREATE TABLE ... AS SELECT) is enabled.
@changelog_1025_li
@changelog_1028_li
In version 1.3.x, OPTIMIZE_OR (convert OR conditions to IN(..) if possible) is enabled.
@changelog_1026_li
@changelog_1029_li
In version 1.3.x, QUERY_CACHE_SIZE is enabled.
@changelog_1027_li
@changelog_1030_li
In version 1.3.x, SELECT_FOR_UPDATE_MVCC (MVCC and SELECT FOR UPDATE) is enabled.
@changelog_1028_li
@changelog_1031_li
In version 1.3.x, RUNSCRIPT and SCRIPT (commands and tools), use UTF-8 by default (ScriptCommand.charset).
@changelog_1029_li
@changelog_1032_li
In version 1.3.x, Lucene 3 is used by default. Issue 147.
@changelog_1030_li
@changelog_1033_li
When the system property h2.lobInDatabase is set, the lob tables were always created when closing the database, even if the tables were not needed.
@changelog_1031_li
@changelog_1034_li
In the MySQL mode, SHOW TABLES didn't work, and meta data tables were not case insensitive. Updatable result sets didn't work as expected. Issue 249.
@changelog_1032_li
@changelog_1035_li
Connection-created Clob and Blob objects can now be filled using Clob.setCharacterStream(1), Clob.setString(1, s), Blob.setBytes(1, x), Blob.setBinaryStream(1). Issue 235.
@changelog_1033_li
@changelog_1036_li
Trying to convert a very small CLOB to a BLOB or a very small CLOB to a BLOB threw a NullPointerException.
@changelog_1034_li
@changelog_1037_li
INFORMATION_SCHEMA.SETTINGS: now the current page count can be queried using select * from information_schema.settings where name = 'info.PAGE_COUNT'.
@changelog_1035_li
@changelog_1038_li
For an invalid value exception, the parameter name and value was switched in some cases.
@changelog_1036_li
@changelog_1039_li
When using trace level 3, opening a database no longer prints there is a EOFException (because that is the expected behavior).
@changelog_1037_li
@changelog_1040_li
CALL calling a Java function with return type ResultSet and return value null threw a ClassCastException.
@changelog_1038_li
@changelog_1041_li
SELECT ... FROM CSVREAD no longer creates a temporary file. Some large imports are now twice as fast.
@changelog_1039_h2
@changelog_1042_h2
Version 1.2.145 (2010-11-02)
@changelog_1040_li
@changelog_1043_li
A new String cache is now created at most once every 5 second, so that out of memory exceptions are not artificially delayed.
@changelog_1041_li
@changelog_1044_li
After closing a database, the writer thread will stop after 100 ms at the latest (instead of 1 second).
@changelog_1042_li
@changelog_1045_li
Opening a large database could fail in theory if the process was killed and then not fully compacted (because the unique transaction log key was re-used).
@changelog_1043_li
@changelog_1046_li
Views now store the schema for Java functions if "functions in schemas" is enabled (system property h2.functionsInSchema).
@changelog_1044_li
@changelog_1047_li
Improved error message if the LOB files are already deleted on the client side.
@changelog_1045_li
@changelog_1048_li
Closing a Statement or PreparedStatement at the same time as executing a statement could throw a strange exception. Issue 241.
@changelog_1046_li
@changelog_1049_li
The Recover tool did not work with compressed lob files (set compress_lob lzf). Also, sometimes the Recover tool was very slow, specially using a 64-bit JVM, because it tried to de-compress lob files even if they were not compressed (which could allocate a lot of memory).
@changelog_1047_li
@changelog_1050_li
H2 Console: webAllowOthers and webSSL were swapped if they didn't exist in the properties file. Issue 244.
@changelog_1048_li
@changelog_1051_li
When the system property h2.lobInDatabase is set, CREATE TABLE ... AS SELECT with a LOB column did not always work.
@changelog_1049_li
@changelog_1052_li
Some system properties are not supported any longer, because they can already be set in the database URL. The constants are: CACHE_SIZE_DEFAULT, CACHE_TYPE_DEFAULT, DEFAULT_LOCK_MODE, LOCK_MODE_READ_COMMITTED, DEFAULT_MAX_LENGTH_INPLACE_LOB, DEFAULT_MAX_LENGTH_INPLACE_LOB2, DEFAULT_MAX_MEMORY_UNDO, DEFAULT_MAX_OPERATION_MEMORY, DEFAULT_PAGE_SIZE, DEFAULT_RESULT_SET_CONCURRENCY, MIN_WRITE_DELAY.
@changelog_1050_li
@changelog_1053_li
Various system properties have been replaced with database level settings: ALIAS_COLUMN_NAME, ANALYZE_AUTO, ANALYZE_SAMPLE, DATABASE_TO_UPPER, DEFAULT_ESCAPE, DEFRAG_ALWAYS, DROP_RESTRICT, ESTIMATED_FUNCTION_TABLE_ROWS, FUNCTIONS_IN_SCHEMA, LARGE_RESULT_BUFFER_SIZE, LARGE_TRANSACTIONS, MAX_COMPACT_COUNT, MAX_COMPACT_TIME, MAX_MEMORY_ROWS_DISTINCT, MAX_QUERY_TIMEOUT, NESTED_JOINS, OPTIMIZE_DISTINCT, OPTIMIZE_EVALUATABLE_SUBQUERIES, OPTIMIZE_INSERT_FROM_SELECT, OPTIMIZE_IN_LIST, OPTIMIZE_IS_NULL, OPTIMIZE_OR, OPTIMIZE_SUBQUERY_CACHE, OPTIMIZE_TWO_EQUALS, OPTIMIZE_UPDATE, PAGE_STORE_INTERNAL_COUNT, PAGE_STORE_TRIM, QUERY_CACHE_SIZE, RECOMPILE_ALWAYS, RECONNECT_CHECK_DELAY, SELECT_FOR_UPDATE_MVCC, SHARE_LINKED_CONNECTIONS. See the Javadoc documentation of DbSettings for details. The system properties are still supported for backward compatibility.
@changelog_1051_li
@changelog_1054_li
When the system property h2.nestedJoins was enabled, some outer joins returned the wrong result.
@changelog_1052_li
@changelog_1055_li
Opening a database could throw a NullPointerException.
@changelog_1053_li
@changelog_1056_li
After a crash, the database file did not always shrink because old transaction log pages were not removed from the file.
@changelog_1054_li
@changelog_1057_li
Various CallableStatement methods could throw a NullPointerException.
@changelog_1055_li
@changelog_1058_li
LOB files were not deleted when running DROP ALL OBJECTS.
@changelog_1056_li
@changelog_1059_li
MS SQL Server compatibility: support "N" in front of string literals ("National Language" strings). Issue 240.
@changelog_1057_li
@changelog_1060_li
CAST: when converting a string to binary, it is hex encoded (every byte two characters); a hex string can be converted to a number by first converting it to binary. Examples: CAST(CAST('FFFF' AS BINARY) AS INT) = 65535, CAST(65535 AS BINARY) = '0000FFFF'.
@changelog_1058_li
@changelog_1061_li
When a domain (user defined data type) contained a user defined function, the database could not be opened.
@changelog_1059_li
@changelog_1062_li
CAST('011' AS INT) will no longer use decode the value as an octal number (using Integer.decode) but now use Integer.parseInt. The same logic applied to byte, short, and long. This also means that trying to convert hex numbers (0x...) with CAST now fails.
@changelog_1060_li
@changelog_1063_li
A table in the Recover tool script could not be imported if the script contained duplicate keys.
@changelog_1061_h2
@changelog_1064_h2
Version 1.2.144 (2010-10-15)
@changelog_1062_li
@changelog_1065_li
The Windows .bat files did not contain CR+LF.
@changelog_1063_li
@changelog_1066_li
The LOB storage (when the system property h2.lobInDatabase is set) is now only initialized when needed.
@changelog_1064_li
@changelog_1067_li
The index condition columnName IS NULL was not efficient when using a clustered index.
@changelog_1065_li
@changelog_1068_li
The Recover tool did not work for databases larger than 2 GB.
@changelog_1066_li
@changelog_1069_li
In memory database: outer joins with a condition "column is null" could return the wrong result.
@changelog_1067_li
@changelog_1070_li
Temporary files were not created in the temporary directory of the system, but in the current working directory. This affected temporary undo log files for read-only databases, temporary files for large result sets when using read-only databases, and temporary LOB files when storing LOBs in the database (system property h2.lobInDatabase). When the setting h2.lobInDatabase is not set, temporary LOB files are still stored in a sub-directory (.lobs.db/) of the current working directory.
@changelog_1068_li
@changelog_1071_li
New experimental feature to speed up CREATE TABLE ... AS SELECT. To enable the feature, set the system property h2.optimizeInsertFromSelect to true. For large queries, performance can be doubled.
@changelog_1069_li
@changelog_1072_li
When LOB objects are stored in the database (using the experimental setting h2.lobInDatabase), and using the MVCC mode, opening a database with uncommitted transactions could throw a NullPointerException.
@changelog_1070_li
@changelog_1073_li
Support of stored procedures with OUT parameters in CallableStatement is implemented.
@changelog_1071_li
@changelog_1074_li
PreparedStatement.getMetaData() was not always consistent with resulting ResultSet.getMetaData().
@changelog_1072_li
@changelog_1075_li
The build tool now uses JAVA_HOME for javac as well. Issue 233.
@changelog_1073_li
@changelog_1076_li
Opening and closing encrypted databases is now much faster.
@changelog_1074_li
@changelog_1077_li
H2 Console: new experimental feature to support file download and upload, but only if there is a directory called "transfer" in the current working directory. For security reasons, only very simple file names are supported. Sub-directories are not supported. To upload, use transfer.jsp; to download, use transfer/fileName.
@changelog_1075_li
@changelog_1078_li
A new sample application that shows how to manually create an encrypted and compressed script file.
@changelog_1076_li
@changelog_1079_li
Performance has been improved a bit.
@changelog_1077_li
@changelog_1080_li
DatabaseMetaData.getJDBCMajorVersion now returns 4 (instead of 3) when the driver is compiled with Java 6 (the default).
@changelog_1078_li
@changelog_1081_li
Re-added the internal utility class BitField which improves performance of opening and closing a database (because it supports setByte / getByte, unlike java.util.BitSet).
@changelog_1079_li
@changelog_1082_li
INFORMATION_SCHEMA.SESSIONS: the start time of a SQL statement is no longer set in each case. It is only set for long running statements. This change should improve performance a bit on some devices, specially when using Android.
@changelog_1080_li
@changelog_1083_li
A old databases without user name and password (created with H2 version 1.2.142 or older) couldn't be opened with version 1.2.143. Fixed.
@changelog_1081_li
@changelog_1084_li
The database upgrade classes have been renamed.
@changelog_1082_li
@changelog_1085_li
The database did not automatically upgrade when using a connection pool or data source.
@changelog_1083_li
@changelog_1086_li
JaQu: a database object can now also be created using a DataSource. Issue 227.
@changelog_1084_li
@changelog_1087_li
The built-in profiler now better supports the Dalvik VM.
@changelog_1085_li
@changelog_1088_li
The jarSmall build target no longer includes assertions (SysProperties.CHECK, CHECK2, system properties h2.check and h2.check2).
@changelog_1086_li
@changelog_1089_li
The jarSmall build target excluded the DbUpgrade classes by mistake.
@changelog_1087_h2
@changelog_1090_h2
Version 1.2.143 (2010-09-18)
@changelog_1088_li
@changelog_1091_li
If the user name and password are not set or empty, then the password is not hashed. To disable this behavior, set the system property h2.emptyPassword to false. TCP server: the default user name for the management database is now an empty string.
@changelog_1089_li
@changelog_1092_li
Cluster: auto-commit was disabled after opening a connection.
@changelog_1090_li
@changelog_1093_li
Connection.getAutoCommit() is now much faster, specially when using the server mode.
@changelog_1091_li
@changelog_1094_li
Statement.cancel() had no effect when using the server mode.
@changelog_1092_li
@changelog_1095_li
SCRIPT: the SQL script no longer contains settings that match the default value.
@changelog_1093_li
@changelog_1096_li
Statement.cancel() did not work when running RUNSCRIPT and SCRIPT.
@changelog_1094_li
@changelog_1097_li
Statement.cancel() could cause a NullPointerException.
@changelog_1095_li
@changelog_1098_li
In some cases (specially when using a small cache size or a large database over 1 GB) for some operations like ALTER TABLE the data was written before the transaction log entries, which could cause a corrupt database if the process was killed during the ALTER TABLE operation. Thanks a lot to Victor Pyankov for helping solve this problem!
@changelog_1096_li
@changelog_1099_li
The Recover tool could throw a ArrayIndexOutOfBoundsException when trying to recover a corrupt database file.
@changelog_1097_li
@changelog_1100_li
The SCRIPT command and tool now uses the default file encoding for the system now instead of UTF-8 (as before). In most cases, this will not affect existing applications, as the encoding only affects how SQL identifiers (table names and so on) that contain special characters are stored. Table data is escaped, and therefore is no problem.
@changelog_1098_li
@changelog_1101_li
The SCRIPT command and tool now also support the CHARSET option (like RUNSCRIPT).
@changelog_1099_li
@changelog_1102_li
When closing a database, sometimes empty space in the database was not freed up.
@changelog_1100_li
@changelog_1103_li
Trying to create a view with parameters in the query will now throw an exception. So far, creating the view was allowed, but the parameter value was not used (null was used instead).
@changelog_1101_li
@changelog_1104_li
New experimental feature SHUTDOWN DEFRAG. This option re-orders the pages while closing the database so that table scans are faster.
@changelog_1102_li
@changelog_1105_li
When using the MULTI_THREADED option, concurrently reading from a database (specially from a larger database, or when using a small cache size) could throw an exception.
@changelog_1103_li
@changelog_1106_li
When adding a comment to a column that has a check constraint, the database couldn't be re-opened.
@changelog_1104_li
@changelog_1107_li
New system property h2.lobClientMaxSizeMemory to set the maximum size of a LOB object to keep in memory on the client side when using the server mode.
@changelog_1105_h2
@changelog_1108_h2
Version 1.2.142 (2010-08-31)
@changelog_1106_li
@changelog_1109_li
Documentation for using H2 on Android devices has been added under Tutorial - Android.
@changelog_1107_li
@changelog_1110_li
An ArrayIndexOutOfBoundsException was thrown when querying the table information_schema.function_aliases while there are any user defined aggregate functions.
@changelog_1108_li
@changelog_1111_li
The jar files are now about 50 KB smaller. In the last few versions they contained superfluous classes.
@changelog_1109_li
@changelog_1112_li
The default time to compact a database when closing (system property h2.maxCompactTime) is now 0.2 seconds instead of 1 second.
@changelog_1110_li
@changelog_1113_li
Opening an closing a database is now faster.
@changelog_1111_li
@changelog_1114_li
In theory, when using indexes with large index rows (or when using a very small page size), removing rows could throw an internal exception in some cases.
@changelog_1112_li
@changelog_1115_li
Inserting rows in reverse order could throw an ArrayIndexOutOfBoundsException in some cases (specially rows larger than the page size, which is 2 KB by default). Issue 226.
@changelog_1113_li
@changelog_1116_li
H2 Console: with Chrome and Safari, resizing the table/query frame doesn't work. Issue 225.
@changelog_1114_li
@changelog_1117_li
New experimental database file locking mechanism "FS" to use native file locking (no *.lock.db file is created in this case, and no background thread is started). This mechanism may not work on all systems (on some systems it's possible to lock the same file multiple times within the same virtual machine, and on some system native file locking is not working or unlocking is not working).
@changelog_1115_h2
@changelog_1118_h2
Version 1.2.141 (2010-08-22)
@changelog_1116_li
@changelog_1119_li
New experimental pseudo-encryption algorithm "FOG". It makes the data appear to be encrypted. This algorithm is cryptographically extremely weak, and should only be used to hide data from reading the plain text using a text editor. Please let us know if you think this is useful or not.
@changelog_1117_li
@changelog_1120_li
Documentation: the grammar and function documentation can now be easier translated.
@changelog_1118_li
@changelog_1121_li
Password hash: in addition to connecting with the plain text password, H2 now supports connecting with the password hash. Like this you don't have to store plain text passwords in config files. For details, see the documentation at Advanced / Password Hash.
@changelog_1119_li
@changelog_1122_li
Lucene 3.x support was added in the source code, however it is not yet enabled by default and is not yet supported when using the default h2 jar file. To enable Lucene 3.x support, the source code of H2 needs to be switched using <code>./build.sh -Dlucene=3 switchSource</code>, and then re-compile. To switch the source code back use <code>./build.sh -Dlucene=2 switchSource</code> (replace ./build.sh with build.bat on Windows). The plan is to use Lucene 3 by default in H2 version 1.3.x. Issue 147.
@changelog_1120_li
@changelog_1123_li
The native fulltext search could cause a Java level deadlock if searching from multiple connections concurrently.
@changelog_1121_li
@changelog_1124_li
CREATE FORCE VIEW didn't work in most cases if a referenced table didn't exist.
@changelog_1122_li
@changelog_1125_li
MVCC: when trying to insert two rows with the same key from two connections, the second connection immediately threw the exception "Unique index or primary key violation". Instead, the second connection now waits throwing the exception until the first connection committed the change (same as when trying to concurrently update the same row).
@changelog_1123_li
@changelog_1126_li
Server mode: if the client ran with a different timezone setting than the server, date values got shifted by the difference between the timezones. This problem affected the data types DATE, TIME, and TIMESTAMP, when using PreparedStatement.setDate / setTime / setTimestamp and ResultSet.getDate / getTime / getTimestamp. To solve the problem, both the client and the server need to be updated (otherwise the old transfer protocol is used).
@changelog_1124_li
@changelog_1127_li
The built-in connection pool (JdbcConnectionPool) did not always honor the login timeout (the timeout could occur much too early). Thanks a lot to Dario Fassi for the patch!
@changelog_1125_li
@changelog_1128_li
Translation: the new messages have been translated to Spanish. Thanks a lot to Dario Fassi!
@changelog_1126_li
@changelog_1129_li
The table INFORMATION_SCHEMA.SETTINGS now contains all H2-specific system properties (the ones that start with "h2.") and that are explicitly set. Previously, some H2-specific settings (for example h2.analyzeAuto) were missing in this list.
@changelog_1127_li
@changelog_1130_li
EXPLAIN ANALYZE with an in-memory database threw an exception. Issue 216.
@changelog_1128_li
@changelog_1131_li
Data modifications (inserts, updates, and deletes) are now up to 5 times faster because converting objects to byte arrays is avoided if possible.
@changelog_1129_li
@changelog_1132_li
LOG=0 is now a bit faster (previously undo log entries were still written).
@changelog_1130_li
@changelog_1133_li
The command line tools now say so if the source directory of an option doesn't exist.
@changelog_1131_li
@changelog_1134_li
It is now allowed to truncate a table if referential integrity has been disabled for this table or database.
@changelog_1132_li
@changelog_1135_li
For unencrypted databases, the automatic upgrade temporary script file is now unencrypted again.
@changelog_1133_h2
@changelog_1136_h2
Version 1.2.140 (2010-07-25)
@changelog_1134_li
@changelog_1137_li
The default MAX_LOG_SIZE is now 16 MB instead of 2 MB. Some uses cases are 3 times faster now.
@changelog_1135_li
@changelog_1138_li
Improved cache memory usage calculation.
@changelog_1136_li
@changelog_1139_li
Only resources that are actually used are loaded in memory. This can reduce the memory usage by about 400 KB.
@changelog_1137_li
@changelog_1140_li
Profiling: the jar file can now be installed as an agent using java -javaagent:h2*.jar - this was be used to more accurately calculate the memory footprint of the cache. It has no effect when using H2 (using this feature in an application is not needed and not recommended).
@changelog_1138_li
@changelog_1141_li
The cache was not used efficiently when reading (behaving like a FIFO cache instead of an LRU cache).
@changelog_1139_li
@changelog_1142_li
Storing lobs in the database has been changed. It is now faster. Unfortunately, the change is not backward compatible; if you have used h2.lobInDatabase before you will need to re-build the database.
@changelog_1140_li
@changelog_1143_li
SHUTDOWN COMPACT is now faster.
@changelog_1141_li
@changelog_1144_li
H2 Console: requesting the status did not always show the window on top of others.
@changelog_1142_li
@changelog_1145_li
H2 Console: on some system, the browser windows got opened when requesting a new one.
@changelog_1143_li
@changelog_1146_li
The built-in profiling tool now uses a default stack depth of 32 elements and a default interval of 10 ms.
@changelog_1144_li
@changelog_1147_li
Database files now grows in 1 MB blocks (and at least 20% at a time), instead of always 256 KB. This speeds up loading a new database.
@changelog_1145_li
@changelog_1148_li
H2 Console: new built-in command @sleep to help profile another session.
@changelog_1146_li
@changelog_1149_li
For improved performance, LOG=0 and LOG=1 are again supported. LOG=0 means the transaction log is disabled completely (fastest; for loading a database). LOG=1 means the transaction log is enabled, but FileDescriptor.sync is disabled (if no protection against power failure is required). LOG=2 is the default (transaction log is enabled, FileDescriptor.sync for each checkpoint).
@changelog_1147_li
@changelog_1150_li
After deleting a lot of data (for example by dropping or altering tables, or indexes, or after a large transaction), opening a large database was very slow. Fixed.
@changelog_1148_li
@changelog_1151_li
When killing the process after creating and dropping many tables (specially temporary tables), the database could not be opened sometimes.
@changelog_1149_li
@changelog_1152_li
CAST(NULL AS ...) doesn't forget the data type, precision, and scale any longer.
@changelog_1150_li
@changelog_1153_li
Experimental support for recursive queries (see 'Advanced' - 'Recursive Queries' for details).
@changelog_1151_li
@changelog_1154_li
Problems with JDK 1.6.0_18 have been reports in the class StringUtils.quoteRemarkSQL. This method is now changed.
@changelog_1152_li
@changelog_1155_li
The "small jar" distribution did not include the CompressTool, which was required for some operations. Fixed.
@changelog_1153_li
@changelog_1156_li
The build tool now supports (minimalistic) shell mode, started using ./build.sh -
@changelog_1154_li
@changelog_1157_li
IS NULL comparison with nested queries and linked tables did not work. Example: select * from (select x from test) where x is null.
@changelog_1155_li
@changelog_1158_li
Support for null-safe equals. This includes the ANSI SQL standard syntax A IS [NOT] DISTINCT FROM B as well as the shorter A IS [NOT] B.
@changelog_1156_li
@changelog_1159_li
Primary key violations threw a strange exception message when using a single column INT or BIGINT key.
@changelog_1157_li
@changelog_1160_li
EXPLAIN ANALYZE now also lists the number of pages read from the file.
@changelog_1158_li
@changelog_1161_li
Memory mapped files: There was a bug in version 1.2.139 so that memory mapped files could only be used together with split, for example: split:nioMapped: - the problem is now solved. It is still a good idea to use split:nioMapped: to work around the 2 GB limitation of memory mapped files.
@changelog_1159_li
@changelog_1162_li
Memory mapped files: the system property h2.nioCleanerHack is now disabled by default because it was not always working as expected. Now System.gc() is used in a loop until the buffer is garbage collected. This of course is also not a nice solution, but the only one known to work. See also http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4724038
@changelog_1160_li
@changelog_1163_li
Bugfixes for the automatic 1.1 db migration.
@changelog_1161_li
@changelog_1164_li
If an old 1.1 database file version is found on connect, it is now possible to let the old h2 classes (v 1.2.128) connect to the database. The automatic upgrade .jar file must be present, and the url must contain NO_UPGRADE=TRUE
@changelog_1162_li
@changelog_1165_li
The automatic upgrade temporary script file is now encrypted.
@changelog_1163_h2
@changelog_1166_h2
Version 1.2.139 (2010-07-10)
@changelog_1164_li
@changelog_1167_li
There was a bug in the internal IntIntHashMap. There were no known side effects however.
@changelog_1165_li
@changelog_1168_li
ANALYZE now uses less memory.
@changelog_1166_li
@changelog_1169_li
Memory mapped file system: improved error messages if there is a problem.
@changelog_1167_li
@changelog_1170_li
The Lucene fulltext search did not work well when using special file systems such as split or nioMapped.
@changelog_1168_li
@changelog_1171_li
The memory mapped file system (nioMapped: file prefix) couldn't seek past the file length.
@changelog_1169_li
@changelog_1172_li
Some file system operations did not work with stacked file systems (for example split and nioMapped). This also affected the DeleteDbFiles tool.
@changelog_1170_li
@changelog_1173_li
New experimental query cache. The cache is only used if the SQL statement and all parameters match. Each session has it's own cache with the given size. Only the last returned result per query is cached. Only SELECT statements are cached (excluding UNION and FOR UPDATE statements). This works for both statements and prepared statement. To enable, set the system property h2.commandCacheSize to a value larger than 0. There is currently no plan to enable this option by default in future versions.
@changelog_1171_li
@changelog_1174_li
Conditions with many OR operations could throw an UnsupportedOperationException if h2.optimizeOr was enabled.
@changelog_1172_li
@changelog_1175_li
XA connection: after transaction commit or rollback, the physical connection is set into autocommit mode.
@changelog_1173_li
@changelog_1176_li
MULTI_THREADED did not work correctly and could throw the exception "try to add a record twice" for larger databases because cache access was not correctly synchronized.
@changelog_1174_li
@changelog_1177_li
Automatic database upgrade from non page store is now possible. If the classes from the h2mig_pagestore_addon.jar file are in the classpath, the database will be converted to the current page store format automatically. The file can be found here: <a href="http://h2database.com/h2mig_pagestore_addon.jar">http://h2database.com/h2mig_pagestore_addon.jar</a>
@changelog_1175_li
@changelog_1178_li
The MultiDimension tools was extended with a few helper methods. The API was unified a bit.
@changelog_1176_li
@changelog_1179_li
ODBC: MS Access could not link to a table with unique index or primary key. To solve this problem, index meta data is currently disabled for ODBC. When using the new H2 version to access a database over ODBC, the PostgreSQL catalog is automatically upgraded. Using a database with an upgraded PostgreSQL catalog with an older version of H2 is still possible, but not over ODBC.
@changelog_1177_li
@changelog_1180_li
ODBC: MS Access could not link to a table with a name containing '_'.
@changelog_1178_li
@changelog_1181_li
ODBC: additional connection settings can now be added to the database name. Example: ~/test;cipher=xtea. Therefore, encrypted databases are supported.
@changelog_1179_li
@changelog_1182_li
Local temporary tables can now be created without having to commit a transaction using CREATE LOCAL TEMPORARY TABLE TEMP(ID INT PRIMARY KEY) TRANSACTIONAL.
@changelog_1180_li
@changelog_1183_li
New system property h2.dropRestrict (default false) to change the default action for DROP TABLE and DROP VIEW (false for CASCADE, true for RESTRICT). The plan is to enable this property by default in version 1.3.x.
@changelog_1181_li
@changelog_1184_li
DROP TABLE now also supports CASCADE (still the default) and RESTRICT.
@changelog_1182_li
@changelog_1185_li
The wrong exception was thrown when trying to connect to a server if the server was not running.
@changelog_1183_li
@changelog_1186_li
UNION queries where the first query contains a nested query were parsed incorrectly. Example: "select 1 from (select 2 from dual) union select 3 from dual" was parsed as "select 1 from ((select 2 from dual) union select 3 from dual)". Fixed.
@changelog_1184_li
@changelog_1187_li
Support ALTER SCHEMA name RENAME TO newName (rename schema). (patch from Kerry Sainsbury)
@changelog_1185_h2
@changelog_1188_h2
Version 1.2.138 (2010-06-27)
@changelog_1186_li
@changelog_1189_li
Referential integrity: it was not allowed to delete a row with NULL in the parent table, if there was a row with NULL in the child table.
@changelog_1187_li
@changelog_1190_li
Experimental feature to support case sensitive catalog names and database names using the DATABASE() method. To use this feature, set the system property h2.databaseToUpper to false. The plan is to set the property to false by default in version 1.3.x. Issue 204 - thanks to Sylvain Cuaz (ILM Informatique) for the patch.
@changelog_1188_li
@changelog_1191_li
Experimental feature to support nested joins. To enable, set the system property h2.nestedJoins to true. If enabled, nested joins and right outer joins should work as expected (issues 145, 177, and 203). The plan is to enable this feature by default in version 1.3.x.
@changelog_1189_li
@changelog_1192_li
New sample application: CachedPreparedStatements.
@changelog_1190_li
@changelog_1193_li
When creating functions within a schema, those functions could not be used in views, nested queries, and constraints. Fixed.
@changelog_1191_li
@changelog_1194_li
The benchmarks have been run using recent database versions.
@changelog_1192_li
@changelog_1195_li
Version 1.2.137 could still not be converted to Java 1.4 (because the Retrotranslator doesn't support BigDecimal.precision).
@changelog_1193_li
@changelog_1196_li
Cluster: non-admin users could not connect when one of the cluster node was stopped. Issue 206.
@changelog_1194_li
@changelog_1197_li
DROP VIEW now supports the CASCADE and RESTRICT clauses (patch from Kerry Sainsbury)
@changelog_1195_li
@changelog_1198_li
CREATE VIEW now supports the OR REPLACE clause (patch from Kerry Sainsbury)
@changelog_1196_li
@changelog_1199_li
Build tool: ability to only run one test using the -Dtest=className setting. eg: build -Dtest=org.h2.test.db.TestViewDropView test (patch from Kerry Sainsbury).
@changelog_1197_h2
@changelog_1200_h2
Version 1.2.137 (2010-06-06)
@changelog_1198_li
@changelog_1201_li
Statements with a nested query and a condition that was always NULL threw an IndexOutOfBoundsException. Example: select * from (select null as x) where x=1
@changelog_1199_li
@changelog_1202_li
The changes that were made to support large transactions also fixed a bug with large transactions (when the undo log file size is larger than 2 GB).
@changelog_1200_li
@changelog_1203_li
Experimental feature to support very large transactions (except when using MVCC). To enable, set the system property h2.largeTransactions to true. If enabled, changes to tables without a primary key can be buffered to disk. The plan is to enable this feature by default in version 1.3.x.
@changelog_1201_li
@changelog_1204_li
H2 Console: editing result sets is now also working for database other than H2, if they do support updatable result sets. Add "@edit" before the query. Only limited testing has been done on this feature, some data types may not work (please provide feedback if you find issues).
@changelog_1202_li
@changelog_1205_li
Cluster: an open transaction was committed when a cluster node was stopped (because disabling the cluster executes SET CLUSTER '', which committed the transaction). Transaction are no longer committed when calling SET CLUSTER. Issue 199.
@changelog_1203_li
@changelog_1206_li
Cluster: non-admin users couldn't connect to the cluster and couldn't disable the cluster. Issue 201.
@changelog_1204_li
@changelog_1207_li
Cluster: NEXTVAL('sequence') was only called on one cluster node, therefore sequence values could get out of sync.
@changelog_1205_li
@changelog_1208_li
Version 1.2.136 could not be converted to Java 1.4 (because the Retrotranslator doesn't support BigDecimal.precision). A workaround has been implemented.
@changelog_1206_li
@changelog_1209_li
The error code of IO exceptions in CSV functions was incorrect.
@changelog_1207_li
@changelog_1210_li
The TriggerPassData example now uses a prefix (the database name).
@changelog_1208_li
@changelog_1211_li
The wrong exception was thrown when trying to reference a table that doesn't support references such as a table in the information schema.
@changelog_1209_li
@changelog_1212_li
Server.shutdownTcpServer can now stop all TCP servers on this JVM.
@changelog_1210_li
@changelog_1213_li
JdbcConnectionPool: the default connection timeout is now 30 seconds (it used to be 5 minutes).
@changelog_1211_li
@changelog_1214_li
LOB storage: LOBs added with "h2.lobInDatabase" enabled couldn't be read later with this option disabled.
@changelog_1212_h2
@changelog_1215_h2
Version 1.2.136 (2010-05-24)
@changelog_1213_li
@changelog_1216_li
When using ORDER BY and there are both ascending and descending indexes, the database used the first index even when the second one could be used for sorting.
@changelog_1214_li
@changelog_1217_li
Conditions of the form columnName IS NULL now use an index. To disable this feature, set the system property h2.optimizeIsNull to false.
@changelog_1215_li
@changelog_1218_li
H2 Console: when the settings were not stored yet (for example when running for the first time), the last recently used settings were not stored. A workaround was to create the file ".h2.server.properties" manually in the current user home directory, with the contents: webAllowOthers=false, webPort=8082, webSSL=false, 0=Generic H2 (Embedded)|org.h2.Driver|jdbc\:h2\:~/test|sa (where a comma is a newline).
@changelog_1216_li
@changelog_1219_li
The source code is now switched to Java 6 (JDK 1.6) by default. Java 5 (JDK 1.5) is still supported, and the jar file is still compiled for Java 5.
@changelog_1217_li
@changelog_1220_li
The BOM (the byte-order-mark) character 0xfeff at the beginning of the file is ignored. This is for compatibility with Microsoft Excel.
@changelog_1218_li
@changelog_1221_li
When opening an existing database, the cache size is set to at most half the amount of memory available for the virtual machine (Runtime.getRuntime().maxMemory()), even if the cache size setting stored in the database is larger. Setting the cache size in the database URL or explicitly using SET CACHE_SIZE overrides this value (even if larger than the physical memory).
@changelog_1219_li
@changelog_1222_li
INFORMATION_SCHEMA.SETTINGS: the cache size is now returned in KB.
@changelog_1220_li
@changelog_1223_li
New system property h2.selectForUpdateMvcc, the default is false (the feature is disabled). When enabled, SELECT ... FOR UPDATE only locks the selected rows in the MVCC mode. Aggregate or GROUP BY queries are not allowed in this case.
@changelog_1221_li
@changelog_1224_li
Profiler: improved message if there was no stack trace.
@changelog_1222_li
@changelog_1225_li
The H2 Console can now be used within another application, in a frame or iframe. Issue 197.
@changelog_1223_li
@changelog_1226_li
Recover tool: the statistics section now includes page type counts again.
@changelog_1224_li
@changelog_1227_li
Queries with multiple IN(...) conditions sometimes return the wrong results when there was a multi-column index for the column.
@changelog_1225_li
@changelog_1228_li
Queries with IN(..., NULL) did sometimes return the wrong results when there was a index for the column.
@changelog_1226_li
@changelog_1229_li
DECIMAL: faster precision and memory usage calculations.
@changelog_1227_li
@changelog_1230_li
A new class org.h2.tools.TriggerAdapter allows to use the ResultSet interface within trigger implementations.
@changelog_1228_li
@changelog_1231_li
A subselect which used an index could lead to wrong results. Fixed.
@changelog_1229_li
@changelog_1232_li
Creating a cached temporary non persistent table with a primary key threw a NullPointerException.
@changelog_1230_h2
@changelog_1233_h2
Version 1.2.135 (2010-05-08)
@changelog_1231_li
@changelog_1234_li
Temporary files were not deleted when using large transactions, disabling autocommit, and closing the session without committing.
@changelog_1232_li
@changelog_1235_li
Queries using multiple IN(..) conditions on the same table could cause repeated rows in the result set.
@changelog_1233_li
@changelog_1236_li
Translation: Lubomir Grajciar translated the H2 Console as well as all error message to Slovensky. Thanks a lot!
@changelog_1234_li
@changelog_1237_li
There was a possible Java level deadlock when opening an uninitialized database and using a file system that also opened a database.
@changelog_1235_li
@changelog_1238_li
When killing the process while the database was writing a checkpoint, while it was closing, or while running recovery (while removing temporary tables from a previous run), the database could become corrupt. A new test case has been implemented to ensure such problems can not occur in the future.
@changelog_1236_li
@changelog_1239_li
File system: new method FileSystem.setReadOnly.
@changelog_1237_li
@changelog_1240_li
The page size for new databases can now be set in the database URL using ;PAGE_SIZE=512. Currently this feature is only used to simplify testing.
@changelog_1238_li
@changelog_1241_li
New system property h2.functionsInSchema (default is false). If enabled, the SCRIPT statement always includes the schema name in the CREATE ALIAS statement (even if the schema is PUBLIC). This is not backward compatible with H2 versions 1.2.134 and older.
@changelog_1239_li
@changelog_1242_li
Functions: it is no longer required to add a space after a comma in the parameter list. Example: CREATE ALIAS PARSE_INT FOR "java.lang.Integer.parseInt(java.lang.String,int)"
@changelog_1240_li
@changelog_1243_li
Functions now reside within a schema, similar to sequences. If you do create such functions in schemas other than PUBLIC, then the database can not be opened with older versions of H2.
@changelog_1241_li
@changelog_1244_li
Cluster: after a cluster node failed, the second cluster node can now be re-created and started without having to stop the first cluster node, and without having to stop running applications. To do that, append ;AUTO_RECONNECT=TRUE to the database URL.
@changelog_1242_li
@changelog_1245_li
Auto-reconnect: if another connection uses the database in exclusive mode then this connection will try to re-connect until the exclusive mode ends. This is important when using the cluster mode.
@changelog_1243_li
@changelog_1246_li
SET EXCLUSIVE now supports 0 (disable), 1 (enable), and 2 (enable and close all other connections).
@changelog_1244_li
@changelog_1247_li
Installing the H2 as a service should now work on Windows 7. The batch files now explicitly set the directory using pushd "%~dp0".
@changelog_1245_li
@changelog_1248_li
Temporary tables can now be 'cached', that means indexes of temporary tables can be persisted. This enables very large temporary tables (both local and global).
@changelog_1246_li
@changelog_1249_li
The CreateCluster tool now sets the source database in exclusive mode before copying data to the new database.
@changelog_1247_li
@changelog_1250_li
The H2 Console now stream results one statement / result set at a time (using chunked transfer encoding). To disable, set the system property h2.consoleStream to false. This feature is not supported when using a servlet container.
@changelog_1248_li
@changelog_1251_li
The H2 Console did not call the CreateCluster tool with the correctly escaped parameters.
@changelog_1249_li
@changelog_1252_li
Improved PostgreSQL compatibility for ALTER TABLE ALTER COLUMN.
@changelog_1250_li
@changelog_1253_li
Commas at the end of INSERT ... VALUES (), (), are now supported.
@changelog_1251_li
@changelog_1254_li
The H2 Console "Start Browser" button now works even when the IP address changes while the tool runs (for example, because a wireless connection breaks, or when enabling / disabling the network connection).
@changelog_1252_li
@changelog_1255_li
When casting from float or double to BigDecimal, the result was sometimes unexpected, because "new BigDecimal(double val)" was used. Now "BigDecimal.valueOf(double val)" and "new BigDecimal(Float.toString(f))" are used. But it is still not recommended to use float or double for currency values (see data type documentation).
@changelog_1253_li
@changelog_1256_li
Global temporary tables are now deleted when closing the database. Before, they were deleted when opening the database the next time.
@changelog_1254_li
@changelog_1257_li
UNIQUE was not listed as a keyword.
@changelog_1255_li
@changelog_1258_li
Improved error message when an non-SQL-exception occurred in a user defined function. The method name and parameters are included in the error message.
@changelog_1256_li
@changelog_1259_li
For some queries, the exception did not include the SQL statement. Example: select x from system_range(1, 2) group by 'a'.
@changelog_1257_li
@changelog_1260_li
The Shell tool will execute SQL statements passed as using the command line parameter -sql.
@changelog_1258_li
@changelog_1261_li
If InetAddress.getLocalHost() fails, the database should now throw an exception.
@changelog_1259_li
@changelog_1262_li
New columns INFORMATION_SCHEMA.INDEXES.INDEX_CLASS and INFORMATION_SCHEMA.TABLES.TABLE_CLASS.
@changelog_1260_li
@changelog_1263_li
INFORMATION_SCHEMA.INDEXES.SQL now contains the CREATE INDEX statement instead of just the fully qualified index name.
@changelog_1261_h2
@changelog_1264_h2
Version 1.2.134 (2010-04-23)
@changelog_1262_li
@changelog_1265_li
New system property h2.analyzeAuto (default 0 meaning disabled) to automatically run ANALYZE after that many changes to a table. For details, see the Javadoc of this system property. The plan is to set this property to 2000 in version 1.3.x.
@changelog_1263_li
@changelog_1266_li
JdbcXAConnection.start() does not support TMJOIN. Issue 189.
@changelog_1264_li
@changelog_1267_li
MySQL compatibility: TIMESTAMPDIFF is now an alias for DATEDIFF.
@changelog_1265_li
@changelog_1268_li
MERGE did not respect foreign key and check constraints.
@changelog_1266_li
@changelog_1269_li
ALTER TABLE ALTER COLUMN: changing the data type of a column no longer makes it nullable.
@changelog_1267_li
@changelog_1270_li
When using AUTO_SERVER=TRUE, the server is now started as a daemon thread. This was a problem when using Tomcat and a connection pool.
@changelog_1268_li
@changelog_1271_li
Servers can now be started as a daemon thread using the command line options -tcpDaemon, -pgDaemon, and -webDaemon.
@changelog_1269_li
@changelog_1272_li
H2 Console: the built-in commands are now documented.
@changelog_1270_li
@changelog_1273_li
REPLACE: if any parameter is null, the result is null.
@changelog_1271_li
@changelog_1274_li
Queries with DISTINCT and ORDER BY will now use the index on ORDER BY if possible. This is specially important for queries used inside IN(SELECT ...).
@changelog_1272_li
@changelog_1275_li
The new statement EXPLAIN ANALYZE executes the statement, and displays the query plan with the actual row scan count for each table.
@changelog_1273_li
@changelog_1276_li
H2 Console: the auto-complete feature didn't quote column names that need quoting. Issue 186.
@changelog_1274_li
@changelog_1277_li
The experimental LOB storage mechanism now supports all features of the old one. To use it, set the system property "h2.lobInDatabase" to "true". If you have used this feature in version 1.2.133, you need to export and re-import the database using SCRIPT / RUNSCRIPT.
@changelog_1275_li
@changelog_1278_li
The functions isBeforeFirst() and isAfterLast() were not compliant to the JDBC spec. If the ResultSet contains no rows, they must return false. Fixed.
@changelog_1276_li
@changelog_1279_li
Filesystem parameters like "split:" didn't work in server mode with baseDir set.
@changelog_1277_li
@changelog_1280_li
If baseDir is set, and a database name is given which points to a directory outside the baseDir (eg. "../dbname"), an exception is thrown.
@changelog_1278_h2
@changelog_1281_h2
Version 1.2.133 (2010-04-10)
@changelog_1279_li
@changelog_1282_li
A new experimental LOB storage mechanism is available. When enabled, CLOB and BLOB data is stored in hidden tables in the database. To use it, set the system property "h2.lobInDatabase" to "true". Compression is not yet implemented. Duplicate objects are only stored once. Usually writing is slower, but reading is faster (mainly because of caching).
@changelog_1280_li
@changelog_1283_li
The Shell tool threw a NumberFormatException on a empty statement.
@changelog_1281_li
@changelog_1284_li
The h2small-*.jar did not support "drop all objects delete files". Now it is supported (the DeleteDbFiles tool is now included).
@changelog_1282_li
@changelog_1285_li
Operations that don't fit in memory are now faster. Temporary file handling was changed.
@changelog_1283_li
@changelog_1286_li
The default maximum log stream size is now 2 MB. This is a good value according to some performance tests.
@changelog_1284_li
@changelog_1287_li
New system property "h2.syncMethod" to configure what method to call when closing the database, on checkpoint, and on CHECKPOINT SYNC. The default is "sync" which calls RandomAccessFile.getFD().sync().
@changelog_1285_li
@changelog_1288_li
ROWNUM could not be used for pagination. The follow query returned no rows: select x from (select *, rownum as r from system_range(1, 3)) where r=2;
@changelog_1286_li
@changelog_1289_li
Workaround for a java.sql.Date issue: years above 9999 are not formatted correctly. When calling ResultSet.getString() on a date value, an alternative formatting algorithm is used.
@changelog_1287_li
@changelog_1290_li
Prepared statements with nested subqueries did not always return the correct result. Example: select ?, ?, (select count(*) from test t, (select id from test where 0=?) t2 where t2.id=t.id) from test
@changelog_1288_li
@changelog_1291_li
When using MULTI_THREADED=TRUE, the exception following exception could be thrown: "object already exists: TABLES"
@changelog_1289_li
@changelog_1292_li
Comparison of integer columns against float numbers was not always correct. Issue 182.
@changelog_1290_li
@changelog_1293_li
H2 Console: Editing the result of a multi-line queries failed. Issue 183.
@changelog_1291_li
@changelog_1294_li
H2 Console: if the settings file (.h2.properties) can't be accessed, the exception is now ignored.
@changelog_1292_h2
@changelog_1295_h2
Version 1.2.132 (2010-03-21)
@changelog_1293_li
@changelog_1296_li
The implementation of a Java to C (source code level) converter has been started. The plan is: it should be possible to convert H2 (or a part of it) to C so that the database can be run without a JVM. This will be a long term project (it may take a year or so).
@changelog_1294_li
@changelog_1297_li
User defined table implementation can now be used using CREATE TABLE ... ENGINE. Thanks to Sergi Vladykin for implementing this feature!
@changelog_1295_li
@changelog_1298_li
Improved MS SQL Server compatibility: support string concatenation using "+". Thanks to Stepan for the patch!
@changelog_1296_li
@changelog_1299_li
When using the multi-threaded mode, running ANALYZE concurrently in multiple connections could throw an exception.
@changelog_1297_li
@changelog_1300_li
The MERGE statement is now about 30% faster when using a PreparedStatement.
@changelog_1298_li
@changelog_1301_li
Multi-column indexes where the second or later column was descending did not always produce correct results (rows were missing in the result set, or the result set was empty).
@changelog_1299_li
@changelog_1302_li
When using large transactions or a small log size, the database could get very slow (profiling shows the hotspot is in FileObjectDisk.sync()).
@changelog_1300_li
@changelog_1303_li
The Shell tool now prints the stack trace when the list mode is enabled.
@changelog_1301_li
@changelog_1304_li
CREATE ALIAS ... AS: Compilation was incorrect if the source code contained characters that are not supported by the default file encoding.
@changelog_1302_li
@changelog_1305_li
Issue 176: the JdbcDataSource now also supports a 'description' property.
@changelog_1303_li
@changelog_1306_li
The Shell tool threw a ArrayIndexOutOfBoundsException after 20 statements.
@changelog_1304_li
@changelog_1307_li
When using the small version of H2 ('jarClient'), the first call to Connection.createBlob (or similar) could throw a ClassNotFoundException because the file org.h2.store.fs.FileSystemZip is not included. This missing class is now ignored.
@changelog_1305_li
@changelog_1308_li
Literals of type BIGINT now have the correct data type.
@changelog_1306_h2
@changelog_1309_h2
Version 1.2.131 (2010-03-05)
@changelog_1307_li
@changelog_1310_li
Older versions of H2 (version 1.2.127 and older) could not connect to a new version (version 1.2.129 and newer). The connection blocked when trying to connect. Now the connection no longer blocks, instead a SQL exception is thrown.
@changelog_1308_li
@changelog_1311_li
In versions 1.2.129 and 1.2.130, a database could not be opened sometimes after dropping tables or indexes, and then creating new indexes for existing tables. The exception contained the text "parent not found" (version 1.2.129) or "Table not found" (version 1.2.130).
@changelog_1309_li
@changelog_1312_li
After the database was closed, a null pointer exception could occur in Database.flush.
@changelog_1310_li
@changelog_1313_li
An ArrayIndexOutOfBoundsException could occur in the page store (eg. on "delete from table"). Fixed.
@changelog_1311_h2
@changelog_1314_h2
Version 1.2.130 (2010-02-26)
@changelog_1312_li
@changelog_1315_li
EXPLAIN: The query plan now contains ".tableScan" if a table scan is used.
@changelog_1313_li
@changelog_1316_li
IN(..): when combining and IN(..) condition with a condition that didn't use an index, the result could contain duplicate rows.
@changelog_1314_li
@changelog_1317_li
IN(..): the index was not used if there were multiple IN(..) conditions.
@changelog_1315_li
@changelog_1318_li
For foreign key constraints, the metadata column INFORMATION_SCHEMA.INDEXES.CONSTRAINT_NAME was not set for non-unique indexes.
@changelog_1316_li
@changelog_1319_li
PostgreSQL compatibility: when using the following exception was thrown: Column "T.TYPTYPMOD" not found. Fixed. This is only when using psqlodbc_08_04*.
@changelog_1317_li
@changelog_1320_li
A tool to migrate an old database from the non-page store format to the newest version has been added in src/tools/org/h2/dev/util/Migrate.java. This file is not included in the jar file currently.
@changelog_1318_li
@changelog_1321_li
When using temporary tables, the database didn't shrink sometimes when closing. Also, sometimes a database could not recover normally.
@changelog_1319_li
@changelog_1322_li
Large transactions could run out of heap space. The maximum size of a transaction is now much larger.
@changelog_1320_li
@changelog_1323_li
The default setting for the system property h2.webMaxValueLength is now 100000 (it was 10000 before).
@changelog_1321_li
@changelog_1324_li
Creating a database was delayed about 2 seconds if the directory didn't exist.
@changelog_1322_li
@changelog_1325_li
Implemented INIT feature. If the database URL contains ";INIT=...;" then the DDL or DML commands following are executed on startup. Example URL: jdbc:h2:mem:test;INIT=RUNSCRIPT FROM '~/create.sql' (patch from Kerry Sainsbury).
@changelog_1323_h2
@changelog_1326_h2
Version 1.2.129 (2010-02-19)
@changelog_1324_li
@changelog_1327_li
The methods of the CloseListener are added to the Trigger interface. The interface CloseListener is removed. This is potentially a breaking change for existing triggers.
@changelog_1325_li
@changelog_1328_li
CREATE ALIAS: error message when compiling Java code have been improved.
@changelog_1326_li
@changelog_1329_li
MVCC: creating a table with an incorrect constraint could cause strange errors.
@changelog_1327_li
@changelog_1330_li
Hash indexes now are only used for single column indexes.
@changelog_1328_li
@changelog_1331_li
The cache types WEAK_* and TQ are no longer supported. A weak reference cache never frees up memory so it's the same as having a very large cache size. The TQ cache was not included in the jar file since a longer time, and was not tested.
@changelog_1329_li
@changelog_1332_li
The file system abstraction no longer throws SQL exceptions.
@changelog_1330_li
@changelog_1333_li
DatabaseEventListener.diskSpaceIsLow has changed.
@changelog_1331_li
@changelog_1334_li
The CompressTool no longer throw as SQL exceptions. Instead, it throws runtime exceptions.
@changelog_1332_li
@changelog_1335_li
SimpleResultSet.addColumn and addRow now can throw a IllegalStateException instead of a SQLException.
@changelog_1333_li
@changelog_1336_li
When doing an index lookup, decimal values with the same value but different scale (for example 0.00 and 0.0) where not considered equal in version 1.2.128. Now they are (unlike BigDecimal.equals()).
@changelog_1334_li
@changelog_1337_li
The BNF parser now uses the visitor pattern.
@changelog_1335_li
@changelog_1338_li
Converting a UUID to bytes was incorrect. Because of that, updatable result sets on tables with UUID primary key did not work.
@changelog_1336_li
@changelog_1339_li
The database URL property DATABASE_EVENT_LISTENER_OBJECT is no longer supported (there are problems passing objects when the PostgreSQL driver is installed as well).
@changelog_1337_li
@changelog_1340_li
H2 Console: asynchronous login (using a DatabaseEventListener) is no longer supported.
@changelog_1338_li
@changelog_1341_li
A workaround for a Windows socket problem has been implemented. Thanks a lot to Sergi Vladykin.
@changelog_1339_li
@changelog_1342_li
The Recover tool did not convert correctly convert CLOB data with non-ASCII characters.
@changelog_1340_li
@changelog_1343_li
Tools: the method run(String... args) has been renamed to runTool(String... args).
@changelog_1341_li
@changelog_1344_li
Server.startWebServer(Connection) was not working as expected.
@changelog_1342_li
@changelog_1345_li
The database URL option ACCESS_MODE_LOG is no longer supported.
@changelog_1343_li
@changelog_1346_li
The database URL option RECOVER has currently no effect.
@changelog_1344_li
@changelog_1347_li
Converting an old (non-page store) database is no longer supported using this version.
@changelog_1345_li
@changelog_1348_li
The following system properties are no longer supported: h2.overflowExceptions, h2.optimizeDropDependencies, h2.optimizeGroupSorted, h2.optimizeMinMax, h2.optimizeNot, h2.optimizeIn, h2.optimizeInJoin, h2.reuseSpace*. Most of then were there for a long time, but always with the same value. There was no unit test with the other value. So changing them was potentially dangerous (not a lot, but still).
@changelog_1346_li
@changelog_1349_li
The setting LOG has currently no effect (it only had an effect when the page store was disabled).
@changelog_1347_li
@changelog_1350_li
Disabling the page store is no longer supported. The old storage mechanism has been removed, shrinking the jar file size by almost 10%.
@changelog_1348_li
@changelog_1351_li
The translated resources are now stored in UTF-8 format.
@changelog_1349_li
@changelog_1352_li
The Windows service wrapper now detects if multiple versions of H2 are installed.
@changelog_1350_h2
@changelog_1353_h2
Version 1.2.128 (2010-01-30)
@changelog_1351_li
@changelog_1354_li
There are known errors on rollback when the page store is disabled and at the same time MVCC is used. See http://code.google.com/p/h2database/issues/detail?id=158
@changelog_1352_li
@changelog_1355_li
The DeleteDbFiles tool deleted all files in the .lob.db directory, even files that didn't belong to the database.
@changelog_1353_li
@changelog_1356_li
Automatic conversion of old databases to the page store format failed if the database contained LOB files.
@changelog_1354_li
@changelog_1357_li
Nested subqueries didn't work for INSERT INTO and IN(..). Example: insert into test ((select 1));
@changelog_1355_li
@changelog_1358_li
If the database was already closed using SHUTDOWN IMMEDIATELY, closing a second connection could throw a NullPointerException if there was a local temporary table.
@changelog_1356_li
@changelog_1359_li
Less classes are loaded when using the database in embedded mode.
@changelog_1357_li
@changelog_1360_li
The information schema tables are only initialized when needed. This reduces memory usage and speeds up creating in-memory databases. Each in-memory database needs about 8 KB of heap memory.
@changelog_1358_li
@changelog_1361_li
Nested UNION/INTERSECT queries with brackets could produce the wrong result if used within a subquery. Example: select count(*) from (select 1 union (select 2 intersect select 2)) x;
@changelog_1359_li
@changelog_1362_li
Comparing an column against a constant expression with a higher precision or length than the column could give wrong results (the expression was truncated before comparing).
@changelog_1360_li
@changelog_1363_li
Improved PostgreSQL compatibility (support SHOW DEFAULT_TRANSACTION_ISOLATION).
@changelog_1361_li
@changelog_1364_li
Documentation: the javadocs for Csv.write and read used the wrong default charset.
@changelog_1362_li
@changelog_1365_li
MVCC: if the table was locked in exclusive mode (such as SELECT ... FOR UPDATE), another session could query the table. This is now longer possible.
@changelog_1363_li
@changelog_1366_li
If a FOR UPDATE query was executed twice (using a PreparedStatement), the table was not locked.
@changelog_1364_li
@changelog_1367_li
Triggers: INSTEAD OF triggers are now supported. Such triggers can be defined on views.
@changelog_1365_li
@changelog_1368_li
New system property h2.identifiersToUpper. If set to false, identifiers in SQL statements are case sensitive even if they are not quoted.
@changelog_1366_li
@changelog_1369_li
Slightly improved performance if the table is already locked.
@changelog_1367_li
@changelog_1370_li
CompressLZF: faster decompression.
@changelog_1368_li
@changelog_1371_li
PgServer: the wrong size was sent for VARCHAR data. Thanks again to Sergi Vladykin for the patch.
@changelog_1369_li
@changelog_1372_li
Serialized access mode (server-less multi-connection mode): fixed getGeneratedKeys() for sequences.
@changelog_1370_h2
@changelog_1373_h2
Version 1.2.127 (2010-01-15)
@changelog_1371_li
@changelog_1374_li
Serialized access mode (server-less multi-connection mode): sequences did not work as expected (there were gaps in generated values when using multiple connections).
@changelog_1372_li
@changelog_1375_li
Page store: new databases can not be opened with older versions.
@changelog_1373_li
@changelog_1376_li
Page store: adding data to new database is now faster.
@changelog_1374_li
@changelog_1377_li
File system: getting the file name from a path is now faster. This should speed up BLOB and CLOB access.
@changelog_1375_li
@changelog_1378_li
PgServer: incorrect SQL types were returned in result set meta data. Concurrently opening a database could fail (PG catalog initialization was not synchronized). Thanks a lot to Sergi Vladykin for providing the patches!
@changelog_1376_li
@changelog_1379_li
SHOW COLUMNS did not work correctly if there where multiple indexes on the same columns.
@changelog_1377_li
@changelog_1380_li
Page store: the wrong write count was written to the database header. This could cause the server-less multi-connection mode to fail.
@changelog_1378_li
@changelog_1381_li
Result sets larger than 2 GB threw an exception "Negative seek offset". Fixed.
@changelog_1379_li
@changelog_1382_li
If the system property h2.check was set to false, an ArrayIndexOutOfBoundsException could occur.
@changelog_1380_li
@changelog_1383_li
Alter table is now supported even if a table has views defined. (Patch from Kerry Sainsbury).
@changelog_1381_li
@changelog_1384_li
Fulltext search: exceptions within the fulltext search package had the wrong SQL state.
@changelog_1382_li
@changelog_1385_li
The Lucene fulltext search ignored transaction rollback. Fixed using a trigger on rollback.
@changelog_1383_li
@changelog_1386_li
Trigger can now be called on rollback.
@changelog_1384_li
@changelog_1387_li
The shell script h2.sh ignored command line line arguments.
@changelog_1385_li
@changelog_1388_li
When running H2 in the Google AppEngine for Java, a AccessControlException could be thrown when trying to open a read-only database. Fixed.
@changelog_1386_li
@changelog_1389_li
The user home directory prefix (~) is now only expanded when followed by a slash or backslash, or standing alone.
@changelog_1387_li
@changelog_1390_li
Native fulltext search: before inserting or deleting data, FT_INIT() had to be called. This is no longer required.
@changelog_1388_li
@changelog_1391_li
The .trace.db file is now only created if required.
@changelog_1389_li
@changelog_1392_li
Shell tool: improved PostgreSQL compatibility.
@changelog_1390_li
@changelog_1393_li
Trying to open a database in read-only mode when a .lock.db file exists will now fail with a nice error message.
@changelog_1391_li
@changelog_1394_li
H2 Console: data that is too long is now abbreviated as follows: text... (100000 characters). A large binary is abbreviated as follows: abcdef... (100000 bytes).
@changelog_1392_li
@changelog_1395_li
Faster data conversion from BIGINT or INT to DECIMAL.
@changelog_1393_li
@changelog_1396_li
Server-less multi-connection mode: try to delete log files if switching between read/write operations.
@changelog_1394_li
@changelog_1397_li
CompressLZF: Faster decompress and improved javadocs
@changelog_1395_h2
@changelog_1398_h2
Version 1.2.126 (2009-12-18)
@changelog_1396_li
@changelog_1399_li
The ChangeFileEncryption tool will now fail with an exception if the database is still in use. The Backup tool will also fail except when running in quiet mode.
@changelog_1397_li
@changelog_1400_li
CSVREAD: when reading the column names from the CSV file, column names that contain no special characters are considered case insensitive now.
@changelog_1398_li
@changelog_1401_li
Optimization index conditions of the form 'column=NULL' (which is always false; unlike 'column IS NULL').
@changelog_1399_li
@changelog_1402_li
Script command and tool: the primary key constraint is now listed before inserting the data. This will result in a smaller database when using the page store.
@changelog_1400_li
@changelog_1403_li
Statements with IN(SELECT..) conditions could produce the wrong result. Example: index on id, name; query: select * from test where id between 1 and 3 and name in (select 'World').
@changelog_1401_li
@changelog_1404_li
Statements with IN(..) conditions could produce the wrong result when using views or nested select statements. Example: index on id; index on name; query: select * from (select * from test) where id=1 and name in('a', 'b'). select * from (select * from test) where id=1 and name in('Hello', 'World').
@changelog_1402_li
@changelog_1405_li
Page store: a rollback of a relatively large transaction could fail with an ArrayIndexOutOfBoundsException or a 'row not found' exception in the PageBtreeIndex in some cases.
@changelog_1403_li
@changelog_1406_li
JaQu: the decompiler has been improved, and a few test cases already work. It is still incomplete however.
@changelog_1404_li
@changelog_1407_li
LIKE: any letter is now allowed after the escape character (which is still '\' by default). Previously, an exception was thrown (unlike other databases) if it was not the escape character, '_' or '%'. If the escape character appears at the end of the pattern, the result is it is ignored (like PostgreSQL and MS SQL Server).
@changelog_1405_li
@changelog_1408_li
The reserve heap memory is no longer used.
@changelog_1406_li
@changelog_1409_li
Database.checkpoint() could throw a NullPointerException.
@changelog_1407_h2
@changelog_1410_h2
Version 1.2.125 (2009-12-06)
@changelog_1408_li
@changelog_1411_li
Lucene fulltext search: the Lucene field names now match the table column names, except if the column names start with _ (in which case another _ is prepended). Unfortunately this change means existing fulltext indexes need to be re-built.
@changelog_1409_li
@changelog_1412_li
The shell tool now has a very simple statement history.
@changelog_1410_li
@changelog_1413_li
The zip file system implementation now supports the '~' home directory prefix. Example database URL: jdbc:h2:zip:~/test.zip!/test
@changelog_1411_li
@changelog_1414_li
Right outer joins on tables that were already 'inner joined' was processed incorrectly.
@changelog_1412_li
@changelog_1415_li
Temporary files from LOB objects were not deleted early enough when using the server mode.
@changelog_1413_li
@changelog_1416_li
Trying to alter a temporary table threw a strange exception. It is still not possible to do that, but the exception message is better now.
@changelog_1414_li
@changelog_1417_li
When the system property h2.maxMemoryRowsDistinct was set, and using SELECT DISTINCT, the temporary table was not correctly dropped. This could cause problems in recovery when the process was killed.
@changelog_1415_li
@changelog_1418_li
Trigger that are called before a select statement are now supported. This allows to create tables that work like materialized views.
@changelog_1416_li
@changelog_1419_li
Non-row based triggers were called even if the action didn't match the declared action (INSERT triggers were also called when deleting rows). This has been changed. The MERGE statement calls both INSERT and DELETE triggers.
@changelog_1417_li
@changelog_1420_li
Statements with IN(..) conditions could produce the wrong result or a data conversion error (since version 1.2.120). Examples: index on id, name, condition: id=1 and name in('Hello', 'x'); index on id, query: select * from (select * from test) where id=1 and name in('Hello', 'World').
@changelog_1418_li
@changelog_1421_li
The CompressTool was not multithreading safe. Because of this, the following database operations where also not multithreading safe (even when using different databases): the SCRIPT command (only when using compression), the COMPRESS function, and storing CLOB or BLOB data (only when compression is enabled).
@changelog_1419_li
@changelog_1422_li
The compression algorithm "LZF" is now about 33% faster than before when compressing small block (around 2 KB). It is much faster than Deflate, but the compression ratio is lower. Some of the optimizations are from Sam Van Oort, thanks a lot!
@changelog_1420_li
@changelog_1423_li
Compressing large blocks of data didn't work when using the "Deflate" compression algorithm. Compressing a lot of data could run out of heap memory.
@changelog_1421_li
@changelog_1424_li
The test cases don't access the file system directly, this simplifies GAE for Java testing. Thanks to Vince Bonfanti.
@changelog_1422_li
@changelog_1425_li
More bugs in the server-less multi-connection mode have been fixed.
@changelog_1423_li
@changelog_1426_li
When running against an old database, the SCRIPT statement could generate a SQL script that contained duplicate indexes (PRIMARY_KEY_E).
@changelog_1424_li
@changelog_1427_li
JdbcConnectionPool.getConnection() could throw a NullPointerException.
@changelog_1425_li
@changelog_1428_li
User defined functions: the source code is now available using SELECT SOURCE FROM INFORMATION_SCHEMA.FUNCTION_ALIASES.
@changelog_1426_li
@changelog_1429_li
User defined functions with source code didn't work after re-opening the database.
@changelog_1427_li
@changelog_1430_li
The newsfeeds are now Atom 1.0 standard compliant.
@changelog_1428_li
@changelog_1431_li
The database is now closed after an out of memory exception, because the database could get corrupt otherwise.
@changelog_1429_li
@changelog_1432_li
Better error message if both AUTO_SERVER and SERIALIZED parameters are set to TRUE.
@changelog_1430_li
@changelog_1433_li
Drop table did not delete lob files in old file store (not PAGE_STORE).
@changelog_1431_h2
@changelog_1434_h2
Version 1.2.124 (2009-11-20)
@changelog_1432_li
@changelog_1435_li
Clustering: there is now a way to detect which cluster instances are running.
@changelog_1433_li
@changelog_1436_li
ConvertTraceFile: the SQL statement statistics are better formatted (newline are removed).
@changelog_1434_li
@changelog_1437_li
The file lock thread is now stopped when the database is closed.
@changelog_1435_li
@changelog_1438_li
Issue 140: the Script tool now supports writing to a stream.
@changelog_1436_li
@changelog_1439_li
Issue 138: the trace output of Statement.execute(String, int) and executeUpdate was incorrect.
@changelog_1437_li
@changelog_1440_li
Page store: new databases can not be opened with older versions.
@changelog_1438_li
@changelog_1441_li
Page store: multi-column indexes didn't work if the cache was very small.
@changelog_1439_li
@changelog_1442_li
Page store: opening a database could theoretically result in an endless loop.
@changelog_1440_li
@changelog_1443_li
Page store: adding large indexed columns could get very slow.
@changelog_1441_li
@changelog_1444_li
Page store: after a duplicate key exception, an ArrayIndexOutOfBoundsException could be thrown (only for very large rows).
@changelog_1442_li
@changelog_1445_li
Page store: the recover tool sometimes generated a script file that contained duplicate data.
@changelog_1443_li
@changelog_1446_li
Page store: sometimes opening a read-only database failed.
@changelog_1444_li
@changelog_1447_li
Page store: opening a database sometimes failed if large rows where updated, or if a table was truncated before.
@changelog_1445_li
@changelog_1448_li
Page store: when using a very small page size (128 bytes or smaller), writing a large row could result in an endless recursion. This is only a theoretical problem, as the page size is 2 KB.
@changelog_1446_li
@changelog_1449_li
Page store: getting the min value from a descending index with NULL entries could return the wrong result.
@changelog_1447_li
@changelog_1450_li
Page store: improved auto-recovery after power failure.
@changelog_1448_li
@changelog_1451_li
The JDBC client did not detect that it was not talking to an H2 server. This could result in strange exceptions when trying to connect to another kind of server.
@changelog_1449_li
@changelog_1452_li
User defined functions can be created with source code. Example: CREATE ALIAS HI AS 'String hi() { return "Hello"; }'
@changelog_1450_li
@changelog_1453_li
Database file lock: the exception "lock file modified in the future" is no longer thrown; instead, opening the file will be delayed by 2 seconds.
@changelog_1451_li
@changelog_1454_li
Inserting LOBs got slower each time the process was restarted. It could loop endlessly after about 1000 process restarts.
@changelog_1452_li
@changelog_1455_li
Issue 117: Multi-version concurrency: concurrent MERGE statements now work.
@changelog_1453_li
@changelog_1456_li
Improved read-only database detection.
@cheatSheet_1000_h1
...
...
@@ -5555,7 +5570,7 @@ JaQu
What is JaQu
@jaqu_1012_p
JaQu stands for Java Query and allows to access databases using pure Java. JaQu provides a fluent interface (or internal DSL) to access a database. JaQu is something like LINQ for Java (LINQ stands for "language integrated query" and is a Microsoft .NET technology). The following JaQu code:
JaQu stands for Java Query and allows to access databases using pure Java. JaQu provides a fluent interface (or internal DSL). JaQu is something like LINQ for Java (LINQ stands for "language integrated query" and is a Microsoft .NET technology). The following JaQu code:
@jaqu_1013_p
stands for the SQL statement:
...
...
@@ -5564,13 +5579,13 @@ What is JaQu
Differences to Other Data Access Tools
@jaqu_1015_p
Unlike SQL, JaQu can be easily integrated in Java applications. Because JaQu is pure Java, auto-complete in the IDE and Javadoc and are supported. Type checking is performed by the compiler. JaQu fully protects against SQL injection.
Unlike SQL, JaQu can be easily integrated in Java applications. Because JaQu is pure Java, auto-complete in the IDE is supported. Type checking is performed by the compiler. JaQu fully protects against SQL injection.
@jaqu_1016_p
JaQu is more a replacement for JDBC than it is a replacement for tools like Hibernate. With JaQu, you don't write SQL statements as Strings. JaQu is much smaller and simpler than other persistence frameworks such as Hibernate, but it also does not provide all the features of those. Unlike iBatis and Hibernate, no XML or annotation based configuration is required; instead the configuration (if required at all) is done in pure Java, in the application itself.
JaQu is meant as replacement for JDBC and SQL and not as much as a replacement for tools like Hibernate. With JaQu, you don't write SQL statements as strings. JaQu is much smaller and simpler than other persistence frameworks such as Hibernate, but it also does not provide all the features of those. Unlike iBatis and Hibernate, no XML or annotation based configuration is required; instead the configuration (if required at all) is done in pure Java, within the application.
@jaqu_1017_p
JaQu does not require or contain any data caching mechanism. Like JDBC and iBatis, JaQu provides full control over when and what SQL statements are executed (but without having to write SQL statements as Strings).
JaQu does not require or contain any data caching mechanism. Like JDBC and iBatis, JaQu provides full control over when and what SQL statements are executed (but without having to write SQL statements as strings).
@jaqu_1018_h3
Restrictions
...
...
@@ -5582,7 +5597,7 @@ Restrictions
Why in Java?
@jaqu_1021_p
Most people use Java in their application. Mixing Java and another language (for example Scala or Groovy) in the same application is complicated: you would need to split the application and database code.
Most applications are written in Java. Mixing Java and another language (for example Scala or Groovy) in the same application is complicated: you would need to split the application and database code, and write adapter / wrapper code.
@jaqu_1022_h2
Current State
...
...
@@ -5621,22 +5636,22 @@ Example Code
Configuration
@jaqu_1034_p
JaQu does not require any configuration when using the default mapping. To define table indices, or if you want to map a class to a table with a different name, or a field to a column with another name, create a function called <code>define</code> in the data class. Example:
JaQu does not require any configuration when using the default field to column mapping. To define table indices, or if you want to map a class to a table with a different name, or a field to a column with another name, create a function called <code>define</code> in the data class. Example:
@jaqu_1035_p
The method <code>define()</code> contains the mapping definition. It is called once when the class is used for the first time. Like annotations, the mapping is defined in the class itself. Unlike when using annotations, the compiler can check the syntax even for multi-column objects (multi-column indexes, multi-column primary keys and so on). Because the definition is written in regular Java, the configuration can depend on the environment. This is not possible using annotations. Unlike XML mapping configuration, the configuration is integrated in the class itself.
The method <code>define()</code> contains the mapping definition. It is called once when the class is used for the first time. Like annotations, the mapping is defined in the class itself. Unlike when using annotations, the compiler can check the syntax even for multi-column objects (multi-column indexes, multi-column primary keys and so on). Because the definition is written in Java, the configuration can be set at runtime, which is not possible using annotations. Unlike XML mapping configuration, the configuration is integrated in the class itself.
@jaqu_1036_h2
Natural Syntax
@jaqu_1037_p
The plan is to support more natural (pure Java) syntax in conditions. To do that, the condition class is de-compiled to a SQL condition. A proof of concept decompiler is included (but it doesn't work yet). The planned syntax is:
The plan is to support more natural (pure Java) syntax in conditions. To do that, the condition class is de-compiled to a SQL condition. A proof of concept decompiler is included (but it doesn't fully work yet; patches are welcome). The planned syntax is:
@jaqu_1038_h2
Other Ideas
@jaqu_1039_p
This project has just been started, and nothing is fixed yet. Some ideas for what to implement are:
This project has just been started, and nothing is fixed yet. Some ideas are:
@jaqu_1040_li
Support queries on collections (instead of using a database).
...
...
@@ -5705,10 +5720,10 @@ Summary and License FAQ
H2 is dual licensed and available under a modified version of the MPL 1.1 (<a href="http://www.mozilla.org/MPL">Mozilla Public License</a>) or under the (unmodified) EPL 1.0 (<a href="http://opensource.org/licenses/eclipse-1.0.php">Eclipse Public License</a>). The changes to the MPL are
@license_1006_em
underlined</em>. There is a License FAQ for both the MPL and the EPL, most of that is applicable to the H2 License as well.
underlined</em>. There is a license FAQ for both the MPL and the EPL, most of that is applicable to the H2 license as well.
@license_1007_li
You can use H2 for free. You can integrate it into your application (including commercial applications), and you can distribute it.
You can use H2 for free. You can integrate it into your applications (including in commercial applications), and you can distribute it.
@license_1008_li
Files containing only your code are not covered by this license (it is 'commercial friendly').
...
...
@@ -6170,7 +6185,7 @@ Eclipse Public License - Version 1.0
H2 In Use and Links
@links_1001_p
Those are just a few links to products using or supporting H2. If you want to add a link, please send it to the support email address or post it in the group.
Listed below are just a few links to products using or supporting H2. If you want to add a link, please send it to the support email address or post it to the group.
@links_1002_a
Books
...
...
@@ -10111,16 +10126,19 @@ Require appending DANGEROUS=TRUE when using certain dangerous settings such as L
@roadmap_1481_li
Allow to defragment at runtime (similar to SHUTDOWN DEFRAG) in a background thread.
@roadmap_1482_h2
@roadmap_1482_li
Support for Thread.interrupt to cancel running statements.
@roadmap_1483_h2
Not Planned
@roadmap_1483_li
@roadmap_1484_li
HSQLDB (did) support this: select id i from test where i<0 (other databases don't). Supporting it may break compatibility.
@roadmap_1484_li
@roadmap_1485_li
String.intern (so that Strings can be compared with ==) will not be used because some VMs have problems when used extensively.
@roadmap_1485_li
@roadmap_1486_li
In prepared statements, identifier names (table names and so on) can not be parameterized. Adding such a feature would complicate the source code without providing reasonable speedup, and would slow down regular prepared statements.
@sourceError_1000_h1
...
...
@@ -11033,7 +11051,7 @@ Using the Native Fulltext Search
Using the Lucene Fulltext Search
@tutorial_1290_p
To use the Lucene full text search, you need the Lucene library in the classpath. Currently only Apache Lucene version 2.x is supported. How to do that depends on the application; if you use the H2 Console, you can add the Lucene jar file to the environment variables <code>H2DRIVERS</code> or <code>CLASSPATH</code>. To initialize the Lucene fulltext search in a database, call:
To use the Lucene full text search, you need the Lucene library in the classpath. Currently Apache Lucene version 2.x is used by default for H2 version 1.2.x, and Lucene version 3.x is used by default for H2 version 1.3.x. How to do that depends on the application; if you use the H2 Console, you can add the Lucene jar file to the environment variables <code>H2DRIVERS</code> or <code>CLASSPATH</code>. To initialize the Lucene fulltext search in a database, call:
@tutorial_1291_p
You need to initialize it in each database where you want to use it. Afterwards, you can create a full text index for a table using:
# To create the file <code>h2client.jar</code>, go to the directory <code>h2</code> and execute the following command:
@build_1045_h2
@build_1045_h3
#Using Lucene 2 / 3
@build_1046_p
# Both Apache Lucene 2 and Lucene 3 are supported. Currently Apache Lucene version 2.x is used by default for H2 version 1.2.x, and Lucene version 3.x is used by default for H2 version 1.3.x. To use a different version of Lucene when compiling, it needs to be specified as follows:
@build_1047_h2
Maven 2 の利用
@build_1046_h3
@build_1048_h3
Centralリポジトリの利用
@build_1047_p
@build_1049_p
# You can include the database in your Maven 2 project as a dependency. Example:
@build_1048_p
@build_1050_p
# New versions of this database are first uploaded to http://hsql.sourceforge.net/m2-repo/ and then automatically synchronized with the main Maven repository; however after a new release it may take a few hours before they are available there.
@build_1049_h3
@build_1051_h3
スナップショットバージョンの利用
@build_1050_p
@build_1052_p
# To build a <code>h2-*-SNAPSHOT.jar</code> file and upload it the to the local Maven 2 repository, execute the following command:
@build_1051_p
@build_1053_p
# Afterwards, you can include the database in your Maven 2 project as a dependency:
@build_1052_h2
@build_1054_h2
#Translating
@build_1053_p
@build_1055_p
# The translation of this software is split into the following parts:
# To translate the H2 Console, start it and select Preferences / Translate. After you are done, send the translated <code>*.prop</code> file to the Google Group. The web site is currently translated using Google.
@build_1057_h2
@build_1059_h2
#Providing Patches
@build_1058_p
@build_1060_p
# If you like to provide patches, please consider the following guidelines to simplify merging them:
@build_1059_li
@build_1061_li
#Only use Java 1.5 features (do not use Java 1.6) (see <a href="#environment">Environment</a>).
@build_1060_li
@build_1062_li
#Follow the coding style used in the project, and use Checkstyle (see above) to verify. For example, do not use tabs (use spaces instead). The checkstyle configuration is in <code>src/installer/checkstyle.xml</code>.
@build_1061_li
@build_1063_li
#A template of the Eclipse settings are in <code>src/installer/eclipse.settings/*</code>. If you want to use them, you need to copy them to the <code>.settings</code> directory. The formatting options (<code>eclipseCodeStyle</code>) are also included.
@build_1062_li
@build_1064_li
#Please provide test cases and integrate them into the test suite. For Java level tests, see <code>src/test/org/h2/test/TestAll.java</code>. For SQL level tests, see <code>src/test/org/h2/test/test.in.txt</code> or <code>testSimple.in.txt</code>.
@build_1063_li
@build_1065_li
#The test cases should cover at least 90% of the changed and new code; use a code coverage tool to verify that (see above). or use the build target <code>coverage</code>.
@build_1064_li
@build_1066_li
#Verify that you did not break other features: run the test cases by executing <code>build test</code>.
@build_1065_li
@build_1067_li
#Provide end user documentation if required (<code>src/docsrc/html/*</code>).
@build_1066_li
@build_1068_li
#Document grammar changes in <code>src/docsrc/help/help.csv</code>
@build_1067_li
@build_1069_li
#Provide a change log entry (<code>src/docsrc/html/changelog.html</code>).
@build_1068_li
@build_1070_li
#Verify the spelling using <code>build spellcheck</code>. If required add the new words to <code>src/tools/org/h2/build/doc/dictionary.txt</code>.
@build_1069_li
@build_1071_li
#Run <code>src/installer/buildRelease</code> to find and fix formatting errors.
@build_1070_li
@build_1072_li
#Verify the formatting using <code>build docs</code> and <code>build javadoc</code>.
@build_1071_li
@build_1073_li
#Submit patches as <code>.patch</code> files (compressed if big). To create a patch using Eclipse, use Team / Create Patch.
@build_1072_p
@build_1074_p
# For legal reasons, patches need to be public in the form of an email to the <a href="http://groups.google.com/group/h2-database">group</a>, or in the form of an <a href="http://code.google.com/p/h2database/issues/list">issue report or attachment</a>. Significant contributions need to include the following statement:
@build_1073_p
@build_1075_p
# "I wrote the code, it's mine, and I'm contributing it to H2 for distribution multiple-licensed under the H2 License, version 1.0, and under the Eclipse Public License, version 1.0 (http://h2database.com/html/license.html)."
@build_1074_h2
@build_1076_h2
#Reporting Problems or Requests
@build_1075_p
@build_1077_p
# Please consider the following checklist if you have a question, want to report a problem, or if you have a feature request:
@build_1076_li
@build_1078_li
#Feature requests are always welcome, even if the feature is already on the <a href="roadmap.html">roadmap</a>. Your mail will help prioritize feature requests. If you urgently need a feature, consider <a href="#providing_patches">providing a patch</a>.
@build_1077_li
@build_1079_li
#Before posting problems, check the <a href="faq.html">FAQ</a> and do a <a href="http://google.com">Google search</a>.
@build_1078_li
@build_1080_li
#When got an unexpected exception, please try the <a href="sourceError.html">Error Analyzer tool</a>. If this doesn't help, please report the problem, including the complete error message and stack trace, and the root cause stack trace(s).
@build_1079_li
@build_1081_li
#When sending source code, please use a public web clipboard such as <a href="http://pastebin.com">Pastebin</a>, <a href="http://cl1p.net">Cl1p</a>, or <a href="http://www.mysticpaste.com/new">Mystic Paste</a> to avoid formatting problems. Please keep test cases as simple and short as possible, but so that the problem can still be reproduced. As a template, use: <a href="http://h2database.googlecode.com/svn/trunk/h2/src/test/org/h2/samples/HelloWorld.java">HelloWorld.java</a>. Method that simply call other methods should be avoided, as well as unnecessary exception handling. Please use the JDBC API and no external tools or libraries. The test should include all required initialization code, and should be started with the main method.
@build_1080_li
@build_1082_li
#For large attachments, use a public temporary storage such as <a href="http://rapidshare.com">Rapidshare</a>.
@build_1081_li
@build_1083_li
#Google Group versus issue tracking: Use the <a href="http://groups.google.com/group/h2-database">Google Group</a> for questions or if you are not sure it's a bug. If you are sure it's a bug, you can create an <a href="http://code.google.com/p/h2database/issues/list">issue</a>, but you don't need to (sending an email to the group is enough). Please note that only few people monitor the issue tracking system.
@build_1082_li
@build_1084_li
#For out-of-memory problems, please analyze the problem yourself first, for example using the command line option <code>-XX:+HeapDumpOnOutOfMemoryError</code> and a memory analysis tool such as the <a href="http://www.eclipse.org/mat">Eclipse Memory Analyzer (MAT)</a>.
@build_1083_li
@build_1085_li
#It may take a few days to get an answers. Please do not double post.
@build_1084_h2
@build_1086_h2
#Automated Build
@build_1085_p
@build_1087_p
# This build process is automated and runs regularly. The build process includes running the tests and code coverage, using the command line <code>./build.sh clean jar coverage -Dh2.ftpPassword=... uploadBuild</code>. The last results are available here:
@build_1086_a
@build_1088_a
#Test Output
@build_1087_a
@build_1089_a
#Code Coverage Summary
@build_1088_a
@build_1090_a
#Code Coverage Details (download, 1.3 MB)
@build_1089_a
@build_1091_a
#Build Newsfeed
@build_1090_a
@build_1092_a
#Latest Jar File (download, 1 MB)
@build_1091_h2
@build_1093_h2
#Generating Railroad Diagrams
@build_1092_p
@build_1094_p
# The railroad diagrams are HTML, formatted as nested tables. The diagrams are generated as follows:
@build_1093_li
@build_1095_li
#The BNF parser (<code>org.h2.bnf.Bnf</code>) reads and parses the BNF from the file <code>help.csv</code>.
@build_1094_li
@build_1096_li
#The page parser (<code>org.h2.server.web.PageParser</code>) reads the template HTML file and fills in the diagrams.
@build_1095_li
@build_1097_li
#The rail images (one straight, four junctions, two turns) are generated using a simple Java application.
@build_1096_p
@build_1098_p
# To generate railroad diagrams for other grammars, see the package <code>org.h2.jcr</code>. This package is used to generate the SQL-2 railroad diagrams for the JCR 2.0 specification.
@changelog_1000_h1
...
...
@@ -1523,1359 +1529,1368 @@ Centralリポジトリの利用
#Next Version (unreleased)
@changelog_1002_li
#JMX (the Java management extension) is now supported. Issue 253.
#Improved date / time arithmetics. Now supported are multiplying and dividing a time with / by a number, adding and subtracting a time to / from a time or date, subtracting a time or timestamp from a timestamp.
@changelog_1003_li
#Creating a comment on a column didn't work if the schema name was equal the database name.
#The Ant build script has been removed because it is no longer up to date.
@changelog_1004_li
#When using multi-version concurrency, re-running a prepared statement with the same parameters would sometimes give the same result even if another connection committed a change (the previous result was sometimes re-used incorrectly).
#Nested outer joins without brackets were not working as expected. Example: select * from a inner join b inner join c on c.id = b.id on b.id = a.id;
@changelog_1005_li
#When using SELECT_FOR_UPDATE_MVCC (lock only the selected rows when using MVCC), the selected rows were sometimes not locked correctly.
#JMX (the Java management extension) is now supported. Issue 253.
@changelog_1006_li
#When using Lucene 3, the index files were not always closed when the database was closed.
#Creating a comment on a column didn't work if the schema name was equal the database name.
@changelog_1007_li
#Concurrently preparing a statement and altering a table could throw a table not found exception.
#When using multi-version concurrency, re-running a prepared statement with the same parameters would sometimes give the same result even if another connection committed a change (the previous result was sometimes re-used incorrectly).
@changelog_1008_li
#When concurrently preparing many statements with a subquery, in some cases the query didn't run (Column "..." must be in the GROUP BY list).
#When using SELECT_FOR_UPDATE_MVCC (lock only the selected rows when using MVCC), the selected rows were sometimes not locked correctly.
@changelog_1009_li
#CallableStatement: now the syntax "{? = CALL...}" is supported as well.
#When using Lucene 3, the index files were not always closed when the database was closed.
@changelog_1010_li
#Lob in databases: two small BLOB or CLOB values were always considered equal. This also affected unique indexes.
#Concurrently preparing a statement and altering a table could throw a table not found exception.
@changelog_1011_li
#The shutdown hook is (re-) enabled by default even for H2 version 1.3.x.
#When concurrently preparing many statements with a subquery, in some cases the query didn't run (Column "..." must be in the GROUP BY list).
@changelog_1012_li
#When creating a database from a recovery script, the same user can now be used (CREATE USER now always includes IF EXISTS).
#CallableStatement: now the syntax "{? = CALL...}" is supported as well.
@changelog_1013_li
#Lob in databases: two small BLOB or CLOB values were always considered equal. This also affected unique indexes.
@changelog_1014_li
#The shutdown hook is (re-) enabled by default even for H2 version 1.3.x.
@changelog_1015_li
#When creating a database from a recovery script, the same user can now be used (CREATE USER now always includes IF EXISTS).
@changelog_1016_li
#The H2 Console now prints a status message if started with parameters.
@changelog_1014_h2
@changelog_1017_h2
#Version 1.3.146 Beta (2010-11-08)
@changelog_1015_li
@changelog_1018_li
#This is a beta version. The next version will be 1.2.147. The differences between 1.2.x and 1.3.x are:
@changelog_1016_li
@changelog_1019_li
#In version 1.3.x, h2.lobInDatabase (store CLOB and BLOB in the database file) is enabled by default.
@changelog_1017_li
@changelog_1020_li
#In version 1.3.x, ANALYZE_AUTO is 2000 (automatic ANALYZE).
@changelog_1018_li
@changelog_1021_li
#In version 1.3.x, DB_CLOSE_ON_EXIT (the shutdown hook) is disabled by default.
@changelog_1019_li
@changelog_1022_li
#In version 1.3.x, DROP_RESTRICT (default action for DROP is RESTRICT) is enabled.
@changelog_1020_li
@changelog_1023_li
#In version 1.3.x, FUNCTIONS_IN_SCHEMA (allow to store functions in a schema) is enabled.
@changelog_1021_li
@changelog_1024_li
#In version 1.3.x, LARGE_TRANSACTIONS (support for very large transactions) is enabled. Changes to tables without a primary key can be buffered to disk.
@changelog_1022_li
@changelog_1025_li
#In version 1.3.x, MAX_MEMORY_ROWS_DISTINCT is set to a 10000.
@changelog_1023_li
@changelog_1026_li
#In version 1.3.x, NESTED_JOINS (nested joins and right outer joins) is enabled.
@changelog_1024_li
@changelog_1027_li
#In version 1.3.x, OPTIMIZE_INSERT_FROM_SELECT (speed up CREATE TABLE ... AS SELECT) is enabled.
@changelog_1025_li
@changelog_1028_li
#In version 1.3.x, OPTIMIZE_OR (convert OR conditions to IN(..) if possible) is enabled.
@changelog_1026_li
@changelog_1029_li
#In version 1.3.x, QUERY_CACHE_SIZE is enabled.
@changelog_1027_li
@changelog_1030_li
#In version 1.3.x, SELECT_FOR_UPDATE_MVCC (MVCC and SELECT FOR UPDATE) is enabled.
@changelog_1028_li
@changelog_1031_li
#In version 1.3.x, RUNSCRIPT and SCRIPT (commands and tools), use UTF-8 by default (ScriptCommand.charset).
@changelog_1029_li
@changelog_1032_li
#In version 1.3.x, Lucene 3 is used by default. Issue 147.
@changelog_1030_li
@changelog_1033_li
#When the system property h2.lobInDatabase is set, the lob tables were always created when closing the database, even if the tables were not needed.
@changelog_1031_li
@changelog_1034_li
#In the MySQL mode, SHOW TABLES didn't work, and meta data tables were not case insensitive. Updatable result sets didn't work as expected. Issue 249.
@changelog_1032_li
@changelog_1035_li
#Connection-created Clob and Blob objects can now be filled using Clob.setCharacterStream(1), Clob.setString(1, s), Blob.setBytes(1, x), Blob.setBinaryStream(1). Issue 235.
@changelog_1033_li
@changelog_1036_li
#Trying to convert a very small CLOB to a BLOB or a very small CLOB to a BLOB threw a NullPointerException.
@changelog_1034_li
@changelog_1037_li
#INFORMATION_SCHEMA.SETTINGS: now the current page count can be queried using select * from information_schema.settings where name = 'info.PAGE_COUNT'.
@changelog_1035_li
@changelog_1038_li
#For an invalid value exception, the parameter name and value was switched in some cases.
@changelog_1036_li
@changelog_1039_li
#When using trace level 3, opening a database no longer prints there is a EOFException (because that is the expected behavior).
@changelog_1037_li
@changelog_1040_li
#CALL calling a Java function with return type ResultSet and return value null threw a ClassCastException.
@changelog_1038_li
@changelog_1041_li
#SELECT ... FROM CSVREAD no longer creates a temporary file. Some large imports are now twice as fast.
@changelog_1039_h2
@changelog_1042_h2
#Version 1.2.145 (2010-11-02)
@changelog_1040_li
@changelog_1043_li
#A new String cache is now created at most once every 5 second, so that out of memory exceptions are not artificially delayed.
@changelog_1041_li
@changelog_1044_li
#After closing a database, the writer thread will stop after 100 ms at the latest (instead of 1 second).
@changelog_1042_li
@changelog_1045_li
#Opening a large database could fail in theory if the process was killed and then not fully compacted (because the unique transaction log key was re-used).
@changelog_1043_li
@changelog_1046_li
#Views now store the schema for Java functions if "functions in schemas" is enabled (system property h2.functionsInSchema).
@changelog_1044_li
@changelog_1047_li
#Improved error message if the LOB files are already deleted on the client side.
@changelog_1045_li
@changelog_1048_li
#Closing a Statement or PreparedStatement at the same time as executing a statement could throw a strange exception. Issue 241.
@changelog_1046_li
@changelog_1049_li
#The Recover tool did not work with compressed lob files (set compress_lob lzf). Also, sometimes the Recover tool was very slow, specially using a 64-bit JVM, because it tried to de-compress lob files even if they were not compressed (which could allocate a lot of memory).
@changelog_1047_li
@changelog_1050_li
#H2 Console: webAllowOthers and webSSL were swapped if they didn't exist in the properties file. Issue 244.
@changelog_1048_li
@changelog_1051_li
#When the system property h2.lobInDatabase is set, CREATE TABLE ... AS SELECT with a LOB column did not always work.
@changelog_1049_li
@changelog_1052_li
#Some system properties are not supported any longer, because they can already be set in the database URL. The constants are: CACHE_SIZE_DEFAULT, CACHE_TYPE_DEFAULT, DEFAULT_LOCK_MODE, LOCK_MODE_READ_COMMITTED, DEFAULT_MAX_LENGTH_INPLACE_LOB, DEFAULT_MAX_LENGTH_INPLACE_LOB2, DEFAULT_MAX_MEMORY_UNDO, DEFAULT_MAX_OPERATION_MEMORY, DEFAULT_PAGE_SIZE, DEFAULT_RESULT_SET_CONCURRENCY, MIN_WRITE_DELAY.
@changelog_1050_li
@changelog_1053_li
#Various system properties have been replaced with database level settings: ALIAS_COLUMN_NAME, ANALYZE_AUTO, ANALYZE_SAMPLE, DATABASE_TO_UPPER, DEFAULT_ESCAPE, DEFRAG_ALWAYS, DROP_RESTRICT, ESTIMATED_FUNCTION_TABLE_ROWS, FUNCTIONS_IN_SCHEMA, LARGE_RESULT_BUFFER_SIZE, LARGE_TRANSACTIONS, MAX_COMPACT_COUNT, MAX_COMPACT_TIME, MAX_MEMORY_ROWS_DISTINCT, MAX_QUERY_TIMEOUT, NESTED_JOINS, OPTIMIZE_DISTINCT, OPTIMIZE_EVALUATABLE_SUBQUERIES, OPTIMIZE_INSERT_FROM_SELECT, OPTIMIZE_IN_LIST, OPTIMIZE_IS_NULL, OPTIMIZE_OR, OPTIMIZE_SUBQUERY_CACHE, OPTIMIZE_TWO_EQUALS, OPTIMIZE_UPDATE, PAGE_STORE_INTERNAL_COUNT, PAGE_STORE_TRIM, QUERY_CACHE_SIZE, RECOMPILE_ALWAYS, RECONNECT_CHECK_DELAY, SELECT_FOR_UPDATE_MVCC, SHARE_LINKED_CONNECTIONS. See the Javadoc documentation of DbSettings for details. The system properties are still supported for backward compatibility.
@changelog_1051_li
@changelog_1054_li
#When the system property h2.nestedJoins was enabled, some outer joins returned the wrong result.
@changelog_1052_li
@changelog_1055_li
#Opening a database could throw a NullPointerException.
@changelog_1053_li
@changelog_1056_li
#After a crash, the database file did not always shrink because old transaction log pages were not removed from the file.
@changelog_1054_li
@changelog_1057_li
#Various CallableStatement methods could throw a NullPointerException.
@changelog_1055_li
@changelog_1058_li
#LOB files were not deleted when running DROP ALL OBJECTS.
@changelog_1056_li
@changelog_1059_li
#MS SQL Server compatibility: support "N" in front of string literals ("National Language" strings). Issue 240.
@changelog_1057_li
@changelog_1060_li
#CAST: when converting a string to binary, it is hex encoded (every byte two characters); a hex string can be converted to a number by first converting it to binary. Examples: CAST(CAST('FFFF' AS BINARY) AS INT) = 65535, CAST(65535 AS BINARY) = '0000FFFF'.
@changelog_1058_li
@changelog_1061_li
#When a domain (user defined data type) contained a user defined function, the database could not be opened.
@changelog_1059_li
@changelog_1062_li
#CAST('011' AS INT) will no longer use decode the value as an octal number (using Integer.decode) but now use Integer.parseInt. The same logic applied to byte, short, and long. This also means that trying to convert hex numbers (0x...) with CAST now fails.
@changelog_1060_li
@changelog_1063_li
#A table in the Recover tool script could not be imported if the script contained duplicate keys.
@changelog_1061_h2
@changelog_1064_h2
#Version 1.2.144 (2010-10-15)
@changelog_1062_li
@changelog_1065_li
#The Windows .bat files did not contain CR+LF.
@changelog_1063_li
@changelog_1066_li
#The LOB storage (when the system property h2.lobInDatabase is set) is now only initialized when needed.
@changelog_1064_li
@changelog_1067_li
#The index condition columnName IS NULL was not efficient when using a clustered index.
@changelog_1065_li
@changelog_1068_li
#The Recover tool did not work for databases larger than 2 GB.
@changelog_1066_li
@changelog_1069_li
#In memory database: outer joins with a condition "column is null" could return the wrong result.
@changelog_1067_li
@changelog_1070_li
#Temporary files were not created in the temporary directory of the system, but in the current working directory. This affected temporary undo log files for read-only databases, temporary files for large result sets when using read-only databases, and temporary LOB files when storing LOBs in the database (system property h2.lobInDatabase). When the setting h2.lobInDatabase is not set, temporary LOB files are still stored in a sub-directory (.lobs.db/) of the current working directory.
@changelog_1068_li
@changelog_1071_li
#New experimental feature to speed up CREATE TABLE ... AS SELECT. To enable the feature, set the system property h2.optimizeInsertFromSelect to true. For large queries, performance can be doubled.
@changelog_1069_li
@changelog_1072_li
#When LOB objects are stored in the database (using the experimental setting h2.lobInDatabase), and using the MVCC mode, opening a database with uncommitted transactions could throw a NullPointerException.
@changelog_1070_li
@changelog_1073_li
#Support of stored procedures with OUT parameters in CallableStatement is implemented.
@changelog_1071_li
@changelog_1074_li
#PreparedStatement.getMetaData() was not always consistent with resulting ResultSet.getMetaData().
@changelog_1072_li
@changelog_1075_li
#The build tool now uses JAVA_HOME for javac as well. Issue 233.
@changelog_1073_li
@changelog_1076_li
#Opening and closing encrypted databases is now much faster.
@changelog_1074_li
@changelog_1077_li
#H2 Console: new experimental feature to support file download and upload, but only if there is a directory called "transfer" in the current working directory. For security reasons, only very simple file names are supported. Sub-directories are not supported. To upload, use transfer.jsp; to download, use transfer/fileName.
@changelog_1075_li
@changelog_1078_li
#A new sample application that shows how to manually create an encrypted and compressed script file.
@changelog_1076_li
@changelog_1079_li
#Performance has been improved a bit.
@changelog_1077_li
@changelog_1080_li
#DatabaseMetaData.getJDBCMajorVersion now returns 4 (instead of 3) when the driver is compiled with Java 6 (the default).
@changelog_1078_li
@changelog_1081_li
#Re-added the internal utility class BitField which improves performance of opening and closing a database (because it supports setByte / getByte, unlike java.util.BitSet).
@changelog_1079_li
@changelog_1082_li
#INFORMATION_SCHEMA.SESSIONS: the start time of a SQL statement is no longer set in each case. It is only set for long running statements. This change should improve performance a bit on some devices, specially when using Android.
@changelog_1080_li
@changelog_1083_li
#A old databases without user name and password (created with H2 version 1.2.142 or older) couldn't be opened with version 1.2.143. Fixed.
@changelog_1081_li
@changelog_1084_li
#The database upgrade classes have been renamed.
@changelog_1082_li
@changelog_1085_li
#The database did not automatically upgrade when using a connection pool or data source.
@changelog_1083_li
@changelog_1086_li
#JaQu: a database object can now also be created using a DataSource. Issue 227.
@changelog_1084_li
@changelog_1087_li
#The built-in profiler now better supports the Dalvik VM.
@changelog_1085_li
@changelog_1088_li
#The jarSmall build target no longer includes assertions (SysProperties.CHECK, CHECK2, system properties h2.check and h2.check2).
@changelog_1086_li
@changelog_1089_li
#The jarSmall build target excluded the DbUpgrade classes by mistake.
@changelog_1087_h2
@changelog_1090_h2
#Version 1.2.143 (2010-09-18)
@changelog_1088_li
@changelog_1091_li
#If the user name and password are not set or empty, then the password is not hashed. To disable this behavior, set the system property h2.emptyPassword to false. TCP server: the default user name for the management database is now an empty string.
@changelog_1089_li
@changelog_1092_li
#Cluster: auto-commit was disabled after opening a connection.
@changelog_1090_li
@changelog_1093_li
#Connection.getAutoCommit() is now much faster, specially when using the server mode.
@changelog_1091_li
@changelog_1094_li
#Statement.cancel() had no effect when using the server mode.
@changelog_1092_li
@changelog_1095_li
#SCRIPT: the SQL script no longer contains settings that match the default value.
@changelog_1093_li
@changelog_1096_li
#Statement.cancel() did not work when running RUNSCRIPT and SCRIPT.
@changelog_1094_li
@changelog_1097_li
#Statement.cancel() could cause a NullPointerException.
@changelog_1095_li
@changelog_1098_li
#In some cases (specially when using a small cache size or a large database over 1 GB) for some operations like ALTER TABLE the data was written before the transaction log entries, which could cause a corrupt database if the process was killed during the ALTER TABLE operation. Thanks a lot to Victor Pyankov for helping solve this problem!
@changelog_1096_li
@changelog_1099_li
#The Recover tool could throw a ArrayIndexOutOfBoundsException when trying to recover a corrupt database file.
@changelog_1097_li
@changelog_1100_li
#The SCRIPT command and tool now uses the default file encoding for the system now instead of UTF-8 (as before). In most cases, this will not affect existing applications, as the encoding only affects how SQL identifiers (table names and so on) that contain special characters are stored. Table data is escaped, and therefore is no problem.
@changelog_1098_li
@changelog_1101_li
#The SCRIPT command and tool now also support the CHARSET option (like RUNSCRIPT).
@changelog_1099_li
@changelog_1102_li
#When closing a database, sometimes empty space in the database was not freed up.
@changelog_1100_li
@changelog_1103_li
#Trying to create a view with parameters in the query will now throw an exception. So far, creating the view was allowed, but the parameter value was not used (null was used instead).
@changelog_1101_li
@changelog_1104_li
#New experimental feature SHUTDOWN DEFRAG. This option re-orders the pages while closing the database so that table scans are faster.
@changelog_1102_li
@changelog_1105_li
#When using the MULTI_THREADED option, concurrently reading from a database (specially from a larger database, or when using a small cache size) could throw an exception.
@changelog_1103_li
@changelog_1106_li
#When adding a comment to a column that has a check constraint, the database couldn't be re-opened.
@changelog_1104_li
@changelog_1107_li
#New system property h2.lobClientMaxSizeMemory to set the maximum size of a LOB object to keep in memory on the client side when using the server mode.
@changelog_1105_h2
@changelog_1108_h2
#Version 1.2.142 (2010-08-31)
@changelog_1106_li
@changelog_1109_li
#Documentation for using H2 on Android devices has been added under Tutorial - Android.
@changelog_1107_li
@changelog_1110_li
#An ArrayIndexOutOfBoundsException was thrown when querying the table information_schema.function_aliases while there are any user defined aggregate functions.
@changelog_1108_li
@changelog_1111_li
#The jar files are now about 50 KB smaller. In the last few versions they contained superfluous classes.
@changelog_1109_li
@changelog_1112_li
#The default time to compact a database when closing (system property h2.maxCompactTime) is now 0.2 seconds instead of 1 second.
@changelog_1110_li
@changelog_1113_li
#Opening an closing a database is now faster.
@changelog_1111_li
@changelog_1114_li
#In theory, when using indexes with large index rows (or when using a very small page size), removing rows could throw an internal exception in some cases.
@changelog_1112_li
@changelog_1115_li
#Inserting rows in reverse order could throw an ArrayIndexOutOfBoundsException in some cases (specially rows larger than the page size, which is 2 KB by default). Issue 226.
@changelog_1113_li
@changelog_1116_li
#H2 Console: with Chrome and Safari, resizing the table/query frame doesn't work. Issue 225.
@changelog_1114_li
@changelog_1117_li
#New experimental database file locking mechanism "FS" to use native file locking (no *.lock.db file is created in this case, and no background thread is started). This mechanism may not work on all systems (on some systems it's possible to lock the same file multiple times within the same virtual machine, and on some system native file locking is not working or unlocking is not working).
@changelog_1115_h2
@changelog_1118_h2
#Version 1.2.141 (2010-08-22)
@changelog_1116_li
@changelog_1119_li
#New experimental pseudo-encryption algorithm "FOG". It makes the data appear to be encrypted. This algorithm is cryptographically extremely weak, and should only be used to hide data from reading the plain text using a text editor. Please let us know if you think this is useful or not.
@changelog_1117_li
@changelog_1120_li
#Documentation: the grammar and function documentation can now be easier translated.
@changelog_1118_li
@changelog_1121_li
#Password hash: in addition to connecting with the plain text password, H2 now supports connecting with the password hash. Like this you don't have to store plain text passwords in config files. For details, see the documentation at Advanced / Password Hash.
@changelog_1119_li
@changelog_1122_li
#Lucene 3.x support was added in the source code, however it is not yet enabled by default and is not yet supported when using the default h2 jar file. To enable Lucene 3.x support, the source code of H2 needs to be switched using <code>./build.sh -Dlucene=3 switchSource</code>, and then re-compile. To switch the source code back use <code>./build.sh -Dlucene=2 switchSource</code> (replace ./build.sh with build.bat on Windows). The plan is to use Lucene 3 by default in H2 version 1.3.x. Issue 147.
@changelog_1120_li
@changelog_1123_li
#The native fulltext search could cause a Java level deadlock if searching from multiple connections concurrently.
@changelog_1121_li
@changelog_1124_li
#CREATE FORCE VIEW didn't work in most cases if a referenced table didn't exist.
@changelog_1122_li
@changelog_1125_li
#MVCC: when trying to insert two rows with the same key from two connections, the second connection immediately threw the exception "Unique index or primary key violation". Instead, the second connection now waits throwing the exception until the first connection committed the change (same as when trying to concurrently update the same row).
@changelog_1123_li
@changelog_1126_li
#Server mode: if the client ran with a different timezone setting than the server, date values got shifted by the difference between the timezones. This problem affected the data types DATE, TIME, and TIMESTAMP, when using PreparedStatement.setDate / setTime / setTimestamp and ResultSet.getDate / getTime / getTimestamp. To solve the problem, both the client and the server need to be updated (otherwise the old transfer protocol is used).
@changelog_1124_li
@changelog_1127_li
#The built-in connection pool (JdbcConnectionPool) did not always honor the login timeout (the timeout could occur much too early). Thanks a lot to Dario Fassi for the patch!
@changelog_1125_li
@changelog_1128_li
#Translation: the new messages have been translated to Spanish. Thanks a lot to Dario Fassi!
@changelog_1126_li
@changelog_1129_li
#The table INFORMATION_SCHEMA.SETTINGS now contains all H2-specific system properties (the ones that start with "h2.") and that are explicitly set. Previously, some H2-specific settings (for example h2.analyzeAuto) were missing in this list.
@changelog_1127_li
@changelog_1130_li
#EXPLAIN ANALYZE with an in-memory database threw an exception. Issue 216.
@changelog_1128_li
@changelog_1131_li
#Data modifications (inserts, updates, and deletes) are now up to 5 times faster because converting objects to byte arrays is avoided if possible.
@changelog_1129_li
@changelog_1132_li
#LOG=0 is now a bit faster (previously undo log entries were still written).
@changelog_1130_li
@changelog_1133_li
#The command line tools now say so if the source directory of an option doesn't exist.
@changelog_1131_li
@changelog_1134_li
#It is now allowed to truncate a table if referential integrity has been disabled for this table or database.
@changelog_1132_li
@changelog_1135_li
#For unencrypted databases, the automatic upgrade temporary script file is now unencrypted again.
@changelog_1133_h2
@changelog_1136_h2
#Version 1.2.140 (2010-07-25)
@changelog_1134_li
@changelog_1137_li
#The default MAX_LOG_SIZE is now 16 MB instead of 2 MB. Some uses cases are 3 times faster now.
@changelog_1135_li
@changelog_1138_li
#Improved cache memory usage calculation.
@changelog_1136_li
@changelog_1139_li
#Only resources that are actually used are loaded in memory. This can reduce the memory usage by about 400 KB.
@changelog_1137_li
@changelog_1140_li
#Profiling: the jar file can now be installed as an agent using java -javaagent:h2*.jar - this was be used to more accurately calculate the memory footprint of the cache. It has no effect when using H2 (using this feature in an application is not needed and not recommended).
@changelog_1138_li
@changelog_1141_li
#The cache was not used efficiently when reading (behaving like a FIFO cache instead of an LRU cache).
@changelog_1139_li
@changelog_1142_li
#Storing lobs in the database has been changed. It is now faster. Unfortunately, the change is not backward compatible; if you have used h2.lobInDatabase before you will need to re-build the database.
@changelog_1140_li
@changelog_1143_li
#SHUTDOWN COMPACT is now faster.
@changelog_1141_li
@changelog_1144_li
#H2 Console: requesting the status did not always show the window on top of others.
@changelog_1142_li
@changelog_1145_li
#H2 Console: on some system, the browser windows got opened when requesting a new one.
@changelog_1143_li
@changelog_1146_li
#The built-in profiling tool now uses a default stack depth of 32 elements and a default interval of 10 ms.
@changelog_1144_li
@changelog_1147_li
#Database files now grows in 1 MB blocks (and at least 20% at a time), instead of always 256 KB. This speeds up loading a new database.
@changelog_1145_li
@changelog_1148_li
#H2 Console: new built-in command @sleep to help profile another session.
@changelog_1146_li
@changelog_1149_li
#For improved performance, LOG=0 and LOG=1 are again supported. LOG=0 means the transaction log is disabled completely (fastest; for loading a database). LOG=1 means the transaction log is enabled, but FileDescriptor.sync is disabled (if no protection against power failure is required). LOG=2 is the default (transaction log is enabled, FileDescriptor.sync for each checkpoint).
@changelog_1147_li
@changelog_1150_li
#After deleting a lot of data (for example by dropping or altering tables, or indexes, or after a large transaction), opening a large database was very slow. Fixed.
@changelog_1148_li
@changelog_1151_li
#When killing the process after creating and dropping many tables (specially temporary tables), the database could not be opened sometimes.
@changelog_1149_li
@changelog_1152_li
#CAST(NULL AS ...) doesn't forget the data type, precision, and scale any longer.
@changelog_1150_li
@changelog_1153_li
#Experimental support for recursive queries (see 'Advanced' - 'Recursive Queries' for details).
@changelog_1151_li
@changelog_1154_li
#Problems with JDK 1.6.0_18 have been reports in the class StringUtils.quoteRemarkSQL. This method is now changed.
@changelog_1152_li
@changelog_1155_li
#The "small jar" distribution did not include the CompressTool, which was required for some operations. Fixed.
@changelog_1153_li
@changelog_1156_li
#The build tool now supports (minimalistic) shell mode, started using ./build.sh -
@changelog_1154_li
@changelog_1157_li
#IS NULL comparison with nested queries and linked tables did not work. Example: select * from (select x from test) where x is null.
@changelog_1155_li
@changelog_1158_li
#Support for null-safe equals. This includes the ANSI SQL standard syntax A IS [NOT] DISTINCT FROM B as well as the shorter A IS [NOT] B.
@changelog_1156_li
@changelog_1159_li
#Primary key violations threw a strange exception message when using a single column INT or BIGINT key.
@changelog_1157_li
@changelog_1160_li
#EXPLAIN ANALYZE now also lists the number of pages read from the file.
@changelog_1158_li
@changelog_1161_li
#Memory mapped files: There was a bug in version 1.2.139 so that memory mapped files could only be used together with split, for example: split:nioMapped: - the problem is now solved. It is still a good idea to use split:nioMapped: to work around the 2 GB limitation of memory mapped files.
@changelog_1159_li
@changelog_1162_li
#Memory mapped files: the system property h2.nioCleanerHack is now disabled by default because it was not always working as expected. Now System.gc() is used in a loop until the buffer is garbage collected. This of course is also not a nice solution, but the only one known to work. See also http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4724038
@changelog_1160_li
@changelog_1163_li
#Bugfixes for the automatic 1.1 db migration.
@changelog_1161_li
@changelog_1164_li
#If an old 1.1 database file version is found on connect, it is now possible to let the old h2 classes (v 1.2.128) connect to the database. The automatic upgrade .jar file must be present, and the url must contain NO_UPGRADE=TRUE
@changelog_1162_li
@changelog_1165_li
#The automatic upgrade temporary script file is now encrypted.
@changelog_1163_h2
@changelog_1166_h2
#Version 1.2.139 (2010-07-10)
@changelog_1164_li
@changelog_1167_li
#There was a bug in the internal IntIntHashMap. There were no known side effects however.
@changelog_1165_li
@changelog_1168_li
#ANALYZE now uses less memory.
@changelog_1166_li
@changelog_1169_li
#Memory mapped file system: improved error messages if there is a problem.
@changelog_1167_li
@changelog_1170_li
#The Lucene fulltext search did not work well when using special file systems such as split or nioMapped.
@changelog_1168_li
@changelog_1171_li
#The memory mapped file system (nioMapped: file prefix) couldn't seek past the file length.
@changelog_1169_li
@changelog_1172_li
#Some file system operations did not work with stacked file systems (for example split and nioMapped). This also affected the DeleteDbFiles tool.
@changelog_1170_li
@changelog_1173_li
#New experimental query cache. The cache is only used if the SQL statement and all parameters match. Each session has it's own cache with the given size. Only the last returned result per query is cached. Only SELECT statements are cached (excluding UNION and FOR UPDATE statements). This works for both statements and prepared statement. To enable, set the system property h2.commandCacheSize to a value larger than 0. There is currently no plan to enable this option by default in future versions.
@changelog_1171_li
@changelog_1174_li
#Conditions with many OR operations could throw an UnsupportedOperationException if h2.optimizeOr was enabled.
@changelog_1172_li
@changelog_1175_li
#XA connection: after transaction commit or rollback, the physical connection is set into autocommit mode.
@changelog_1173_li
@changelog_1176_li
#MULTI_THREADED did not work correctly and could throw the exception "try to add a record twice" for larger databases because cache access was not correctly synchronized.
@changelog_1174_li
@changelog_1177_li
#Automatic database upgrade from non page store is now possible. If the classes from the h2mig_pagestore_addon.jar file are in the classpath, the database will be converted to the current page store format automatically. The file can be found here: <a href="http://h2database.com/h2mig_pagestore_addon.jar">http://h2database.com/h2mig_pagestore_addon.jar</a>
@changelog_1175_li
@changelog_1178_li
#The MultiDimension tools was extended with a few helper methods. The API was unified a bit.
@changelog_1176_li
@changelog_1179_li
#ODBC: MS Access could not link to a table with unique index or primary key. To solve this problem, index meta data is currently disabled for ODBC. When using the new H2 version to access a database over ODBC, the PostgreSQL catalog is automatically upgraded. Using a database with an upgraded PostgreSQL catalog with an older version of H2 is still possible, but not over ODBC.
@changelog_1177_li
@changelog_1180_li
#ODBC: MS Access could not link to a table with a name containing '_'.
@changelog_1178_li
@changelog_1181_li
#ODBC: additional connection settings can now be added to the database name. Example: ~/test;cipher=xtea. Therefore, encrypted databases are supported.
@changelog_1179_li
@changelog_1182_li
#Local temporary tables can now be created without having to commit a transaction using CREATE LOCAL TEMPORARY TABLE TEMP(ID INT PRIMARY KEY) TRANSACTIONAL.
@changelog_1180_li
@changelog_1183_li
#New system property h2.dropRestrict (default false) to change the default action for DROP TABLE and DROP VIEW (false for CASCADE, true for RESTRICT). The plan is to enable this property by default in version 1.3.x.
@changelog_1181_li
@changelog_1184_li
#DROP TABLE now also supports CASCADE (still the default) and RESTRICT.
@changelog_1182_li
@changelog_1185_li
#The wrong exception was thrown when trying to connect to a server if the server was not running.
@changelog_1183_li
@changelog_1186_li
#UNION queries where the first query contains a nested query were parsed incorrectly. Example: "select 1 from (select 2 from dual) union select 3 from dual" was parsed as "select 1 from ((select 2 from dual) union select 3 from dual)". Fixed.
@changelog_1184_li
@changelog_1187_li
#Support ALTER SCHEMA name RENAME TO newName (rename schema). (patch from Kerry Sainsbury)
@changelog_1185_h2
@changelog_1188_h2
#Version 1.2.138 (2010-06-27)
@changelog_1186_li
@changelog_1189_li
#Referential integrity: it was not allowed to delete a row with NULL in the parent table, if there was a row with NULL in the child table.
@changelog_1187_li
@changelog_1190_li
#Experimental feature to support case sensitive catalog names and database names using the DATABASE() method. To use this feature, set the system property h2.databaseToUpper to false. The plan is to set the property to false by default in version 1.3.x. Issue 204 - thanks to Sylvain Cuaz (ILM Informatique) for the patch.
@changelog_1188_li
@changelog_1191_li
#Experimental feature to support nested joins. To enable, set the system property h2.nestedJoins to true. If enabled, nested joins and right outer joins should work as expected (issues 145, 177, and 203). The plan is to enable this feature by default in version 1.3.x.
#When creating functions within a schema, those functions could not be used in views, nested queries, and constraints. Fixed.
@changelog_1191_li
@changelog_1194_li
#The benchmarks have been run using recent database versions.
@changelog_1192_li
@changelog_1195_li
#Version 1.2.137 could still not be converted to Java 1.4 (because the Retrotranslator doesn't support BigDecimal.precision).
@changelog_1193_li
@changelog_1196_li
#Cluster: non-admin users could not connect when one of the cluster node was stopped. Issue 206.
@changelog_1194_li
@changelog_1197_li
#DROP VIEW now supports the CASCADE and RESTRICT clauses (patch from Kerry Sainsbury)
@changelog_1195_li
@changelog_1198_li
#CREATE VIEW now supports the OR REPLACE clause (patch from Kerry Sainsbury)
@changelog_1196_li
@changelog_1199_li
#Build tool: ability to only run one test using the -Dtest=className setting. eg: build -Dtest=org.h2.test.db.TestViewDropView test (patch from Kerry Sainsbury).
@changelog_1197_h2
@changelog_1200_h2
#Version 1.2.137 (2010-06-06)
@changelog_1198_li
@changelog_1201_li
#Statements with a nested query and a condition that was always NULL threw an IndexOutOfBoundsException. Example: select * from (select null as x) where x=1
@changelog_1199_li
@changelog_1202_li
#The changes that were made to support large transactions also fixed a bug with large transactions (when the undo log file size is larger than 2 GB).
@changelog_1200_li
@changelog_1203_li
#Experimental feature to support very large transactions (except when using MVCC). To enable, set the system property h2.largeTransactions to true. If enabled, changes to tables without a primary key can be buffered to disk. The plan is to enable this feature by default in version 1.3.x.
@changelog_1201_li
@changelog_1204_li
#H2 Console: editing result sets is now also working for database other than H2, if they do support updatable result sets. Add "@edit" before the query. Only limited testing has been done on this feature, some data types may not work (please provide feedback if you find issues).
@changelog_1202_li
@changelog_1205_li
#Cluster: an open transaction was committed when a cluster node was stopped (because disabling the cluster executes SET CLUSTER '', which committed the transaction). Transaction are no longer committed when calling SET CLUSTER. Issue 199.
@changelog_1203_li
@changelog_1206_li
#Cluster: non-admin users couldn't connect to the cluster and couldn't disable the cluster. Issue 201.
@changelog_1204_li
@changelog_1207_li
#Cluster: NEXTVAL('sequence') was only called on one cluster node, therefore sequence values could get out of sync.
@changelog_1205_li
@changelog_1208_li
#Version 1.2.136 could not be converted to Java 1.4 (because the Retrotranslator doesn't support BigDecimal.precision). A workaround has been implemented.
@changelog_1206_li
@changelog_1209_li
#The error code of IO exceptions in CSV functions was incorrect.
@changelog_1207_li
@changelog_1210_li
#The TriggerPassData example now uses a prefix (the database name).
@changelog_1208_li
@changelog_1211_li
#The wrong exception was thrown when trying to reference a table that doesn't support references such as a table in the information schema.
@changelog_1209_li
@changelog_1212_li
#Server.shutdownTcpServer can now stop all TCP servers on this JVM.
@changelog_1210_li
@changelog_1213_li
#JdbcConnectionPool: the default connection timeout is now 30 seconds (it used to be 5 minutes).
@changelog_1211_li
@changelog_1214_li
#LOB storage: LOBs added with "h2.lobInDatabase" enabled couldn't be read later with this option disabled.
@changelog_1212_h2
@changelog_1215_h2
#Version 1.2.136 (2010-05-24)
@changelog_1213_li
@changelog_1216_li
#When using ORDER BY and there are both ascending and descending indexes, the database used the first index even when the second one could be used for sorting.
@changelog_1214_li
@changelog_1217_li
#Conditions of the form columnName IS NULL now use an index. To disable this feature, set the system property h2.optimizeIsNull to false.
@changelog_1215_li
@changelog_1218_li
#H2 Console: when the settings were not stored yet (for example when running for the first time), the last recently used settings were not stored. A workaround was to create the file ".h2.server.properties" manually in the current user home directory, with the contents: webAllowOthers=false, webPort=8082, webSSL=false, 0=Generic H2 (Embedded)|org.h2.Driver|jdbc\:h2\:~/test|sa (where a comma is a newline).
@changelog_1216_li
@changelog_1219_li
#The source code is now switched to Java 6 (JDK 1.6) by default. Java 5 (JDK 1.5) is still supported, and the jar file is still compiled for Java 5.
@changelog_1217_li
@changelog_1220_li
#The BOM (the byte-order-mark) character 0xfeff at the beginning of the file is ignored. This is for compatibility with Microsoft Excel.
@changelog_1218_li
@changelog_1221_li
#When opening an existing database, the cache size is set to at most half the amount of memory available for the virtual machine (Runtime.getRuntime().maxMemory()), even if the cache size setting stored in the database is larger. Setting the cache size in the database URL or explicitly using SET CACHE_SIZE overrides this value (even if larger than the physical memory).
@changelog_1219_li
@changelog_1222_li
#INFORMATION_SCHEMA.SETTINGS: the cache size is now returned in KB.
@changelog_1220_li
@changelog_1223_li
#New system property h2.selectForUpdateMvcc, the default is false (the feature is disabled). When enabled, SELECT ... FOR UPDATE only locks the selected rows in the MVCC mode. Aggregate or GROUP BY queries are not allowed in this case.
@changelog_1221_li
@changelog_1224_li
#Profiler: improved message if there was no stack trace.
@changelog_1222_li
@changelog_1225_li
#The H2 Console can now be used within another application, in a frame or iframe. Issue 197.
@changelog_1223_li
@changelog_1226_li
#Recover tool: the statistics section now includes page type counts again.
@changelog_1224_li
@changelog_1227_li
#Queries with multiple IN(...) conditions sometimes return the wrong results when there was a multi-column index for the column.
@changelog_1225_li
@changelog_1228_li
#Queries with IN(..., NULL) did sometimes return the wrong results when there was a index for the column.
@changelog_1226_li
@changelog_1229_li
#DECIMAL: faster precision and memory usage calculations.
@changelog_1227_li
@changelog_1230_li
#A new class org.h2.tools.TriggerAdapter allows to use the ResultSet interface within trigger implementations.
@changelog_1228_li
@changelog_1231_li
#A subselect which used an index could lead to wrong results. Fixed.
@changelog_1229_li
@changelog_1232_li
#Creating a cached temporary non persistent table with a primary key threw a NullPointerException.
@changelog_1230_h2
@changelog_1233_h2
#Version 1.2.135 (2010-05-08)
@changelog_1231_li
@changelog_1234_li
#Temporary files were not deleted when using large transactions, disabling autocommit, and closing the session without committing.
@changelog_1232_li
@changelog_1235_li
#Queries using multiple IN(..) conditions on the same table could cause repeated rows in the result set.
@changelog_1233_li
@changelog_1236_li
#Translation: Lubomir Grajciar translated the H2 Console as well as all error message to Slovensky. Thanks a lot!
@changelog_1234_li
@changelog_1237_li
#There was a possible Java level deadlock when opening an uninitialized database and using a file system that also opened a database.
@changelog_1235_li
@changelog_1238_li
#When killing the process while the database was writing a checkpoint, while it was closing, or while running recovery (while removing temporary tables from a previous run), the database could become corrupt. A new test case has been implemented to ensure such problems can not occur in the future.
@changelog_1236_li
@changelog_1239_li
#File system: new method FileSystem.setReadOnly.
@changelog_1237_li
@changelog_1240_li
#The page size for new databases can now be set in the database URL using ;PAGE_SIZE=512. Currently this feature is only used to simplify testing.
@changelog_1238_li
@changelog_1241_li
#New system property h2.functionsInSchema (default is false). If enabled, the SCRIPT statement always includes the schema name in the CREATE ALIAS statement (even if the schema is PUBLIC). This is not backward compatible with H2 versions 1.2.134 and older.
@changelog_1239_li
@changelog_1242_li
#Functions: it is no longer required to add a space after a comma in the parameter list. Example: CREATE ALIAS PARSE_INT FOR "java.lang.Integer.parseInt(java.lang.String,int)"
@changelog_1240_li
@changelog_1243_li
#Functions now reside within a schema, similar to sequences. If you do create such functions in schemas other than PUBLIC, then the database can not be opened with older versions of H2.
@changelog_1241_li
@changelog_1244_li
#Cluster: after a cluster node failed, the second cluster node can now be re-created and started without having to stop the first cluster node, and without having to stop running applications. To do that, append ;AUTO_RECONNECT=TRUE to the database URL.
@changelog_1242_li
@changelog_1245_li
#Auto-reconnect: if another connection uses the database in exclusive mode then this connection will try to re-connect until the exclusive mode ends. This is important when using the cluster mode.
@changelog_1243_li
@changelog_1246_li
#SET EXCLUSIVE now supports 0 (disable), 1 (enable), and 2 (enable and close all other connections).
@changelog_1244_li
@changelog_1247_li
#Installing the H2 as a service should now work on Windows 7. The batch files now explicitly set the directory using pushd "%~dp0".
@changelog_1245_li
@changelog_1248_li
#Temporary tables can now be 'cached', that means indexes of temporary tables can be persisted. This enables very large temporary tables (both local and global).
@changelog_1246_li
@changelog_1249_li
#The CreateCluster tool now sets the source database in exclusive mode before copying data to the new database.
@changelog_1247_li
@changelog_1250_li
#The H2 Console now stream results one statement / result set at a time (using chunked transfer encoding). To disable, set the system property h2.consoleStream to false. This feature is not supported when using a servlet container.
@changelog_1248_li
@changelog_1251_li
#The H2 Console did not call the CreateCluster tool with the correctly escaped parameters.
@changelog_1249_li
@changelog_1252_li
#Improved PostgreSQL compatibility for ALTER TABLE ALTER COLUMN.
@changelog_1250_li
@changelog_1253_li
#Commas at the end of INSERT ... VALUES (), (), are now supported.
@changelog_1251_li
@changelog_1254_li
#The H2 Console "Start Browser" button now works even when the IP address changes while the tool runs (for example, because a wireless connection breaks, or when enabling / disabling the network connection).
@changelog_1252_li
@changelog_1255_li
#When casting from float or double to BigDecimal, the result was sometimes unexpected, because "new BigDecimal(double val)" was used. Now "BigDecimal.valueOf(double val)" and "new BigDecimal(Float.toString(f))" are used. But it is still not recommended to use float or double for currency values (see data type documentation).
@changelog_1253_li
@changelog_1256_li
#Global temporary tables are now deleted when closing the database. Before, they were deleted when opening the database the next time.
@changelog_1254_li
@changelog_1257_li
#UNIQUE was not listed as a keyword.
@changelog_1255_li
@changelog_1258_li
#Improved error message when an non-SQL-exception occurred in a user defined function. The method name and parameters are included in the error message.
@changelog_1256_li
@changelog_1259_li
#For some queries, the exception did not include the SQL statement. Example: select x from system_range(1, 2) group by 'a'.
@changelog_1257_li
@changelog_1260_li
#The Shell tool will execute SQL statements passed as using the command line parameter -sql.
@changelog_1258_li
@changelog_1261_li
#If InetAddress.getLocalHost() fails, the database should now throw an exception.
@changelog_1259_li
@changelog_1262_li
#New columns INFORMATION_SCHEMA.INDEXES.INDEX_CLASS and INFORMATION_SCHEMA.TABLES.TABLE_CLASS.
@changelog_1260_li
@changelog_1263_li
#INFORMATION_SCHEMA.INDEXES.SQL now contains the CREATE INDEX statement instead of just the fully qualified index name.
@changelog_1261_h2
@changelog_1264_h2
#Version 1.2.134 (2010-04-23)
@changelog_1262_li
@changelog_1265_li
#New system property h2.analyzeAuto (default 0 meaning disabled) to automatically run ANALYZE after that many changes to a table. For details, see the Javadoc of this system property. The plan is to set this property to 2000 in version 1.3.x.
@changelog_1263_li
@changelog_1266_li
#JdbcXAConnection.start() does not support TMJOIN. Issue 189.
@changelog_1264_li
@changelog_1267_li
#MySQL compatibility: TIMESTAMPDIFF is now an alias for DATEDIFF.
@changelog_1265_li
@changelog_1268_li
#MERGE did not respect foreign key and check constraints.
@changelog_1266_li
@changelog_1269_li
#ALTER TABLE ALTER COLUMN: changing the data type of a column no longer makes it nullable.
@changelog_1267_li
@changelog_1270_li
#When using AUTO_SERVER=TRUE, the server is now started as a daemon thread. This was a problem when using Tomcat and a connection pool.
@changelog_1268_li
@changelog_1271_li
#Servers can now be started as a daemon thread using the command line options -tcpDaemon, -pgDaemon, and -webDaemon.
@changelog_1269_li
@changelog_1272_li
#H2 Console: the built-in commands are now documented.
@changelog_1270_li
@changelog_1273_li
#REPLACE: if any parameter is null, the result is null.
@changelog_1271_li
@changelog_1274_li
#Queries with DISTINCT and ORDER BY will now use the index on ORDER BY if possible. This is specially important for queries used inside IN(SELECT ...).
@changelog_1272_li
@changelog_1275_li
#The new statement EXPLAIN ANALYZE executes the statement, and displays the query plan with the actual row scan count for each table.
@changelog_1273_li
@changelog_1276_li
#H2 Console: the auto-complete feature didn't quote column names that need quoting. Issue 186.
@changelog_1274_li
@changelog_1277_li
#The experimental LOB storage mechanism now supports all features of the old one. To use it, set the system property "h2.lobInDatabase" to "true". If you have used this feature in version 1.2.133, you need to export and re-import the database using SCRIPT / RUNSCRIPT.
@changelog_1275_li
@changelog_1278_li
#The functions isBeforeFirst() and isAfterLast() were not compliant to the JDBC spec. If the ResultSet contains no rows, they must return false. Fixed.
@changelog_1276_li
@changelog_1279_li
#Filesystem parameters like "split:" didn't work in server mode with baseDir set.
@changelog_1277_li
@changelog_1280_li
#If baseDir is set, and a database name is given which points to a directory outside the baseDir (eg. "../dbname"), an exception is thrown.
@changelog_1278_h2
@changelog_1281_h2
#Version 1.2.133 (2010-04-10)
@changelog_1279_li
@changelog_1282_li
#A new experimental LOB storage mechanism is available. When enabled, CLOB and BLOB data is stored in hidden tables in the database. To use it, set the system property "h2.lobInDatabase" to "true". Compression is not yet implemented. Duplicate objects are only stored once. Usually writing is slower, but reading is faster (mainly because of caching).
@changelog_1280_li
@changelog_1283_li
#The Shell tool threw a NumberFormatException on a empty statement.
@changelog_1281_li
@changelog_1284_li
#The h2small-*.jar did not support "drop all objects delete files". Now it is supported (the DeleteDbFiles tool is now included).
@changelog_1282_li
@changelog_1285_li
#Operations that don't fit in memory are now faster. Temporary file handling was changed.
@changelog_1283_li
@changelog_1286_li
#The default maximum log stream size is now 2 MB. This is a good value according to some performance tests.
@changelog_1284_li
@changelog_1287_li
#New system property "h2.syncMethod" to configure what method to call when closing the database, on checkpoint, and on CHECKPOINT SYNC. The default is "sync" which calls RandomAccessFile.getFD().sync().
@changelog_1285_li
@changelog_1288_li
#ROWNUM could not be used for pagination. The follow query returned no rows: select x from (select *, rownum as r from system_range(1, 3)) where r=2;
@changelog_1286_li
@changelog_1289_li
#Workaround for a java.sql.Date issue: years above 9999 are not formatted correctly. When calling ResultSet.getString() on a date value, an alternative formatting algorithm is used.
@changelog_1287_li
@changelog_1290_li
#Prepared statements with nested subqueries did not always return the correct result. Example: select ?, ?, (select count(*) from test t, (select id from test where 0=?) t2 where t2.id=t.id) from test
@changelog_1288_li
@changelog_1291_li
#When using MULTI_THREADED=TRUE, the exception following exception could be thrown: "object already exists: TABLES"
@changelog_1289_li
@changelog_1292_li
#Comparison of integer columns against float numbers was not always correct. Issue 182.
@changelog_1290_li
@changelog_1293_li
#H2 Console: Editing the result of a multi-line queries failed. Issue 183.
@changelog_1291_li
@changelog_1294_li
#H2 Console: if the settings file (.h2.properties) can't be accessed, the exception is now ignored.
@changelog_1292_h2
@changelog_1295_h2
#Version 1.2.132 (2010-03-21)
@changelog_1293_li
@changelog_1296_li
#The implementation of a Java to C (source code level) converter has been started. The plan is: it should be possible to convert H2 (or a part of it) to C so that the database can be run without a JVM. This will be a long term project (it may take a year or so).
@changelog_1294_li
@changelog_1297_li
#User defined table implementation can now be used using CREATE TABLE ... ENGINE. Thanks to Sergi Vladykin for implementing this feature!
@changelog_1295_li
@changelog_1298_li
#Improved MS SQL Server compatibility: support string concatenation using "+". Thanks to Stepan for the patch!
@changelog_1296_li
@changelog_1299_li
#When using the multi-threaded mode, running ANALYZE concurrently in multiple connections could throw an exception.
@changelog_1297_li
@changelog_1300_li
#The MERGE statement is now about 30% faster when using a PreparedStatement.
@changelog_1298_li
@changelog_1301_li
#Multi-column indexes where the second or later column was descending did not always produce correct results (rows were missing in the result set, or the result set was empty).
@changelog_1299_li
@changelog_1302_li
#When using large transactions or a small log size, the database could get very slow (profiling shows the hotspot is in FileObjectDisk.sync()).
@changelog_1300_li
@changelog_1303_li
#The Shell tool now prints the stack trace when the list mode is enabled.
@changelog_1301_li
@changelog_1304_li
#CREATE ALIAS ... AS: Compilation was incorrect if the source code contained characters that are not supported by the default file encoding.
@changelog_1302_li
@changelog_1305_li
#Issue 176: the JdbcDataSource now also supports a 'description' property.
@changelog_1303_li
@changelog_1306_li
#The Shell tool threw a ArrayIndexOutOfBoundsException after 20 statements.
@changelog_1304_li
@changelog_1307_li
#When using the small version of H2 ('jarClient'), the first call to Connection.createBlob (or similar) could throw a ClassNotFoundException because the file org.h2.store.fs.FileSystemZip is not included. This missing class is now ignored.
@changelog_1305_li
@changelog_1308_li
#Literals of type BIGINT now have the correct data type.
@changelog_1306_h2
@changelog_1309_h2
#Version 1.2.131 (2010-03-05)
@changelog_1307_li
@changelog_1310_li
#Older versions of H2 (version 1.2.127 and older) could not connect to a new version (version 1.2.129 and newer). The connection blocked when trying to connect. Now the connection no longer blocks, instead a SQL exception is thrown.
@changelog_1308_li
@changelog_1311_li
#In versions 1.2.129 and 1.2.130, a database could not be opened sometimes after dropping tables or indexes, and then creating new indexes for existing tables. The exception contained the text "parent not found" (version 1.2.129) or "Table not found" (version 1.2.130).
@changelog_1309_li
@changelog_1312_li
#After the database was closed, a null pointer exception could occur in Database.flush.
@changelog_1310_li
@changelog_1313_li
#An ArrayIndexOutOfBoundsException could occur in the page store (eg. on "delete from table"). Fixed.
@changelog_1311_h2
@changelog_1314_h2
#Version 1.2.130 (2010-02-26)
@changelog_1312_li
@changelog_1315_li
#EXPLAIN: The query plan now contains ".tableScan" if a table scan is used.
@changelog_1313_li
@changelog_1316_li
#IN(..): when combining and IN(..) condition with a condition that didn't use an index, the result could contain duplicate rows.
@changelog_1314_li
@changelog_1317_li
#IN(..): the index was not used if there were multiple IN(..) conditions.
@changelog_1315_li
@changelog_1318_li
#For foreign key constraints, the metadata column INFORMATION_SCHEMA.INDEXES.CONSTRAINT_NAME was not set for non-unique indexes.
@changelog_1316_li
@changelog_1319_li
#PostgreSQL compatibility: when using the following exception was thrown: Column "T.TYPTYPMOD" not found. Fixed. This is only when using psqlodbc_08_04*.
@changelog_1317_li
@changelog_1320_li
#A tool to migrate an old database from the non-page store format to the newest version has been added in src/tools/org/h2/dev/util/Migrate.java. This file is not included in the jar file currently.
@changelog_1318_li
@changelog_1321_li
#When using temporary tables, the database didn't shrink sometimes when closing. Also, sometimes a database could not recover normally.
@changelog_1319_li
@changelog_1322_li
#Large transactions could run out of heap space. The maximum size of a transaction is now much larger.
@changelog_1320_li
@changelog_1323_li
#The default setting for the system property h2.webMaxValueLength is now 100000 (it was 10000 before).
@changelog_1321_li
@changelog_1324_li
#Creating a database was delayed about 2 seconds if the directory didn't exist.
@changelog_1322_li
@changelog_1325_li
#Implemented INIT feature. If the database URL contains ";INIT=...;" then the DDL or DML commands following are executed on startup. Example URL: jdbc:h2:mem:test;INIT=RUNSCRIPT FROM '~/create.sql' (patch from Kerry Sainsbury).
@changelog_1323_h2
@changelog_1326_h2
#Version 1.2.129 (2010-02-19)
@changelog_1324_li
@changelog_1327_li
#The methods of the CloseListener are added to the Trigger interface. The interface CloseListener is removed. This is potentially a breaking change for existing triggers.
@changelog_1325_li
@changelog_1328_li
#CREATE ALIAS: error message when compiling Java code have been improved.
@changelog_1326_li
@changelog_1329_li
#MVCC: creating a table with an incorrect constraint could cause strange errors.
@changelog_1327_li
@changelog_1330_li
#Hash indexes now are only used for single column indexes.
@changelog_1328_li
@changelog_1331_li
#The cache types WEAK_* and TQ are no longer supported. A weak reference cache never frees up memory so it's the same as having a very large cache size. The TQ cache was not included in the jar file since a longer time, and was not tested.
@changelog_1329_li
@changelog_1332_li
#The file system abstraction no longer throws SQL exceptions.
@changelog_1330_li
@changelog_1333_li
#DatabaseEventListener.diskSpaceIsLow has changed.
@changelog_1331_li
@changelog_1334_li
#The CompressTool no longer throw as SQL exceptions. Instead, it throws runtime exceptions.
@changelog_1332_li
@changelog_1335_li
#SimpleResultSet.addColumn and addRow now can throw a IllegalStateException instead of a SQLException.
@changelog_1333_li
@changelog_1336_li
#When doing an index lookup, decimal values with the same value but different scale (for example 0.00 and 0.0) where not considered equal in version 1.2.128. Now they are (unlike BigDecimal.equals()).
@changelog_1334_li
@changelog_1337_li
#The BNF parser now uses the visitor pattern.
@changelog_1335_li
@changelog_1338_li
#Converting a UUID to bytes was incorrect. Because of that, updatable result sets on tables with UUID primary key did not work.
@changelog_1336_li
@changelog_1339_li
#The database URL property DATABASE_EVENT_LISTENER_OBJECT is no longer supported (there are problems passing objects when the PostgreSQL driver is installed as well).
@changelog_1337_li
@changelog_1340_li
#H2 Console: asynchronous login (using a DatabaseEventListener) is no longer supported.
@changelog_1338_li
@changelog_1341_li
#A workaround for a Windows socket problem has been implemented. Thanks a lot to Sergi Vladykin.
@changelog_1339_li
@changelog_1342_li
#The Recover tool did not convert correctly convert CLOB data with non-ASCII characters.
@changelog_1340_li
@changelog_1343_li
#Tools: the method run(String... args) has been renamed to runTool(String... args).
@changelog_1341_li
@changelog_1344_li
#Server.startWebServer(Connection) was not working as expected.
@changelog_1342_li
@changelog_1345_li
#The database URL option ACCESS_MODE_LOG is no longer supported.
@changelog_1343_li
@changelog_1346_li
#The database URL option RECOVER has currently no effect.
@changelog_1344_li
@changelog_1347_li
#Converting an old (non-page store) database is no longer supported using this version.
@changelog_1345_li
@changelog_1348_li
#The following system properties are no longer supported: h2.overflowExceptions, h2.optimizeDropDependencies, h2.optimizeGroupSorted, h2.optimizeMinMax, h2.optimizeNot, h2.optimizeIn, h2.optimizeInJoin, h2.reuseSpace*. Most of then were there for a long time, but always with the same value. There was no unit test with the other value. So changing them was potentially dangerous (not a lot, but still).
@changelog_1346_li
@changelog_1349_li
#The setting LOG has currently no effect (it only had an effect when the page store was disabled).
@changelog_1347_li
@changelog_1350_li
#Disabling the page store is no longer supported. The old storage mechanism has been removed, shrinking the jar file size by almost 10%.
@changelog_1348_li
@changelog_1351_li
#The translated resources are now stored in UTF-8 format.
@changelog_1349_li
@changelog_1352_li
#The Windows service wrapper now detects if multiple versions of H2 are installed.
@changelog_1350_h2
@changelog_1353_h2
#Version 1.2.128 (2010-01-30)
@changelog_1351_li
@changelog_1354_li
#There are known errors on rollback when the page store is disabled and at the same time MVCC is used. See http://code.google.com/p/h2database/issues/detail?id=158
@changelog_1352_li
@changelog_1355_li
#The DeleteDbFiles tool deleted all files in the .lob.db directory, even files that didn't belong to the database.
@changelog_1353_li
@changelog_1356_li
#Automatic conversion of old databases to the page store format failed if the database contained LOB files.
@changelog_1354_li
@changelog_1357_li
#Nested subqueries didn't work for INSERT INTO and IN(..). Example: insert into test ((select 1));
@changelog_1355_li
@changelog_1358_li
#If the database was already closed using SHUTDOWN IMMEDIATELY, closing a second connection could throw a NullPointerException if there was a local temporary table.
@changelog_1356_li
@changelog_1359_li
#Less classes are loaded when using the database in embedded mode.
@changelog_1357_li
@changelog_1360_li
#The information schema tables are only initialized when needed. This reduces memory usage and speeds up creating in-memory databases. Each in-memory database needs about 8 KB of heap memory.
@changelog_1358_li
@changelog_1361_li
#Nested UNION/INTERSECT queries with brackets could produce the wrong result if used within a subquery. Example: select count(*) from (select 1 union (select 2 intersect select 2)) x;
@changelog_1359_li
@changelog_1362_li
#Comparing an column against a constant expression with a higher precision or length than the column could give wrong results (the expression was truncated before comparing).
@changelog_1360_li
@changelog_1363_li
#Improved PostgreSQL compatibility (support SHOW DEFAULT_TRANSACTION_ISOLATION).
@changelog_1361_li
@changelog_1364_li
#Documentation: the javadocs for Csv.write and read used the wrong default charset.
@changelog_1362_li
@changelog_1365_li
#MVCC: if the table was locked in exclusive mode (such as SELECT ... FOR UPDATE), another session could query the table. This is now longer possible.
@changelog_1363_li
@changelog_1366_li
#If a FOR UPDATE query was executed twice (using a PreparedStatement), the table was not locked.
@changelog_1364_li
@changelog_1367_li
#Triggers: INSTEAD OF triggers are now supported. Such triggers can be defined on views.
@changelog_1365_li
@changelog_1368_li
#New system property h2.identifiersToUpper. If set to false, identifiers in SQL statements are case sensitive even if they are not quoted.
@changelog_1366_li
@changelog_1369_li
#Slightly improved performance if the table is already locked.
@changelog_1367_li
@changelog_1370_li
#CompressLZF: faster decompression.
@changelog_1368_li
@changelog_1371_li
#PgServer: the wrong size was sent for VARCHAR data. Thanks again to Sergi Vladykin for the patch.
@changelog_1369_li
@changelog_1372_li
#Serialized access mode (server-less multi-connection mode): fixed getGeneratedKeys() for sequences.
@changelog_1370_h2
@changelog_1373_h2
#Version 1.2.127 (2010-01-15)
@changelog_1371_li
@changelog_1374_li
#Serialized access mode (server-less multi-connection mode): sequences did not work as expected (there were gaps in generated values when using multiple connections).
@changelog_1372_li
@changelog_1375_li
#Page store: new databases can not be opened with older versions.
@changelog_1373_li
@changelog_1376_li
#Page store: adding data to new database is now faster.
@changelog_1374_li
@changelog_1377_li
#File system: getting the file name from a path is now faster. This should speed up BLOB and CLOB access.
@changelog_1375_li
@changelog_1378_li
#PgServer: incorrect SQL types were returned in result set meta data. Concurrently opening a database could fail (PG catalog initialization was not synchronized). Thanks a lot to Sergi Vladykin for providing the patches!
@changelog_1376_li
@changelog_1379_li
#SHOW COLUMNS did not work correctly if there where multiple indexes on the same columns.
@changelog_1377_li
@changelog_1380_li
#Page store: the wrong write count was written to the database header. This could cause the server-less multi-connection mode to fail.
@changelog_1378_li
@changelog_1381_li
#Result sets larger than 2 GB threw an exception "Negative seek offset". Fixed.
@changelog_1379_li
@changelog_1382_li
#If the system property h2.check was set to false, an ArrayIndexOutOfBoundsException could occur.
@changelog_1380_li
@changelog_1383_li
#Alter table is now supported even if a table has views defined. (Patch from Kerry Sainsbury).
@changelog_1381_li
@changelog_1384_li
#Fulltext search: exceptions within the fulltext search package had the wrong SQL state.
@changelog_1382_li
@changelog_1385_li
#The Lucene fulltext search ignored transaction rollback. Fixed using a trigger on rollback.
@changelog_1383_li
@changelog_1386_li
#Trigger can now be called on rollback.
@changelog_1384_li
@changelog_1387_li
#The shell script h2.sh ignored command line line arguments.
@changelog_1385_li
@changelog_1388_li
#When running H2 in the Google AppEngine for Java, a AccessControlException could be thrown when trying to open a read-only database. Fixed.
@changelog_1386_li
@changelog_1389_li
#The user home directory prefix (~) is now only expanded when followed by a slash or backslash, or standing alone.
@changelog_1387_li
@changelog_1390_li
#Native fulltext search: before inserting or deleting data, FT_INIT() had to be called. This is no longer required.
@changelog_1388_li
@changelog_1391_li
#The .trace.db file is now only created if required.
@changelog_1389_li
@changelog_1392_li
#Shell tool: improved PostgreSQL compatibility.
@changelog_1390_li
@changelog_1393_li
#Trying to open a database in read-only mode when a .lock.db file exists will now fail with a nice error message.
@changelog_1391_li
@changelog_1394_li
#H2 Console: data that is too long is now abbreviated as follows: text... (100000 characters). A large binary is abbreviated as follows: abcdef... (100000 bytes).
@changelog_1392_li
@changelog_1395_li
#Faster data conversion from BIGINT or INT to DECIMAL.
@changelog_1393_li
@changelog_1396_li
#Server-less multi-connection mode: try to delete log files if switching between read/write operations.
@changelog_1394_li
@changelog_1397_li
#CompressLZF: Faster decompress and improved javadocs
@changelog_1395_h2
@changelog_1398_h2
#Version 1.2.126 (2009-12-18)
@changelog_1396_li
@changelog_1399_li
#The ChangeFileEncryption tool will now fail with an exception if the database is still in use. The Backup tool will also fail except when running in quiet mode.
@changelog_1397_li
@changelog_1400_li
#CSVREAD: when reading the column names from the CSV file, column names that contain no special characters are considered case insensitive now.
@changelog_1398_li
@changelog_1401_li
#Optimization index conditions of the form 'column=NULL' (which is always false; unlike 'column IS NULL').
@changelog_1399_li
@changelog_1402_li
#Script command and tool: the primary key constraint is now listed before inserting the data. This will result in a smaller database when using the page store.
@changelog_1400_li
@changelog_1403_li
#Statements with IN(SELECT..) conditions could produce the wrong result. Example: index on id, name; query: select * from test where id between 1 and 3 and name in (select 'World').
@changelog_1401_li
@changelog_1404_li
#Statements with IN(..) conditions could produce the wrong result when using views or nested select statements. Example: index on id; index on name; query: select * from (select * from test) where id=1 and name in('a', 'b'). select * from (select * from test) where id=1 and name in('Hello', 'World').
@changelog_1402_li
@changelog_1405_li
#Page store: a rollback of a relatively large transaction could fail with an ArrayIndexOutOfBoundsException or a 'row not found' exception in the PageBtreeIndex in some cases.
@changelog_1403_li
@changelog_1406_li
#JaQu: the decompiler has been improved, and a few test cases already work. It is still incomplete however.
@changelog_1404_li
@changelog_1407_li
#LIKE: any letter is now allowed after the escape character (which is still '\' by default). Previously, an exception was thrown (unlike other databases) if it was not the escape character, '_' or '%'. If the escape character appears at the end of the pattern, the result is it is ignored (like PostgreSQL and MS SQL Server).
@changelog_1405_li
@changelog_1408_li
#The reserve heap memory is no longer used.
@changelog_1406_li
@changelog_1409_li
#Database.checkpoint() could throw a NullPointerException.
@changelog_1407_h2
@changelog_1410_h2
#Version 1.2.125 (2009-12-06)
@changelog_1408_li
@changelog_1411_li
#Lucene fulltext search: the Lucene field names now match the table column names, except if the column names start with _ (in which case another _ is prepended). Unfortunately this change means existing fulltext indexes need to be re-built.
@changelog_1409_li
@changelog_1412_li
#The shell tool now has a very simple statement history.
@changelog_1410_li
@changelog_1413_li
#The zip file system implementation now supports the '~' home directory prefix. Example database URL: jdbc:h2:zip:~/test.zip!/test
@changelog_1411_li
@changelog_1414_li
#Right outer joins on tables that were already 'inner joined' was processed incorrectly.
@changelog_1412_li
@changelog_1415_li
#Temporary files from LOB objects were not deleted early enough when using the server mode.
@changelog_1413_li
@changelog_1416_li
#Trying to alter a temporary table threw a strange exception. It is still not possible to do that, but the exception message is better now.
@changelog_1414_li
@changelog_1417_li
#When the system property h2.maxMemoryRowsDistinct was set, and using SELECT DISTINCT, the temporary table was not correctly dropped. This could cause problems in recovery when the process was killed.
@changelog_1415_li
@changelog_1418_li
#Trigger that are called before a select statement are now supported. This allows to create tables that work like materialized views.
@changelog_1416_li
@changelog_1419_li
#Non-row based triggers were called even if the action didn't match the declared action (INSERT triggers were also called when deleting rows). This has been changed. The MERGE statement calls both INSERT and DELETE triggers.
@changelog_1417_li
@changelog_1420_li
#Statements with IN(..) conditions could produce the wrong result or a data conversion error (since version 1.2.120). Examples: index on id, name, condition: id=1 and name in('Hello', 'x'); index on id, query: select * from (select * from test) where id=1 and name in('Hello', 'World').
@changelog_1418_li
@changelog_1421_li
#The CompressTool was not multithreading safe. Because of this, the following database operations where also not multithreading safe (even when using different databases): the SCRIPT command (only when using compression), the COMPRESS function, and storing CLOB or BLOB data (only when compression is enabled).
@changelog_1419_li
@changelog_1422_li
#The compression algorithm "LZF" is now about 33% faster than before when compressing small block (around 2 KB). It is much faster than Deflate, but the compression ratio is lower. Some of the optimizations are from Sam Van Oort, thanks a lot!
@changelog_1420_li
@changelog_1423_li
#Compressing large blocks of data didn't work when using the "Deflate" compression algorithm. Compressing a lot of data could run out of heap memory.
@changelog_1421_li
@changelog_1424_li
#The test cases don't access the file system directly, this simplifies GAE for Java testing. Thanks to Vince Bonfanti.
@changelog_1422_li
@changelog_1425_li
#More bugs in the server-less multi-connection mode have been fixed.
@changelog_1423_li
@changelog_1426_li
#When running against an old database, the SCRIPT statement could generate a SQL script that contained duplicate indexes (PRIMARY_KEY_E).
@changelog_1424_li
@changelog_1427_li
#JdbcConnectionPool.getConnection() could throw a NullPointerException.
@changelog_1425_li
@changelog_1428_li
#User defined functions: the source code is now available using SELECT SOURCE FROM INFORMATION_SCHEMA.FUNCTION_ALIASES.
@changelog_1426_li
@changelog_1429_li
#User defined functions with source code didn't work after re-opening the database.
@changelog_1427_li
@changelog_1430_li
#The newsfeeds are now Atom 1.0 standard compliant.
@changelog_1428_li
@changelog_1431_li
#The database is now closed after an out of memory exception, because the database could get corrupt otherwise.
@changelog_1429_li
@changelog_1432_li
#Better error message if both AUTO_SERVER and SERIALIZED parameters are set to TRUE.
@changelog_1430_li
@changelog_1433_li
#Drop table did not delete lob files in old file store (not PAGE_STORE).
@changelog_1431_h2
@changelog_1434_h2
#Version 1.2.124 (2009-11-20)
@changelog_1432_li
@changelog_1435_li
#Clustering: there is now a way to detect which cluster instances are running.
@changelog_1433_li
@changelog_1436_li
#ConvertTraceFile: the SQL statement statistics are better formatted (newline are removed).
@changelog_1434_li
@changelog_1437_li
#The file lock thread is now stopped when the database is closed.
@changelog_1435_li
@changelog_1438_li
#Issue 140: the Script tool now supports writing to a stream.
@changelog_1436_li
@changelog_1439_li
#Issue 138: the trace output of Statement.execute(String, int) and executeUpdate was incorrect.
@changelog_1437_li
@changelog_1440_li
#Page store: new databases can not be opened with older versions.
@changelog_1438_li
@changelog_1441_li
#Page store: multi-column indexes didn't work if the cache was very small.
@changelog_1439_li
@changelog_1442_li
#Page store: opening a database could theoretically result in an endless loop.
@changelog_1440_li
@changelog_1443_li
#Page store: adding large indexed columns could get very slow.
@changelog_1441_li
@changelog_1444_li
#Page store: after a duplicate key exception, an ArrayIndexOutOfBoundsException could be thrown (only for very large rows).
@changelog_1442_li
@changelog_1445_li
#Page store: the recover tool sometimes generated a script file that contained duplicate data.
@changelog_1443_li
@changelog_1446_li
#Page store: sometimes opening a read-only database failed.
@changelog_1444_li
@changelog_1447_li
#Page store: opening a database sometimes failed if large rows where updated, or if a table was truncated before.
@changelog_1445_li
@changelog_1448_li
#Page store: when using a very small page size (128 bytes or smaller), writing a large row could result in an endless recursion. This is only a theoretical problem, as the page size is 2 KB.
@changelog_1446_li
@changelog_1449_li
#Page store: getting the min value from a descending index with NULL entries could return the wrong result.
@changelog_1447_li
@changelog_1450_li
#Page store: improved auto-recovery after power failure.
@changelog_1448_li
@changelog_1451_li
#The JDBC client did not detect that it was not talking to an H2 server. This could result in strange exceptions when trying to connect to another kind of server.
@changelog_1449_li
@changelog_1452_li
#User defined functions can be created with source code. Example: CREATE ALIAS HI AS 'String hi() { return "Hello"; }'
@changelog_1450_li
@changelog_1453_li
#Database file lock: the exception "lock file modified in the future" is no longer thrown; instead, opening the file will be delayed by 2 seconds.
@changelog_1451_li
@changelog_1454_li
#Inserting LOBs got slower each time the process was restarted. It could loop endlessly after about 1000 process restarts.
@changelog_1452_li
@changelog_1455_li
#Issue 117: Multi-version concurrency: concurrent MERGE statements now work.
@changelog_1453_li
@changelog_1456_li
#Improved read-only database detection.
@cheatSheet_1000_h1
...
...
@@ -5555,7 +5570,7 @@ Sourceファイル
#What is JaQu
@jaqu_1012_p
# JaQu stands for Java Query and allows to access databases using pure Java. JaQu provides a fluent interface (or internal DSL) to access a database. JaQu is something like LINQ for Java (LINQ stands for "language integrated query" and is a Microsoft .NET technology). The following JaQu code:
# JaQu stands for Java Query and allows to access databases using pure Java. JaQu provides a fluent interface (or internal DSL). JaQu is something like LINQ for Java (LINQ stands for "language integrated query" and is a Microsoft .NET technology). The following JaQu code:
@jaqu_1013_p
# stands for the SQL statement:
...
...
@@ -5564,13 +5579,13 @@ Sourceファイル
#Differences to Other Data Access Tools
@jaqu_1015_p
# Unlike SQL, JaQu can be easily integrated in Java applications. Because JaQu is pure Java, auto-complete in the IDE and Javadoc and are supported. Type checking is performed by the compiler. JaQu fully protects against SQL injection.
# Unlike SQL, JaQu can be easily integrated in Java applications. Because JaQu is pure Java, auto-complete in the IDE is supported. Type checking is performed by the compiler. JaQu fully protects against SQL injection.
@jaqu_1016_p
# JaQu is more a replacement for JDBC than it is a replacement for tools like Hibernate. With JaQu, you don't write SQL statements as Strings. JaQu is much smaller and simpler than other persistence frameworks such as Hibernate, but it also does not provide all the features of those. Unlike iBatis and Hibernate, no XML or annotation based configuration is required; instead the configuration (if required at all) is done in pure Java, in the application itself.
# JaQu is meant as replacement for JDBC and SQL and not as much as a replacement for tools like Hibernate. With JaQu, you don't write SQL statements as strings. JaQu is much smaller and simpler than other persistence frameworks such as Hibernate, but it also does not provide all the features of those. Unlike iBatis and Hibernate, no XML or annotation based configuration is required; instead the configuration (if required at all) is done in pure Java, within the application.
@jaqu_1017_p
# JaQu does not require or contain any data caching mechanism. Like JDBC and iBatis, JaQu provides full control over when and what SQL statements are executed (but without having to write SQL statements as Strings).
# JaQu does not require or contain any data caching mechanism. Like JDBC and iBatis, JaQu provides full control over when and what SQL statements are executed (but without having to write SQL statements as strings).
@jaqu_1018_h3
#Restrictions
...
...
@@ -5582,7 +5597,7 @@ Sourceファイル
#Why in Java?
@jaqu_1021_p
# Most people use Java in their application. Mixing Java and another language (for example Scala or Groovy) in the same application is complicated: you would need to split the application and database code.
# Most applications are written in Java. Mixing Java and another language (for example Scala or Groovy) in the same application is complicated: you would need to split the application and database code, and write adapter / wrapper code.
@jaqu_1022_h2
#Current State
...
...
@@ -5621,22 +5636,22 @@ Sourceファイル
#Configuration
@jaqu_1034_p
# JaQu does not require any configuration when using the default mapping. To define table indices, or if you want to map a class to a table with a different name, or a field to a column with another name, create a function called <code>define</code> in the data class. Example:
# JaQu does not require any configuration when using the default field to column mapping. To define table indices, or if you want to map a class to a table with a different name, or a field to a column with another name, create a function called <code>define</code> in the data class. Example:
@jaqu_1035_p
# The method <code>define()</code> contains the mapping definition. It is called once when the class is used for the first time. Like annotations, the mapping is defined in the class itself. Unlike when using annotations, the compiler can check the syntax even for multi-column objects (multi-column indexes, multi-column primary keys and so on). Because the definition is written in regular Java, the configuration can depend on the environment. This is not possible using annotations. Unlike XML mapping configuration, the configuration is integrated in the class itself.
# The method <code>define()</code> contains the mapping definition. It is called once when the class is used for the first time. Like annotations, the mapping is defined in the class itself. Unlike when using annotations, the compiler can check the syntax even for multi-column objects (multi-column indexes, multi-column primary keys and so on). Because the definition is written in Java, the configuration can be set at runtime, which is not possible using annotations. Unlike XML mapping configuration, the configuration is integrated in the class itself.
@jaqu_1036_h2
#Natural Syntax
@jaqu_1037_p
#The plan is to support more natural (pure Java) syntax in conditions. To do that, the condition class is de-compiled to a SQL condition. A proof of concept decompiler is included (but it doesn't work yet). The planned syntax is:
#The plan is to support more natural (pure Java) syntax in conditions. To do that, the condition class is de-compiled to a SQL condition. A proof of concept decompiler is included (but it doesn't fully work yet; patches are welcome). The planned syntax is:
@jaqu_1038_h2
#Other Ideas
@jaqu_1039_p
# This project has just been started, and nothing is fixed yet. Some ideas for what to implement are:
# This project has just been started, and nothing is fixed yet. Some ideas are:
@jaqu_1040_li
#Support queries on collections (instead of using a database).
...
...
@@ -5705,10 +5720,10 @@ Sourceファイル
# H2 is dual licensed and available under a modified version of the MPL 1.1 (<a href="http://www.mozilla.org/MPL">Mozilla Public License</a>) or under the (unmodified) EPL 1.0 (<a href="http://opensource.org/licenses/eclipse-1.0.php">Eclipse Public License</a>). The changes to the MPL are
@license_1006_em
#underlined</em>. There is a License FAQ for both the MPL and the EPL, most of that is applicable to the H2 License as well.
#underlined</em>. There is a license FAQ for both the MPL and the EPL, most of that is applicable to the H2 license as well.
@license_1007_li
#You can use H2 for free. You can integrate it into your application (including commercial applications), and you can distribute it.
#You can use H2 for free. You can integrate it into your applications (including in commercial applications), and you can distribute it.
@license_1008_li
#Files containing only your code are not covered by this license (it is 'commercial friendly').
...
...
@@ -6170,7 +6185,7 @@ Sourceファイル
#H2 In Use and Links
@links_1001_p
# Those are just a few links to products using or supporting H2. If you want to add a link, please send it to the support email address or post it in the group.
# Listed below are just a few links to products using or supporting H2. If you want to add a link, please send it to the support email address or post it to the group.
@links_1002_a
# Books
...
...
@@ -10111,16 +10126,19 @@ H2 コンソール アプリケーション
@roadmap_1481_li
#Allow to defragment at runtime (similar to SHUTDOWN DEFRAG) in a background thread.
@roadmap_1482_h2
@roadmap_1482_li
#Support for Thread.interrupt to cancel running statements.
@roadmap_1483_h2
#Not Planned
@roadmap_1483_li
@roadmap_1484_li
#HSQLDB (did) support this: select id i from test where i<0 (other databases don't). Supporting it may break compatibility.
@roadmap_1484_li
@roadmap_1485_li
#String.intern (so that Strings can be compared with ==) will not be used because some VMs have problems when used extensively.
@roadmap_1485_li
@roadmap_1486_li
#In prepared statements, identifier names (table names and so on) can not be parameterized. Adding such a feature would complicate the source code without providing reasonable speedup, and would slow down regular prepared statements.
@sourceError_1000_h1
...
...
@@ -11033,7 +11051,7 @@ Java Web Start / JNLP
Luceneフルテキストサーチを使用する
@tutorial_1290_p
# To use the Lucene full text search, you need the Lucene library in the classpath. Currently only Apache Lucene version 2.x is supported. How to do that depends on the application; if you use the H2 Console, you can add the Lucene jar file to the environment variables <code>H2DRIVERS</code> or <code>CLASSPATH</code>. To initialize the Lucene fulltext search in a database, call:
# To use the Lucene full text search, you need the Lucene library in the classpath. Currently Apache Lucene version 2.x is used by default for H2 version 1.2.x, and Lucene version 3.x is used by default for H2 version 1.3.x. How to do that depends on the application; if you use the H2 Console, you can add the Lucene jar file to the environment variables <code>H2DRIVERS</code> or <code>CLASSPATH</code>. To initialize the Lucene fulltext search in a database, call:
@tutorial_1291_p
# You need to initialize it in each database where you want to use it. Afterwards, you can create a full text index for a table using:
