In Eclipse, create a new Java project from existing source code: <code>File, New, Project, Java Project, Create project from existing source</code>.
In Eclipse, create a new Java project from existing source code: <code>File, New, Project, Java Project, Create project from existing source</code>.
@build_1065_li
@build_1068_li
Select the <code>h2</code> folder, click <code>Next</code> and <code>Finish</code>.
Select the <code>h2</code> folder, click <code>Next</code> and <code>Finish</code>.
@build_1066_li
@build_1069_li
To resolve <code>com.sun.javadoc</code> import statements, you may need to manually add the file <code><java.home>/../lib/tools.jar</code> to the build path.
To resolve <code>com.sun.javadoc</code> import statements, you may need to manually add the file <code><java.home>/../lib/tools.jar</code> to the build path.
@build_1067_h2
@build_1070_h2
Translating
Translating
@build_1068_p
@build_1071_p
The translation of this software is split into the following parts:
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.
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_1072_h2
@build_1075_h2
Providing Patches
Providing Patches
@build_1073_p
@build_1076_p
If you like to provide patches, please consider the following guidelines to simplify merging them:
If you like to provide patches, please consider the following guidelines to simplify merging them:
@build_1074_li
@build_1077_li
Only use Java 6 features (do not use Java 7) (see <a href="#environment">Environment</a>).
Only use Java 6 features (do not use Java 7) (see <a href="#environment">Environment</a>).
@build_1075_li
@build_1078_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>.
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_1076_li
@build_1079_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.
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_1077_li
@build_1080_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>.
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_1078_li
@build_1081_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>.
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_1079_li
@build_1082_li
Verify that you did not break other features: run the test cases by executing <code>build test</code>.
Verify that you did not break other features: run the test cases by executing <code>build test</code>.
@build_1080_li
@build_1083_li
Provide end user documentation if required (<code>src/docsrc/html/*</code>).
Provide end user documentation if required (<code>src/docsrc/html/*</code>).
@build_1081_li
@build_1084_li
Document grammar changes in <code>src/docsrc/help/help.csv</code>
Document grammar changes in <code>src/docsrc/help/help.csv</code>
@build_1082_li
@build_1085_li
Provide a change log entry (<code>src/docsrc/html/changelog.html</code>).
Provide a change log entry (<code>src/docsrc/html/changelog.html</code>).
@build_1083_li
@build_1086_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>.
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_1084_li
@build_1087_li
Run <code>src/installer/buildRelease</code> to find and fix formatting errors.
Run <code>src/installer/buildRelease</code> to find and fix formatting errors.
@build_1085_li
@build_1088_li
Verify the formatting using <code>build docs</code> and <code>build javadoc</code>.
Verify the formatting using <code>build docs</code> and <code>build javadoc</code>.
@build_1086_li
@build_1089_li
Submit patches as <code>.patch</code> files (compressed if big). To create a patch using Eclipse, use Team / Create Patch.
Submit patches as <code>.patch</code> files (compressed if big). To create a patch using Eclipse, use Team / Create Patch.
@build_1087_p
@build_1090_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:
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="https://github.com/h2database/h2database/issues">issue report or attachment</a>. Significant contributions need to include the following statement:
@build_1088_p
@build_1091_p
"I wrote the code, it's mine, and I'm contributing it to H2 for distribution multiple-licensed under the MPL 2.0, and the EPL 1.0 (http://h2database.com/html/license.html)."
"I wrote the code, it's mine, and I'm contributing it to H2 for distribution multiple-licensed under the MPL 2.0, and the EPL 1.0 (http://h2database.com/html/license.html)."
@build_1089_h2
@build_1092_h2
Reporting Problems or Requests
Reporting Problems or Requests
@build_1090_p
@build_1093_p
Please consider the following checklist if you have a question, want to report a problem, or if you have a feature request:
Please consider the following checklist if you have a question, want to report a problem, or if you have a feature request:
@build_1091_li
@build_1094_li
For bug reports, please provide a <a href="http://sscce.org/">short, self contained, correct (compilable), example</a> of the problem.
For bug reports, please provide a <a href="http://sscce.org/">short, self contained, correct (compilable), example</a> of the problem.
@build_1092_li
@build_1095_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>.
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_1093_li
@build_1096_li
Before posting problems, check the <a href="faq.html">FAQ</a> and do a <a href="http://google.com">Google search</a>.
Before posting problems, check the <a href="faq.html">FAQ</a> and do a <a href="http://google.com">Google search</a>.
@build_1094_li
@build_1097_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).
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_1095_li
@build_1098_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.
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="https://github.com/h2database/h2database/tree/master/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_1096_li
@build_1099_li
For large attachments, use a public temporary storage such as <a href="http://rapidshare.com">Rapidshare</a>.
For large attachments, use a public temporary storage such as <a href="http://rapidshare.com">Rapidshare</a>.
@build_1097_li
@build_1100_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.
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="https://github.com/h2database/h2database/issues">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_1098_li
@build_1101_li
For out-of-memory problems, please analyze the problem yourself first, for example using the command line option <code>-XX:+HeapDumpOnOutOfMemoryError</code> (to create a heap dump file on out of memory) and a memory analysis tool such as the <a href="http://www.eclipse.org/mat">Eclipse Memory Analyzer (MAT)</a>.
For out-of-memory problems, please analyze the problem yourself first, for example using the command line option <code>-XX:+HeapDumpOnOutOfMemoryError</code> (to create a heap dump file on out of memory) and a memory analysis tool such as the <a href="http://www.eclipse.org/mat">Eclipse Memory Analyzer (MAT)</a>.
@build_1099_li
@build_1102_li
It may take a few days to get an answers. Please do not double post.
It may take a few days to get an answers. Please do not double post.
@build_1100_h2
@build_1103_h2
Automated Build
Automated Build
@build_1101_p
@build_1104_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:
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_1102_a
@build_1105_a
Test Output
Test Output
@build_1103_a
@build_1106_a
Code Coverage Summary
Code Coverage Summary
@build_1104_a
@build_1107_a
Code Coverage Details (download, 1.3 MB)
Code Coverage Details (download, 1.3 MB)
@build_1105_a
@build_1108_a
Build Newsfeed
Build Newsfeed
@build_1106_a
@build_1109_a
Latest Jar File (download, 1 MB)
Latest Jar File (download, 1 MB)
@build_1107_h2
@build_1110_h2
Generating Railroad Diagrams
Generating Railroad Diagrams
@build_1108_p
@build_1111_p
The railroad diagrams of the <a href="grammar.html">SQL grammar</a> are HTML, formatted as nested tables. The diagrams are generated as follows:
The railroad diagrams of the <a href="grammar.html">SQL grammar</a> are HTML, formatted as nested tables. The diagrams are generated as follows:
@build_1109_li
@build_1112_li
The BNF parser (<code>org.h2.bnf.Bnf</code>) reads and parses the BNF from the file <code>help.csv</code>.
The BNF parser (<code>org.h2.bnf.Bnf</code>) reads and parses the BNF from the file <code>help.csv</code>.
@build_1110_li
@build_1113_li
The page parser (<code>org.h2.server.web.PageParser</code>) reads the template HTML file and fills in the diagrams.
The page parser (<code>org.h2.server.web.PageParser</code>) reads the template HTML file and fills in the diagrams.
@build_1111_li
@build_1114_li
The rail images (one straight, four junctions, two turns) are generated using a simple Java application.
The rail images (one straight, four junctions, two turns) are generated using a simple Java application.
@build_1112_p
@build_1115_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.
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
@changelog_1000_h1
...
@@ -1889,636 +1898,663 @@ Change Log
...
@@ -1889,636 +1898,663 @@ Change Log
Next Version (unreleased)
Next Version (unreleased)
@changelog_1002_li
@changelog_1002_li
-
Granting a schema is now supported.
@changelog_1003_h2
@changelog_1003_li
Version 1.4.187 Beta (2015-04-10)
Linked tables did not work when a function-based index is present (Oracle).
@changelog_1004_li
@changelog_1004_li
MVStore: concurrent changes to the same row could result in the exception "The transaction log might be corrupt for key ...". This could only be reproduced with 3 or more threads.
Creating a user with a null password, salt, or hash threw a NullPointerException.
@changelog_1005_li
@changelog_1005_li
Results with CLOB or BLOB data are no longer reused.
Foreign key: don't add a single column index if column is leading key of existing index.
@changelog_1006_li
@changelog_1006_li
References to BLOB and CLOB objects now have a timeout. The configuration setting is LOB_TIMEOUT (default 5 minutes). This should avoid growing the database file if there are many queries that return BLOB or CLOB objects, and the database is not closed for a longer time.
Pull request #4: Creating and removing temporary tables was getting slower and slower over time, because an internal object id was allocated but never de-allocated.
@changelog_1007_li
@changelog_1007_li
MVStore: when committing a session that removed LOB values, changes were flushed unnecessarily.
Issue 609: the spatial index did not support NULL with update and delete operations.
@changelog_1008_li
@changelog_1008_li
Issue 610: possible integer overflow in WriteBuffer.grow().
Pull request #2: Add external metadata type support (table type "external")
@changelog_1009_li
@changelog_1009_li
Issue 609: the spatial index did not support NULL (ClassCastException).
MS SQL Server: the CONVERT method did not work in views and derived tables.
@changelog_1010_li
@changelog_1010_li
MVStore: in some cases, CLOB/BLOB data blocks were removed incorrectly when opening a database.
Java 8 compatibility for "regexp_replace".
@changelog_1011_li
@changelog_1011_li
When in cluster mode, and one of the nodes goes down, we need to log the problem with priority "error", not "debug"
@changelog_1012_h2
Version 1.4.187 Beta (2015-04-10)
@changelog_1013_li
MVStore: concurrent changes to the same row could result in the exception "The transaction log might be corrupt for key ...". This could only be reproduced with 3 or more threads.
@changelog_1014_li
Results with CLOB or BLOB data are no longer reused.
@changelog_1015_li
References to BLOB and CLOB objects now have a timeout. The configuration setting is LOB_TIMEOUT (default 5 minutes). This should avoid growing the database file if there are many queries that return BLOB or CLOB objects, and the database is not closed for a longer time.
@changelog_1016_li
MVStore: when committing a session that removed LOB values, changes were flushed unnecessarily.
@changelog_1017_li
Issue 610: possible integer overflow in WriteBuffer.grow().
@changelog_1018_li
Issue 609: the spatial index did not support NULL (ClassCastException).
@changelog_1019_li
MVStore: in some cases, CLOB/BLOB data blocks were removed incorrectly when opening a database.
@changelog_1020_li
MVStore: updates that affected many rows were were slow in some cases if there was a secondary index.
MVStore: updates that affected many rows were were slow in some cases if there was a secondary index.
@changelog_1012_li
@changelog_1021_li
Using "runscript" with autocommit disabled could result in a lock timeout on the internal table "SYS".
Using "runscript" with autocommit disabled could result in a lock timeout on the internal table "SYS".
@changelog_1013_li
@changelog_1022_li
Issue 603: there was a memory leak when using H2 in a web application. Apache Tomcat logged an error message: "The web application ... created a ThreadLocal with key of type [org.h2.util.DateTimeUtils$1]".
Issue 603: there was a memory leak when using H2 in a web application. Apache Tomcat logged an error message: "The web application ... created a ThreadLocal with key of type [org.h2.util.DateTimeUtils$1]".
@changelog_1014_li
@changelog_1023_li
When using the MVStore, running a SQL script generate by the Recover tool from a PageStore file failed with a strange error message (NullPointerException), now a clear error message is shown.
When using the MVStore, running a SQL script generate by the Recover tool from a PageStore file failed with a strange error message (NullPointerException), now a clear error message is shown.
@changelog_1015_li
@changelog_1024_li
Issue 605: with version 1.4.186, opening a database could result in an endless loop in LobStorageMap.init.
Issue 605: with version 1.4.186, opening a database could result in an endless loop in LobStorageMap.init.
@changelog_1016_li
@changelog_1025_li
Queries that use the same table alias multiple times now work. Before, the select expression list was expanded incorrectly. Example: "select * from a as x, b as x".
Queries that use the same table alias multiple times now work. Before, the select expression list was expanded incorrectly. Example: "select * from a as x, b as x".
@changelog_1017_li
@changelog_1026_li
The MySQL compatibility feature "insert ... on duplicate key update" did not work with a non-default schema.
The MySQL compatibility feature "insert ... on duplicate key update" did not work with a non-default schema.
@changelog_1018_li
@changelog_1027_li
Issue 599: the condition "in(x, y)" could not be used in the select list when using "group by".
Issue 599: the condition "in(x, y)" could not be used in the select list when using "group by".
@changelog_1019_li
@changelog_1028_li
The LIRS cache could grow larger than the allocated memory.
The LIRS cache could grow larger than the allocated memory.
@changelog_1020_li
@changelog_1029_li
A new file system implementation that re-opens the file if it was closed due to the application calling Thread.interrupt(). File name prefix "retry:". Please note it is strongly recommended to avoid calling Thread.interrupt; this is a problem for various libraries, including Apache Lucene.
A new file system implementation that re-opens the file if it was closed due to the application calling Thread.interrupt(). File name prefix "retry:". Please note it is strongly recommended to avoid calling Thread.interrupt; this is a problem for various libraries, including Apache Lucene.
@changelog_1021_li
@changelog_1030_li
MVStore: use RandomAccessFile file system if the file name starts with "file:".
MVStore: use RandomAccessFile file system if the file name starts with "file:".
@changelog_1022_li
@changelog_1031_li
Allow DATEADD to take a long value for count when manipulating milliseconds.
Allow DATEADD to take a long value for count when manipulating milliseconds.
@changelog_1023_li
@changelog_1032_li
When using MV_STORE=TRUE and the SET CACHE_SIZE setting, the cache size was incorrectly set, so that it was effectively 1024 times smaller than it should be.
When using MV_STORE=TRUE and the SET CACHE_SIZE setting, the cache size was incorrectly set, so that it was effectively 1024 times smaller than it should be.
@changelog_1024_li
@changelog_1033_li
Concurrent CREATE TABLE... IF NOT EXISTS in the presence of MULTI_THREAD=TRUE could throw an exception.
Concurrent CREATE TABLE... IF NOT EXISTS in the presence of MULTI_THREAD=TRUE could throw an exception.
@changelog_1025_li
@changelog_1034_li
Fix bug in MVStore when creating lots of temporary tables, where we could run out of transaction IDs.
Fix bug in MVStore when creating lots of temporary tables, where we could run out of transaction IDs.
@changelog_1026_li
@changelog_1035_li
Add support for PostgreSQL STRING_AGG function. Patch by Fred Aquiles.
Add support for PostgreSQL STRING_AGG function. Patch by Fred Aquiles.
@changelog_1027_li
@changelog_1036_li
Fix bug in "jdbc:h2:nioMemFS" isRoot() function. Also, the page size was increased to 64 KB.
Fix bug in "jdbc:h2:nioMemFS" isRoot() function. Also, the page size was increased to 64 KB.
@changelog_1028_h2
@changelog_1037_h2
Version 1.4.186 Beta (2015-03-02)
Version 1.4.186 Beta (2015-03-02)
@changelog_1029_li
@changelog_1038_li
The Servlet API 3.0.1 is now used, instead of 2.4.
The Servlet API 3.0.1 is now used, instead of 2.4.
@changelog_1030_li
@changelog_1039_li
MVStore: old chunks no longer removed in append-only mode.
MVStore: old chunks no longer removed in append-only mode.
@changelog_1031_li
@changelog_1040_li
MVStore: the cache for page references could grow far too big, resulting in out of memory in some cases.
MVStore: the cache for page references could grow far too big, resulting in out of memory in some cases.
@changelog_1032_li
@changelog_1041_li
MVStore: orphaned lob objects were not correctly removed in some cases, making the database grow unnecessarily.
MVStore: orphaned lob objects were not correctly removed in some cases, making the database grow unnecessarily.
@changelog_1033_li
@changelog_1042_li
MVStore: the maximum cache size was artificially limited to 2 GB (due to an integer overflow).
MVStore: the maximum cache size was artificially limited to 2 GB (due to an integer overflow).
@changelog_1034_li
@changelog_1043_li
MVStore / TransactionStore: concurrent updates could result in a "Too many open transactions" exception.
MVStore / TransactionStore: concurrent updates could result in a "Too many open transactions" exception.
@changelog_1035_li
@changelog_1044_li
StringUtils.toUpperEnglish now has a small cache. This should speed up reading from a ResultSet when using the column name.
StringUtils.toUpperEnglish now has a small cache. This should speed up reading from a ResultSet when using the column name.
@changelog_1036_li
@changelog_1045_li
MVStore: up to 65535 open transactions are now supported. Previously, the limit was at most 65535 transactions between the oldest open and the newest open transaction (which was quite a strange limit).
MVStore: up to 65535 open transactions are now supported. Previously, the limit was at most 65535 transactions between the oldest open and the newest open transaction (which was quite a strange limit).
@changelog_1037_li
@changelog_1046_li
The default limit for in-place LOB objects was changed from 128 to 256 bytes. This is because each read creates a reference to a LOB, and maintaining the references is a big overhead. With the higher limit, less references are needed.
The default limit for in-place LOB objects was changed from 128 to 256 bytes. This is because each read creates a reference to a LOB, and maintaining the references is a big overhead. With the higher limit, less references are needed.
@changelog_1038_li
@changelog_1047_li
Tables without columns didn't work. (The use case for such tables is testing.)
Tables without columns didn't work. (The use case for such tables is testing.)
@changelog_1039_li
@changelog_1048_li
The LIRS cache now resizes the table automatically in all cases and no longer needs the averageMemory configuration.
The LIRS cache now resizes the table automatically in all cases and no longer needs the averageMemory configuration.
@changelog_1040_li
@changelog_1049_li
Creating a linked table from an MVStore database to a non-MVStore database created a second (non-MVStore) database file.
Creating a linked table from an MVStore database to a non-MVStore database created a second (non-MVStore) database file.
@changelog_1041_li
@changelog_1050_li
In version 1.4.184, a bug was introduced that broke queries that have both joins and wildcards, for example: select * from dual join(select x from dual) on 1=1
In version 1.4.184, a bug was introduced that broke queries that have both joins and wildcards, for example: select * from dual join(select x from dual) on 1=1
@changelog_1042_li
@changelog_1051_li
Issue 598: parser fails on timestamp "24:00:00.1234" - prevent the creation of out-of-range time values.
Issue 598: parser fails on timestamp "24:00:00.1234" - prevent the creation of out-of-range time values.
@changelog_1043_li
@changelog_1052_li
Allow declaring triggers as source code (like functions). Patch by Sylvain Cuaz.
Allow declaring triggers as source code (like functions). Patch by Sylvain Cuaz.
@changelog_1044_li
@changelog_1053_li
Make the planner use indexes for sorting when doing a GROUP BY where all of the GROUP BY columns are not mentioned in the select. Patch by Frederico (zepfred).
Make the planner use indexes for sorting when doing a GROUP BY where all of the GROUP BY columns are not mentioned in the select. Patch by Frederico (zepfred).
@changelog_1045_li
@changelog_1054_li
PostgreSQL compatibility: generate_series (as an alias for system_range). Patch by litailang.
PostgreSQL compatibility: generate_series (as an alias for system_range). Patch by litailang.
@changelog_1046_li
@changelog_1055_li
Fix missing "column" type in right-hand parameter in ConditionIn. Patch by Arnaud Thimel.
Fix missing "column" type in right-hand parameter in ConditionIn. Patch by Arnaud Thimel.
@changelog_1047_h2
@changelog_1056_h2
Version 1.4.185 Beta (2015-01-16)
Version 1.4.185 Beta (2015-01-16)
@changelog_1048_li
@changelog_1057_li
In version 1.4.184, "group by" ignored the table name, and could pick a select column by mistake. Example: select 0 as x from system_range(1, 2) d group by d.x;
In version 1.4.184, "group by" ignored the table name, and could pick a select column by mistake. Example: select 0 as x from system_range(1, 2) d group by d.x;
@changelog_1049_li
@changelog_1058_li
New connection setting "REUSE_SPACE" (default: true). If disabled, all changes are appended to the database file, and existing content is never overwritten. This allows to rollback to a previous state of the database by truncating the database file.
New connection setting "REUSE_SPACE" (default: true). If disabled, all changes are appended to the database file, and existing content is never overwritten. This allows to rollback to a previous state of the database by truncating the database file.
@changelog_1050_li
@changelog_1059_li
Issue 587: MVStore: concurrent compaction and store operations could result in an IllegalStateException.
Issue 587: MVStore: concurrent compaction and store operations could result in an IllegalStateException.
@changelog_1051_li
@changelog_1060_li
Issue 594: Profiler.copyInThread does not work properly.
Issue 594: Profiler.copyInThread does not work properly.
@changelog_1052_li
@changelog_1061_li
Script tool: Now, SCRIPT ... TO is always used (for higher speed and lower disk space usage).
Script tool: Now, SCRIPT ... TO is always used (for higher speed and lower disk space usage).
@changelog_1053_li
@changelog_1062_li
Script tool: Fix parsing of BLOCKSIZE parameter, original patch by Ken Jorissen.
Script tool: Fix parsing of BLOCKSIZE parameter, original patch by Ken Jorissen.
@changelog_1054_li
@changelog_1063_li
Fix bug in PageStore#commit method - when the ignoreBigLog flag was set, the logic that cleared the flag could never be reached, resulting in performance degradation. Reported by Alexander Nesterov.
Fix bug in PageStore#commit method - when the ignoreBigLog flag was set, the logic that cleared the flag could never be reached, resulting in performance degradation. Reported by Alexander Nesterov.
@changelog_1055_li
@changelog_1064_li
Issue 552: Implement BIT_AND and BIT_OR aggregate functions.
Issue 552: Implement BIT_AND and BIT_OR aggregate functions.
@changelog_1056_h2
@changelog_1065_h2
Version 1.4.184 Beta (2014-12-19)
Version 1.4.184 Beta (2014-12-19)
@changelog_1057_li
@changelog_1066_li
In version 1.3.183, indexes were not used if the table contains columns with a default value generated by a sequence. This includes tables with identity and auto-increment columns. This bug was introduced by supporting "rownum" in views and derived tables.
In version 1.3.183, indexes were not used if the table contains columns with a default value generated by a sequence. This includes tables with identity and auto-increment columns. This bug was introduced by supporting "rownum" in views and derived tables.
@changelog_1058_li
@changelog_1067_li
MVStore: imported BLOB and CLOB data sometimes disappeared. This was caused by a bug in the ObjectDataType comparison.
MVStore: imported BLOB and CLOB data sometimes disappeared. This was caused by a bug in the ObjectDataType comparison.
@changelog_1059_li
@changelog_1068_li
Reading from a StreamStore now throws an IOException if the underlying data doesn't exist.
Reading from a StreamStore now throws an IOException if the underlying data doesn't exist.
@changelog_1060_li
@changelog_1069_li
MVStore: if there is an exception while saving, the store is now in all cases immediately closed.
MVStore: if there is an exception while saving, the store is now in all cases immediately closed.
@changelog_1061_li
@changelog_1070_li
MVStore: the dump tool could go into an endless loop for some files.
MVStore: the dump tool could go into an endless loop for some files.
@changelog_1062_li
@changelog_1071_li
MVStore: recovery for a database with many CLOB or BLOB entries is now much faster.
MVStore: recovery for a database with many CLOB or BLOB entries is now much faster.
@changelog_1063_li
@changelog_1072_li
Group by with a quoted select column name alias didn't work. Example: select 1 "a" from dual group by "a"
Group by with a quoted select column name alias didn't work. Example: select 1 "a" from dual group by "a"
@changelog_1064_li
@changelog_1073_li
Auto-server mode: the host name is now stored in the .lock.db file.
Auto-server mode: the host name is now stored in the .lock.db file.
@changelog_1065_h2
@changelog_1074_h2
Version 1.4.183 Beta (2014-12-13)
Version 1.4.183 Beta (2014-12-13)
@changelog_1066_li
@changelog_1075_li
MVStore: the default auto-commit buffer size is now about twice as big. This should reduce the database file size after inserting a lot of data.
MVStore: the default auto-commit buffer size is now about twice as big. This should reduce the database file size after inserting a lot of data.
@changelog_1067_li
@changelog_1076_li
The built-in functions "power" and "radians" now always return a double.
The built-in functions "power" and "radians" now always return a double.
@changelog_1068_li
@changelog_1077_li
Using "row_number" or "rownum" in views or derived tables had unexpected results if the outer query contained constraints for the given view. Example: select b.nr, b.id from (select row_number() over() as nr, a.id as id from (select id from test order by name) as a) as b where b.id = 1
Using "row_number" or "rownum" in views or derived tables had unexpected results if the outer query contained constraints for the given view. Example: select b.nr, b.id from (select row_number() over() as nr, a.id as id from (select id from test order by name) as a) as b where b.id = 1
@changelog_1069_li
@changelog_1078_li
MVStore: the Recover tool can now deal with more types of corruption in the file.
MVStore: the Recover tool can now deal with more types of corruption in the file.
@changelog_1070_li
@changelog_1079_li
MVStore: the TransactionStore now first needs to be initialized before it can be used.
MVStore: the TransactionStore now first needs to be initialized before it can be used.
@changelog_1071_li
@changelog_1080_li
Views and derived tables with equality and range conditions on the same columns did not work properly. example: select x from (select x from (select 1 as x) where x > 0 and x < 2) where x = 1
Views and derived tables with equality and range conditions on the same columns did not work properly. example: select x from (select x from (select 1 as x) where x > 0 and x < 2) where x = 1
@changelog_1072_li
@changelog_1081_li
The database URL setting PAGE_SIZE setting is now also used for the MVStore.
The database URL setting PAGE_SIZE setting is now also used for the MVStore.
@changelog_1073_li
@changelog_1082_li
MVStore: the default page split size for persistent stores is now 4096 (it was 16 KB so far). This should reduce the database file size for most situations (in some cases, less than half the size of the previous version).
MVStore: the default page split size for persistent stores is now 4096 (it was 16 KB so far). This should reduce the database file size for most situations (in some cases, less than half the size of the previous version).
@changelog_1074_li
@changelog_1083_li
With query literals disabled, auto-analyze of a table with CLOB or BLOB did not work.
With query literals disabled, auto-analyze of a table with CLOB or BLOB did not work.
@changelog_1075_li
@changelog_1084_li
MVStore: use a mark and sweep GC algorithm instead of reference counting, to ensure used chunks are never overwrite, even if the reference counting algorithm does not work properly.
MVStore: use a mark and sweep GC algorithm instead of reference counting, to ensure used chunks are never overwrite, even if the reference counting algorithm does not work properly.
@changelog_1076_li
@changelog_1085_li
In the multi-threaded mode, updating the column selectivity ("analyze") in the background sometimes did not work.
In the multi-threaded mode, updating the column selectivity ("analyze") in the background sometimes did not work.
@changelog_1077_li
@changelog_1086_li
In the multi-threaded mode, database metadata operations did sometimes not work if the schema was changed at the same time (for example, if tables were dropped).
In the multi-threaded mode, database metadata operations did sometimes not work if the schema was changed at the same time (for example, if tables were dropped).
@changelog_1078_li
@changelog_1087_li
Some CLOB and BLOB values could no longer be read when the original row was removed (even when using the MVCC mode).
Some CLOB and BLOB values could no longer be read when the original row was removed (even when using the MVCC mode).
@changelog_1079_li
@changelog_1088_li
The MVStoreTool could throw an IllegalArgumentException.
The MVStoreTool could throw an IllegalArgumentException.
@changelog_1080_li
@changelog_1089_li
Improved performance for some date / time / timestamp conversion operations. Thanks to Sergey Evdokimov for reporting the problem.
Improved performance for some date / time / timestamp conversion operations. Thanks to Sergey Evdokimov for reporting the problem.
@changelog_1081_li
@changelog_1090_li
H2 Console: the built-in web server did not work properly if an unknown file was requested.
H2 Console: the built-in web server did not work properly if an unknown file was requested.
@changelog_1082_li
@changelog_1091_li
MVStore: the jar file is renamed to "h2-mvstore-*.jar" and is deployed to Maven separately.
MVStore: the jar file is renamed to "h2-mvstore-*.jar" and is deployed to Maven separately.
@changelog_1083_li
@changelog_1092_li
MVStore: support for concurrent reads and writes is now enabled by default.
MVStore: support for concurrent reads and writes is now enabled by default.
@changelog_1084_li
@changelog_1093_li
Server mode: the transfer buffer size has been changed from 16 KB to 64 KB, after it was found that this improves performance on Linux quite a lot.
Server mode: the transfer buffer size has been changed from 16 KB to 64 KB, after it was found that this improves performance on Linux quite a lot.
@changelog_1085_li
@changelog_1094_li
H2 Console and server mode: SSL is now disabled and TLS is used to protect against the Poodle SSLv3 vulnerability. The system property to disable secure anonymous connections is now "h2.enableAnonymousTLS". The default certificate is still self-signed, so you need to manually install another one if you want to avoid man in the middle attacks.
H2 Console and server mode: SSL is now disabled and TLS is used to protect against the Poodle SSLv3 vulnerability. The system property to disable secure anonymous connections is now "h2.enableAnonymousTLS". The default certificate is still self-signed, so you need to manually install another one if you want to avoid man in the middle attacks.
@changelog_1086_li
@changelog_1095_li
MVStore: the R-tree did not correctly measure the memory usage.
MVStore: the R-tree did not correctly measure the memory usage.
@changelog_1087_li
@changelog_1096_li
MVStore: compacting a store with an R-tree did not always work.
MVStore: compacting a store with an R-tree did not always work.
@changelog_1088_li
@changelog_1097_li
Issue 581: When running in LOCK_MODE=0, JdbcDatabaseMetaData#supportsTransactionIsolationLevel(TRANSACTION_READ_UNCOMMITTED) should return false
Issue 581: When running in LOCK_MODE=0, JdbcDatabaseMetaData#supportsTransactionIsolationLevel(TRANSACTION_READ_UNCOMMITTED) should return false
@changelog_1089_li
@changelog_1098_li
Fix bug which could generate deadlocks when multiple connections accessed the same table.
Fix bug which could generate deadlocks when multiple connections accessed the same table.
@changelog_1090_li
@changelog_1099_li
Some places in the code were not respecting the value set in the "SET MAX_MEMORY_ROWS x" command
Some places in the code were not respecting the value set in the "SET MAX_MEMORY_ROWS x" command
@changelog_1091_li
@changelog_1100_li
Fix bug which could generate a NegativeArraySizeException when performing large (>40M) row union operations
Fix bug which could generate a NegativeArraySizeException when performing large (>40M) row union operations
@changelog_1092_li
@changelog_1101_li
Fix "USE schema" command for MySQL compatibility, patch by mfulton
Fix "USE schema" command for MySQL compatibility, patch by mfulton
@changelog_1093_li
@changelog_1102_li
Parse and ignore the ROW_FORMAT=DYNAMIC MySQL syntax, patch by mfulton
Parse and ignore the ROW_FORMAT=DYNAMIC MySQL syntax, patch by mfulton
@changelog_1094_h2
@changelog_1103_h2
Version 1.4.182 Beta (2014-10-17)
Version 1.4.182 Beta (2014-10-17)
@changelog_1095_li
@changelog_1104_li
MVStore: improved error messages and logging; improved behavior if there is an error when serializing objects.
MVStore: improved error messages and logging; improved behavior if there is an error when serializing objects.
@changelog_1096_li
@changelog_1105_li
OSGi: the MVStore packages are now exported.
OSGi: the MVStore packages are now exported.
@changelog_1097_li
@changelog_1106_li
With the MVStore option, when using multiple threads that concurrently create indexes or tables, it was relatively easy to get a lock timeout on the "SYS" table.
With the MVStore option, when using multiple threads that concurrently create indexes or tables, it was relatively easy to get a lock timeout on the "SYS" table.
@changelog_1098_li
@changelog_1107_li
When using the multi-threaded option, the exception "Unexpected code path" could be thrown, specially if the option "analyze_auto" was set to a low value.
When using the multi-threaded option, the exception "Unexpected code path" could be thrown, specially if the option "analyze_auto" was set to a low value.
@changelog_1099_li
@changelog_1108_li
In the server mode, when reading from a CLOB or BLOB, if the connection was closed, a NullPointerException could be thrown instead of an exception saying the connection is closed.
In the server mode, when reading from a CLOB or BLOB, if the connection was closed, a NullPointerException could be thrown instead of an exception saying the connection is closed.
@changelog_1100_li
@changelog_1109_li
DatabaseMetaData.getProcedures and getProcedureColumns could throw an exception if a user defined class is not available.
DatabaseMetaData.getProcedures and getProcedureColumns could throw an exception if a user defined class is not available.
@changelog_1101_li
@changelog_1110_li
Issue 584: the error message for a wrong sequence definition was wrong.
Issue 584: the error message for a wrong sequence definition was wrong.
@changelog_1102_li
@changelog_1111_li
CSV tool: the rowSeparator option is no longer supported, as the same can be achieved with the lineSeparator.
CSV tool: the rowSeparator option is no longer supported, as the same can be achieved with the lineSeparator.
@changelog_1103_li
@changelog_1112_li
Descending indexes on MVStore tables did not work properly.
Descending indexes on MVStore tables did not work properly.
@changelog_1104_li
@changelog_1113_li
Issue 579: Conditions on the "_rowid_" pseudo-column didn't use an index when using the MVStore.
Issue 579: Conditions on the "_rowid_" pseudo-column didn't use an index when using the MVStore.
@changelog_1105_li
@changelog_1114_li
Fixed documentation that "offset" and "fetch" are also keywords since version 1.4.x.
Fixed documentation that "offset" and "fetch" are also keywords since version 1.4.x.
@changelog_1106_li
@changelog_1115_li
The Long.MIN_VALUE could not be parsed for auto-increment (identity) columns.
The Long.MIN_VALUE could not be parsed for auto-increment (identity) columns.
@changelog_1107_li
@changelog_1116_li
Issue 573: Add implementation for Methods "isWrapperFor()" and "unwrap()" in other JDBC classes.
Issue 573: Add implementation for Methods "isWrapperFor()" and "unwrap()" in other JDBC classes.
@changelog_1108_li
@changelog_1117_li
Issue 572: MySQL compatibility for "order by" in update statements.
Issue 572: MySQL compatibility for "order by" in update statements.
@changelog_1109_li
@changelog_1118_li
The change in JDBC escape processing in version 1.4.181 affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax "{t 'time}", or "{ts 'timestamp'}", or "{d 'data'}", then both the client and the server need to be upgraded to version 1.4.181 or later.
The change in JDBC escape processing in version 1.4.181 affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax "{t 'time}", or "{ts 'timestamp'}", or "{d 'data'}", then both the client and the server need to be upgraded to version 1.4.181 or later.
@changelog_1110_h2
@changelog_1119_h2
Version 1.4.181 Beta (2014-08-06)
Version 1.4.181 Beta (2014-08-06)
@changelog_1111_li
@changelog_1120_li
Improved MySQL compatibility by supporting "use schema". Thanks a lot to Karl Pietrzak for the patch!
Improved MySQL compatibility by supporting "use schema". Thanks a lot to Karl Pietrzak for the patch!
@changelog_1112_li
@changelog_1121_li
Writing to the trace file is now faster, specially with the debug level.
Writing to the trace file is now faster, specially with the debug level.
@changelog_1113_li
@changelog_1122_li
The database option "defrag_always=true" did not work with the MVStore.
The database option "defrag_always=true" did not work with the MVStore.
@changelog_1114_li
@changelog_1123_li
The JDBC escape syntax {ts 'value'} did not interpret the value as a timestamp. The same for {d 'value'} (for date) and {t 'value'} (for time). Thanks to Lukas Eder for reporting the issue. The following problem was detected after version 1.4.181 was released: The change in JDBC escape processing affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax {t 'time'}, or {ts 'timestamp'}, or {d 'date'}, then both the client and the server need to be upgraded to version 1.4.181 or later.
The JDBC escape syntax {ts 'value'} did not interpret the value as a timestamp. The same for {d 'value'} (for date) and {t 'value'} (for time). Thanks to Lukas Eder for reporting the issue. The following problem was detected after version 1.4.181 was released: The change in JDBC escape processing affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax {t 'time'}, or {ts 'timestamp'}, or {d 'date'}, then both the client and the server need to be upgraded to version 1.4.181 or later.
@changelog_1115_li
@changelog_1124_li
File system abstraction: support replacing existing files using move (currently not for Windows).
File system abstraction: support replacing existing files using move (currently not for Windows).
@changelog_1116_li
@changelog_1125_li
The statement "shutdown defrag" now compresses the database (with the MVStore). This command can greatly reduce the file size, and is relatively fast, but is not incremental.
The statement "shutdown defrag" now compresses the database (with the MVStore). This command can greatly reduce the file size, and is relatively fast, but is not incremental.
@changelog_1117_li
@changelog_1126_li
The MVStore now automatically compacts the store in the background if there is no read or write activity, which should (after some time; sometimes about one minute) reduce the file size. This is still work in progress, feedback is welcome!
The MVStore now automatically compacts the store in the background if there is no read or write activity, which should (after some time; sometimes about one minute) reduce the file size. This is still work in progress, feedback is welcome!
@changelog_1118_li
@changelog_1127_li
Change default value of PAGE_SIZE from 2048 to 4096 to more closely match most file systems block size (PageStore only; the MVStore already used 4096).
Change default value of PAGE_SIZE from 2048 to 4096 to more closely match most file systems block size (PageStore only; the MVStore already used 4096).
@changelog_1119_li
@changelog_1128_li
Auto-scale MAX_MEMORY_ROWS and CACHE_SIZE settings by the amount of available RAM. Gives a better out of box experience for people with more powerful machines.
Auto-scale MAX_MEMORY_ROWS and CACHE_SIZE settings by the amount of available RAM. Gives a better out of box experience for people with more powerful machines.
@changelog_1120_li
@changelog_1129_li
Handle tabs like 4 spaces in web console, patch by Martin Grajcar.
Handle tabs like 4 spaces in web console, patch by Martin Grajcar.
@changelog_1121_li
@changelog_1130_li
Issue 573: Add implementation for Methods "isWrapperFor()" and "unwrap()" in JdbcConnection.java, patch by BigMichi1.
Issue 573: Add implementation for Methods "isWrapperFor()" and "unwrap()" in JdbcConnection.java, patch by BigMichi1.
@changelog_1122_h2
@changelog_1131_h2
Version 1.4.180 Beta (2014-07-13)
Version 1.4.180 Beta (2014-07-13)
@changelog_1123_li
@changelog_1132_li
MVStore: the store is now auto-compacted automatically up to some point, to avoid very large file sizes. This area is still work in progress.
MVStore: the store is now auto-compacted automatically up to some point, to avoid very large file sizes. This area is still work in progress.
@changelog_1124_li
@changelog_1133_li
Sequences of temporary tables (auto-increment or identity columns) were persisted unnecessarily in the database file, and were not removed when re-opening the database.
Sequences of temporary tables (auto-increment or identity columns) were persisted unnecessarily in the database file, and were not removed when re-opening the database.
@changelog_1125_li
@changelog_1134_li
MVStore: an IndexOutOfBoundsException could sometimes occur MVMap.openVersion when concurrently accessing the store.
MVStore: an IndexOutOfBoundsException could sometimes occur MVMap.openVersion when concurrently accessing the store.
@changelog_1126_li
@changelog_1135_li
The LIRS cache now re-sizes the internal hash map if needed.
The LIRS cache now re-sizes the internal hash map if needed.
@changelog_1127_li
@changelog_1136_li
Optionally persist session history in the H2 console. (patch from Martin Grajcar)
Optionally persist session history in the H2 console. (patch from Martin Grajcar)
@changelog_1128_li
@changelog_1137_li
Add client-info property to get the number of servers currently in the cluster and which servers that are available. (patch from Nikolaj Fogh)
Add client-info property to get the number of servers currently in the cluster and which servers that are available. (patch from Nikolaj Fogh)
@changelog_1129_li
@changelog_1138_li
Fix bug in changing encrypted DB password that kept the file handle open when the wrong password was supplied. (test case from Jens Hohmuth).
Fix bug in changing encrypted DB password that kept the file handle open when the wrong password was supplied. (test case from Jens Hohmuth).
@changelog_1130_li
@changelog_1139_li
Issue 567: H2 hangs for a long time then (sometimes) recovers. Introduce a queue when doing table locking to prevent session starvation.
Issue 567: H2 hangs for a long time then (sometimes) recovers. Introduce a queue when doing table locking to prevent session starvation.
@changelog_1131_h2
@changelog_1140_h2
Version 1.4.179 Beta (2014-06-23)
Version 1.4.179 Beta (2014-06-23)
@changelog_1132_li
@changelog_1141_li
The license was changed to MPL 2.0 (from 1.0) and EPL 1.0.
The license was changed to MPL 2.0 (from 1.0) and EPL 1.0.
@changelog_1133_li
@changelog_1142_li
Issue 565: MVStore: concurrently adding LOB objects (with MULTI_THREADED option) resulted in a NullPointerException.
Issue 565: MVStore: concurrently adding LOB objects (with MULTI_THREADED option) resulted in a NullPointerException.
@changelog_1134_li
@changelog_1143_li
MVStore: reduced dependencies to other H2 classes.
MVStore: reduced dependencies to other H2 classes.
@changelog_1135_li
@changelog_1144_li
There was a way to prevent a database from being re-opened, by creating a column constraint that references a table with a higher id, for example with "check" constraints that contains queries. This is now detected, and creating the table is prohibited. In future versions of H2, most likely creating references to other tables will no longer be supported because of such problems.
There was a way to prevent a database from being re-opened, by creating a column constraint that references a table with a higher id, for example with "check" constraints that contains queries. This is now detected, and creating the table is prohibited. In future versions of H2, most likely creating references to other tables will no longer be supported because of such problems.
@changelog_1136_li
@changelog_1145_li
MVStore: descending indexes with "nulls first" did not work as expected (null was ordered last).
MVStore: descending indexes with "nulls first" did not work as expected (null was ordered last).
@changelog_1137_li
@changelog_1146_li
Large result sets now always create temporary tables instead of temporary files.
Large result sets now always create temporary tables instead of temporary files.
@changelog_1138_li
@changelog_1147_li
When using the PageStore, opening a database failed in some cases with a NullPointerException if temporary tables were used (explicitly, or implicitly when using large result sets).
When using the PageStore, opening a database failed in some cases with a NullPointerException if temporary tables were used (explicitly, or implicitly when using large result sets).
@changelog_1139_li
@changelog_1148_li
If a database file in the PageStore file format exists, this file and this mode is now used, even if the database URL does not contain "MV_STORE=FALSE". If a MVStore file exists, it is used.
If a database file in the PageStore file format exists, this file and this mode is now used, even if the database URL does not contain "MV_STORE=FALSE". If a MVStore file exists, it is used.
@changelog_1140_li
@changelog_1149_li
Databases created with version 1.3.175 and earlier that contained foreign keys in combination with multi-column indexes could not be opened in some cases. This was due to a bugfix in version 1.3.176: Referential integrity constraints sometimes used the wrong index.
Databases created with version 1.3.175 and earlier that contained foreign keys in combination with multi-column indexes could not be opened in some cases. This was due to a bugfix in version 1.3.176: Referential integrity constraints sometimes used the wrong index.
@changelog_1141_li
@changelog_1150_li
MVStore: the ObjectDataType comparison method was incorrect if one key was Serializable and the other was of a common class.
MVStore: the ObjectDataType comparison method was incorrect if one key was Serializable and the other was of a common class.
@changelog_1142_li
@changelog_1151_li
Recursive queries with many result rows (more than the setting "max_memory_rows") did not work correctly.
Recursive queries with many result rows (more than the setting "max_memory_rows") did not work correctly.
@changelog_1143_li
@changelog_1152_li
The license has changed to MPL 2.0 + EPL 1.0.
The license has changed to MPL 2.0 + EPL 1.0.
@changelog_1144_li
@changelog_1153_li
MVStore: temporary tables from result sets could survive re-opening a database, which could result in a ClassCastException.
MVStore: temporary tables from result sets could survive re-opening a database, which could result in a ClassCastException.
@changelog_1145_li
@changelog_1154_li
Issue 566: MVStore: unique indexes that were created later on did not work correctly if there were over 5000 rows in the table. Existing databases need to be re-created (at least the broken index need to be re-built).
Issue 566: MVStore: unique indexes that were created later on did not work correctly if there were over 5000 rows in the table. Existing databases need to be re-created (at least the broken index need to be re-built).
@changelog_1146_li
@changelog_1155_li
MVStore: creating secondary indexes on large tables results in missing rows in the index.
MVStore: creating secondary indexes on large tables results in missing rows in the index.
@changelog_1147_li
@changelog_1156_li
Metadata: the password of linked tables is now only visible for admin users.
Metadata: the password of linked tables is now only visible for admin users.
@changelog_1148_li
@changelog_1157_li
For Windows, database URLs of the form "jdbc:h2:/test" where considered relative and did not work unless the system property "h2.implicitRelativePath" was used.
For Windows, database URLs of the form "jdbc:h2:/test" where considered relative and did not work unless the system property "h2.implicitRelativePath" was used.
@changelog_1149_li
@changelog_1158_li
Windows: using a base directory of "C:/" and similar did not work as expected.
Windows: using a base directory of "C:/" and similar did not work as expected.
@changelog_1150_li
@changelog_1159_li
Follow JDBC specification on Procedures MetaData, use P0 as return type of procedure.
Follow JDBC specification on Procedures MetaData, use P0 as return type of procedure.
@changelog_1151_li
@changelog_1160_li
Issue 531: IDENTITY ignored for added column.
Issue 531: IDENTITY ignored for added column.
@changelog_1152_li
@changelog_1161_li
FileSystem: improve exception throwing compatibility with JDK
FileSystem: improve exception throwing compatibility with JDK
@changelog_1153_li
@changelog_1162_li
Spatial Index: adjust costs so we do not use the spatial index if the query does not contain an intersects operator.
Spatial Index: adjust costs so we do not use the spatial index if the query does not contain an intersects operator.
@changelog_1154_li
@changelog_1163_li
Fix multi-threaded deadlock when using a View that includes a TableFunction.
Fix multi-threaded deadlock when using a View that includes a TableFunction.
@changelog_1155_li
@changelog_1164_li
Fix bug in dividing very-small BigDecimal numbers.
Fix bug in dividing very-small BigDecimal numbers.
@changelog_1156_h2
@changelog_1165_h2
Version 1.4.178 Beta (2014-05-02)
Version 1.4.178 Beta (2014-05-02)
@changelog_1157_li
@changelog_1166_li
Issue 559: Make dependency on org.osgi.service.jdbc optional.
Issue 559: Make dependency on org.osgi.service.jdbc optional.
@changelog_1158_li
@changelog_1167_li
Improve error message when the user specifies an unsupported combination of database settings.
Improve error message when the user specifies an unsupported combination of database settings.
@changelog_1159_li
@changelog_1168_li
MVStore: in the multi-threaded mode, NullPointerException and other exceptions could occur.
MVStore: in the multi-threaded mode, NullPointerException and other exceptions could occur.
@changelog_1160_li
@changelog_1169_li
MVStore: some database file could not be compacted due to a bug in the bookkeeping of the fill rate. Also, database file were compacted quite slowly. This has been improved; but more changes in this area are expected.
MVStore: some database file could not be compacted due to a bug in the bookkeeping of the fill rate. Also, database file were compacted quite slowly. This has been improved; but more changes in this area are expected.
@changelog_1161_li
@changelog_1170_li
MVStore: support for volatile maps (that don't store changes).
MVStore: support for volatile maps (that don't store changes).
@changelog_1162_li
@changelog_1171_li
MVStore mode: in-memory databases now also use the MVStore.
MVStore mode: in-memory databases now also use the MVStore.
@changelog_1163_li
@changelog_1172_li
In server mode, appending ";autocommit=false" to the database URL was working, but the return value of Connection.getAutoCommit() was wrong.
In server mode, appending ";autocommit=false" to the database URL was working, but the return value of Connection.getAutoCommit() was wrong.
@changelog_1164_li
@changelog_1173_li
Issue 561: OSGi: the import package declaration of org.h2 excluded version 1.4.
Issue 561: OSGi: the import package declaration of org.h2 excluded version 1.4.
@changelog_1165_li
@changelog_1174_li
Issue 558: with the MVStore, a NullPointerException could occur when using LOBs at session commit (LobStorageMap.removeLob).
Issue 558: with the MVStore, a NullPointerException could occur when using LOBs at session commit (LobStorageMap.removeLob).
@changelog_1166_li
@changelog_1175_li
Remove the "h2.MAX_MEMORY_ROWS_DISTINCT" system property to reduce confusion. We already have the MAX_MEMORY_ROWS setting which does a very similar thing, and is better documented.
Remove the "h2.MAX_MEMORY_ROWS_DISTINCT" system property to reduce confusion. We already have the MAX_MEMORY_ROWS setting which does a very similar thing, and is better documented.
@changelog_1167_li
@changelog_1176_li
Issue 554: Web Console in an IFrame was not fully supported.
Issue 554: Web Console in an IFrame was not fully supported.
@changelog_1168_h2
@changelog_1177_h2
Version 1.4.177 Beta (2014-04-12)
Version 1.4.177 Beta (2014-04-12)
@changelog_1169_li
@changelog_1178_li
By default, the MV_STORE option is enabled, so it is using the new MVStore storage. The MVCC setting is by default set to the same values as the MV_STORE setting, so it is also enabled by default. For testing, both settings can be disabled by appending ";MV_STORE=FALSE" and/or ";MVCC=FALSE" to the database URL.
By default, the MV_STORE option is enabled, so it is using the new MVStore storage. The MVCC setting is by default set to the same values as the MV_STORE setting, so it is also enabled by default. For testing, both settings can be disabled by appending ";MV_STORE=FALSE" and/or ";MVCC=FALSE" to the database URL.
@changelog_1170_li
@changelog_1179_li
The file locking method 'serialized' is no longer supported. This mode might return in a future version, however this is not clear right now. A new implementation and new tests would be needed.
The file locking method 'serialized' is no longer supported. This mode might return in a future version, however this is not clear right now. A new implementation and new tests would be needed.
@changelog_1171_li
@changelog_1180_li
Enable the new storage format for dates (system property "h2.storeLocalTime"). For the MVStore mode, this is always enabled, but with version 1.4 this is even enabled in the PageStore mode.
Enable the new storage format for dates (system property "h2.storeLocalTime"). For the MVStore mode, this is always enabled, but with version 1.4 this is even enabled in the PageStore mode.
@changelog_1172_li
@changelog_1181_li
Implicit relative paths are disabled (system property "h2.implicitRelativePath"), so that the database URL jdbc:h2:test now needs to be written as jdbc:h2:./test.
Implicit relative paths are disabled (system property "h2.implicitRelativePath"), so that the database URL jdbc:h2:test now needs to be written as jdbc:h2:./test.
@changelog_1173_li
@changelog_1182_li
"select ... fetch first 1 row only" is supported with the regular mode. This was disabled so far because "fetch" and "offset" are now keywords. See also Mode.supportOffsetFetch.
"select ... fetch first 1 row only" is supported with the regular mode. This was disabled so far because "fetch" and "offset" are now keywords. See also Mode.supportOffsetFetch.
@changelog_1174_li
@changelog_1183_li
Byte arrays are now sorted in unsigned mode (x'99' is larger than x'09'). (System property "h2.sortBinaryUnsigned", Mode.binaryUnsigned, setting "binary_collation").
Byte arrays are now sorted in unsigned mode (x'99' is larger than x'09'). (System property "h2.sortBinaryUnsigned", Mode.binaryUnsigned, setting "binary_collation").
@changelog_1175_li
@changelog_1184_li
Csv.getInstance will be removed in future versions of 1.4. Use the public constructor instead.
Csv.getInstance will be removed in future versions of 1.4. Use the public constructor instead.
@changelog_1176_li
@changelog_1185_li
Remove support for the limited old-style outer join syntax using "(+)". Use "outer join" instead. System property "h2.oldStyleOuterJoin".
Remove support for the limited old-style outer join syntax using "(+)". Use "outer join" instead. System property "h2.oldStyleOuterJoin".
@changelog_1177_li
@changelog_1186_li
Support the data type "DATETIME2" as an alias for "DATETIME", for MS SQL Server compatibility.
Support the data type "DATETIME2" as an alias for "DATETIME", for MS SQL Server compatibility.
@changelog_1178_li
@changelog_1187_li
Add Oracle-compatible TRANSLATE function, patch by Eric Chatellier.
Add Oracle-compatible TRANSLATE function, patch by Eric Chatellier.
@changelog_1179_h2
@changelog_1188_h2
Version 1.3.176 (2014-04-05)
Version 1.3.176 (2014-04-05)
@changelog_1180_li
@changelog_1189_li
The file locking method 'serialized' is no longer documented, as it will not be available in version 1.4.
The file locking method 'serialized' is no longer documented, as it will not be available in version 1.4.
@changelog_1181_li
@changelog_1190_li
The static method Csv.getInstance() was removed. Use the public constructor instead.
The static method Csv.getInstance() was removed. Use the public constructor instead.
@changelog_1182_li
@changelog_1191_li
The default user name for the Script, RunScript, Shell, and CreateCluster tools are no longer "sa" but an empty string.
The default user name for the Script, RunScript, Shell, and CreateCluster tools are no longer "sa" but an empty string.
@changelog_1183_li
@changelog_1192_li
The stack trace of the exception "The object is already closed" is no longer logged by default.
The stack trace of the exception "The object is already closed" is no longer logged by default.
@changelog_1184_li
@changelog_1193_li
If a value of a result set was itself a result set, the result could only be read once.
If a value of a result set was itself a result set, the result could only be read once.
@changelog_1185_li
@changelog_1194_li
Column constraints are also visible in views (patch from Nicolas Fortin for H2GIS).
Column constraints are also visible in views (patch from Nicolas Fortin for H2GIS).
@changelog_1186_li
@changelog_1195_li
Granting a additional right to a role that already had a right for that table was not working.
Granting a additional right to a role that already had a right for that table was not working.
@changelog_1187_li
@changelog_1196_li
Spatial index: a few bugs have been fixed (using spatial constraints in views, transferring geometry objects over TCP/IP, the returned geometry object is copied when needed).
Spatial index: a few bugs have been fixed (using spatial constraints in views, transferring geometry objects over TCP/IP, the returned geometry object is copied when needed).
@changelog_1188_li
@changelog_1197_li
Issue 551: the datatype documentation was incorrect (found by Bernd Eckenfels).
Issue 551: the datatype documentation was incorrect (found by Bernd Eckenfels).
@changelog_1189_li
@changelog_1198_li
Issue 368: ON DUPLICATE KEY UPDATE did not work for multi-row inserts. Test case from Angus Macdonald.
Issue 368: ON DUPLICATE KEY UPDATE did not work for multi-row inserts. Test case from Angus Macdonald.
@changelog_1190_li
@changelog_1199_li
OSGi: the package javax.tools is now imported (as an optional).
OSGi: the package javax.tools is now imported (as an optional).
@changelog_1191_li
@changelog_1200_li
H2 Console: auto-complete is now disabled by default, but there is a hot-key (Ctrl+Space).
H2 Console: auto-complete is now disabled by default, but there is a hot-key (Ctrl+Space).
@changelog_1192_li
@changelog_1201_li
H2 Console: auto-complete did not work with multi-line statements.
H2 Console: auto-complete did not work with multi-line statements.
@changelog_1193_li
@changelog_1202_li
CLOB and BLOB data was not immediately removed after a rollback.
CLOB and BLOB data was not immediately removed after a rollback.
@changelog_1194_li
@changelog_1203_li
There is a new Aggregate API that supports the internal H2 data types (GEOMETRY for example). Thanks a lot to Nicolas Fortin for the patch!
There is a new Aggregate API that supports the internal H2 data types (GEOMETRY for example). Thanks a lot to Nicolas Fortin for the patch!
@changelog_1195_li
@changelog_1204_li
Referential integrity constraints sometimes used the wrong index, such that updating a row in the referenced table incorrectly failed with a constraint violation.
Referential integrity constraints sometimes used the wrong index, such that updating a row in the referenced table incorrectly failed with a constraint violation.
@changelog_1196_li
@changelog_1205_li
The Polish translation was completed and corrected by Wojtek Jurczyk. Thanks a lot!
The Polish translation was completed and corrected by Wojtek Jurczyk. Thanks a lot!
@changelog_1197_li
@changelog_1206_li
Issue 545: Unnecessary duplicate code was removed.
Issue 545: Unnecessary duplicate code was removed.
@changelog_1198_li
@changelog_1207_li
The profiler tool can now process files with full thread dumps.
The profiler tool can now process files with full thread dumps.
@changelog_1199_li
@changelog_1208_li
MVStore: the file format was changed slightly.
MVStore: the file format was changed slightly.
@changelog_1200_li
@changelog_1209_li
MVStore mode: the CLOB and BLOB storage was re-implemented and is now much faster than with the PageStore (which is still the default storage).
MVStore mode: the CLOB and BLOB storage was re-implemented and is now much faster than with the PageStore (which is still the default storage).
@changelog_1201_li
@changelog_1210_li
MVStore mode: creating indexes is now much faster (in many cases faster than with the default PageStore).
MVStore mode: creating indexes is now much faster (in many cases faster than with the default PageStore).
@changelog_1202_li
@changelog_1211_li
Various bugs in the MVStore storage and have been fixed, including a bug in the R-tree implementation. The database could get corrupt if there were transient IO exceptions while storing.
Various bugs in the MVStore storage and have been fixed, including a bug in the R-tree implementation. The database could get corrupt if there were transient IO exceptions while storing.
@changelog_1203_li
@changelog_1212_li
The method org.h2.expression.Function.getCost could throw a NullPointException.
The method org.h2.expression.Function.getCost could throw a NullPointException.
@changelog_1204_li
@changelog_1213_li
Storing LOBs in separate files (outside of the main database file) is no longer supported for new databases.
Storing LOBs in separate files (outside of the main database file) is no longer supported for new databases.
@changelog_1205_li
@changelog_1214_li
Lucene 2 is no longer supported.
Lucene 2 is no longer supported.
@changelog_1206_li
@changelog_1215_li
Fix bug in calculating default MIN and MAX values for SEQUENCE.
Fix bug in calculating default MIN and MAX values for SEQUENCE.
@changelog_1207_li
@changelog_1216_li
Fix bug in performing IN queries with multiple values when IGNORECASE=TRUE
Fix bug in performing IN queries with multiple values when IGNORECASE=TRUE
@changelog_1208_li
@changelog_1217_li
Add entry-point to org.h2.tools.Shell so it can be called from inside an application. patch by Thomas Gillet.
Add entry-point to org.h2.tools.Shell so it can be called from inside an application. patch by Thomas Gillet.
@changelog_1209_li
@changelog_1218_li
Fix bug that prevented the PgServer from being stopped and started multiple times.
Fix bug that prevented the PgServer from being stopped and started multiple times.
@changelog_1210_li
@changelog_1219_li
Support some more DDL syntax for MySQL, patch from Peter Jentsch.
Support some more DDL syntax for MySQL, patch from Peter Jentsch.
@changelog_1211_li
@changelog_1220_li
Issue 548: TO_CHAR does not format MM and DD correctly when the month or day of the month is 1 digit, patch from "the.tucc"
Issue 548: TO_CHAR does not format MM and DD correctly when the month or day of the month is 1 digit, patch from "the.tucc"
@changelog_1212_li
@changelog_1221_li
Fix bug in varargs support in ALIAS's, patch from Nicolas Fortin
Fix bug in varargs support in ALIAS's, patch from Nicolas Fortin
@cheatSheet_1000_h1
@cheatSheet_1000_h1
...
@@ -2531,7 +2567,7 @@ Using H2
...
@@ -2531,7 +2567,7 @@ Using H2
H2
H2
@cheatSheet_1003_li
@cheatSheet_1003_li
is <a href="http://code.google.com/p/h2database/source">open source</a>, <a href="license.html">free to use and distribute</a>.
is <a href="https://github.com/h2database/h2database">open source</a>, <a href="license.html">free to use and distribute</a>.
For details about changes, see the <a href="changelog.html">Change Log</a>.
For details about changes, see the <a href="changelog.html">Change Log</a>.
...
@@ -2834,7 +2870,7 @@ Some problems have been found with right outer join. Internally, it is converted
...
@@ -2834,7 +2870,7 @@ Some problems have been found with right outer join. Internally, it is converted
When using Install4j before 4.1.4 on Linux and enabling <code>pack200</code>, the <code>h2*.jar</code> becomes corrupted by the install process, causing application failure. A workaround is to add an empty file <code>h2*.jar.nopack</code> next to the <code>h2*.jar</code> file. This problem is solved in Install4j 4.1.4.
When using Install4j before 4.1.4 on Linux and enabling <code>pack200</code>, the <code>h2*.jar</code> becomes corrupted by the install process, causing application failure. A workaround is to add an empty file <code>h2*.jar.nopack</code> next to the <code>h2*.jar</code> file. This problem is solved in Install4j 4.1.4.
@faq_1027_p
@faq_1027_p
For a complete list, see <a href="http://code.google.com/p/h2database/issues/list">Open Issues</a>.
For a complete list, see <a href="https://github.com/h2database/h2database/issues">Open Issues</a>.
@faq_1028_h3
@faq_1028_h3
Is this Database Engine Open Source?
Is this Database Engine Open Source?
...
@@ -3794,7 +3830,7 @@ Footprint (jar/dll size)
...
@@ -3794,7 +3830,7 @@ Footprint (jar/dll size)
*10 Derby and HSQLDB <a href="http://en.wikipedia.org/wiki/Block_cipher_modes_of_operation#Electronic_codebook_.28ECB.29">don't hide data patterns well</a>.
*10 Derby and HSQLDB <a href="http://en.wikipedia.org/wiki/Block_cipher_modes_of_operation#Electronic_codebook_.28ECB.29">don't hide data patterns well</a>.
@features_1260_p
@features_1260_p
*11 The MULTI_THREADED option is not enabled by default, and not yet supported when using MVCC.
*11 The MULTI_THREADED option is not enabled by default, and with version 1.3.x not supported when using MVCC.
@features_1261_p
@features_1261_p
*12 Derby doesn't support the <code>EXPLAIN</code> statement, but it supports runtime statistics and retrieving statement execution plans.
*12 Derby doesn't support the <code>EXPLAIN</code> statement, but it supports runtime statistics and retrieving statement execution plans.
...
@@ -4211,10 +4247,10 @@ Multiple Connections to the Same Database: Client/Server
...
@@ -4211,10 +4247,10 @@ Multiple Connections to the Same Database: Client/Server
Multithreading Support
Multithreading Support
@features_1399_p
@features_1399_p
This database is multithreading-safe. That means, if an application is multi-threaded, it does not need to worry about synchronizing access to the database. Internally, most requests to the same database are synchronized. That means an application can use multiple threads that access the same database at the same time, however if one thread executes a long running query, the other threads need to wait.
This database is multithreading-safe. If an application is multi-threaded, it does not need to worry about synchronizing access to the database. An application should normally use one connection per thread. This database synchronizes access to the same connection, but other databases may not do this. To get higher concurrency, you need to use multiple connections.
@features_1400_p
@features_1400_p
An application should normally use one connection per thread. This database synchronizes access to the same connection, but other databases may not do this.
By default, requests to the same database are synchronized. That means an application can use multiple threads that access the same database at the same time, however if one thread executes a long running query, the other threads need to wait. To enable concurrent database usage, see the setting <code>MULTI_THREADED</code>.
@features_1401_h3
@features_1401_h3
Locking, Lock-Timeout, Deadlocks
Locking, Lock-Timeout, Deadlocks
...
@@ -4685,7 +4721,7 @@ Read Only Databases in Zip or Jar File
...
@@ -4685,7 +4721,7 @@ Read Only Databases in Zip or Jar File
Databases in zip files are read-only. The performance for some queries will be slower than when using a regular database, because random access in zip files is not supported (only streaming). How much this affects the performance depends on the queries and the data. The database is not read in memory; therefore large databases are supported as well. The same indexes are used as when using a regular database.
Databases in zip files are read-only. The performance for some queries will be slower than when using a regular database, because random access in zip files is not supported (only streaming). How much this affects the performance depends on the queries and the data. The database is not read in memory; therefore large databases are supported as well. The same indexes are used as when using a regular database.
@features_1557_p
@features_1557_p
If the database is larger than a few megabytes, performance is much better if the database file is split into multiple smaller files, because random access in compressed files is not possible. See also the sample application <a href="http://code.google.com/p/h2database/source/browse/trunk/h2/src/test/org/h2/samples/ReadOnlyDatabaseInZip.java">ReadOnlyDatabaseInZip</a>.
If the database is larger than a few megabytes, performance is much better if the database file is split into multiple smaller files, because random access in compressed files is not possible. See also the sample application <a href="https://github.com/h2database/h2database/tree/master/h2/src/test/org/h2/samples/ReadOnlyDatabaseInZip.java">ReadOnlyDatabaseInZip</a>.
@features_1558_h3
@features_1558_h3
Opening a Corrupted Database
Opening a Corrupted Database
...
@@ -10816,19 +10852,16 @@ Issue 390: RUNSCRIPT FROM '...' CONTINUE_ON_ERROR
...
@@ -10816,19 +10852,16 @@ Issue 390: RUNSCRIPT FROM '...' CONTINUE_ON_ERROR
@roadmap_1509_li
@roadmap_1509_li
Use Java 6 exceptions: SQLDataException, SQLSyntaxErrorException, SQLTimeoutException,..
Use Java 6 exceptions: SQLDataException, SQLSyntaxErrorException, SQLTimeoutException,..
@roadmap_1510_li
@roadmap_1510_h2
Support index-only when doing selects (i.e. without needing to load the actual table data)
@roadmap_1511_h2
Not Planned
Not Planned
@roadmap_1512_li
@roadmap_1511_li
HSQLDB (did) support this: select id i from test where i<0 (other databases don't). Supporting it may break compatibility.
HSQLDB (did) support this: select id i from test where i<0 (other databases don't). Supporting it may break compatibility.
@roadmap_1513_li
@roadmap_1512_li
String.intern (so that Strings can be compared with ==) will not be used because some VMs have problems when used extensively.
String.intern (so that Strings can be compared with ==) will not be used because some VMs have problems when used extensively.
@roadmap_1514_li
@roadmap_1513_li
In prepared statements, identifier names (table names and so on) can not be parameterized. Adding such a feature would complicate the source code without providing reasonable speedup, and would slow down regular prepared statements.
In prepared statements, identifier names (table names and so on) can not be parameterized. Adding such a feature would complicate the source code without providing reasonable speedup, and would slow down regular prepared statements.
#In Eclipse, create a new Java project from existing source code: <code>File, New, Project, Java Project, Create project from existing source</code>.
#In Eclipse, create a new Java project from existing source code: <code>File, New, Project, Java Project, Create project from existing source</code>.
@build_1065_li
@build_1068_li
#Select the <code>h2</code> folder, click <code>Next</code> and <code>Finish</code>.
#Select the <code>h2</code> folder, click <code>Next</code> and <code>Finish</code>.
@build_1066_li
@build_1069_li
#To resolve <code>com.sun.javadoc</code> import statements, you may need to manually add the file <code><java.home>/../lib/tools.jar</code> to the build path.
#To resolve <code>com.sun.javadoc</code> import statements, you may need to manually add the file <code><java.home>/../lib/tools.jar</code> to the build path.
@build_1067_h2
@build_1070_h2
#Translating
#Translating
@build_1068_p
@build_1071_p
# The translation of this software is split into the following parts:
# 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.
# 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_1072_h2
@build_1075_h2
#Providing Patches
#Providing Patches
@build_1073_p
@build_1076_p
# If you like to provide patches, please consider the following guidelines to simplify merging them:
# If you like to provide patches, please consider the following guidelines to simplify merging them:
@build_1074_li
@build_1077_li
#Only use Java 6 features (do not use Java 7) (see <a href="#environment">Environment</a>).
#Only use Java 6 features (do not use Java 7) (see <a href="#environment">Environment</a>).
@build_1075_li
@build_1078_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>.
#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_1076_li
@build_1079_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.
#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_1077_li
@build_1080_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>.
#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_1078_li
@build_1081_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>.
#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_1079_li
@build_1082_li
#Verify that you did not break other features: run the test cases by executing <code>build test</code>.
#Verify that you did not break other features: run the test cases by executing <code>build test</code>.
@build_1080_li
@build_1083_li
#Provide end user documentation if required (<code>src/docsrc/html/*</code>).
#Provide end user documentation if required (<code>src/docsrc/html/*</code>).
@build_1081_li
@build_1084_li
#Document grammar changes in <code>src/docsrc/help/help.csv</code>
#Document grammar changes in <code>src/docsrc/help/help.csv</code>
@build_1082_li
@build_1085_li
#Provide a change log entry (<code>src/docsrc/html/changelog.html</code>).
#Provide a change log entry (<code>src/docsrc/html/changelog.html</code>).
@build_1083_li
@build_1086_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>.
#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_1084_li
@build_1087_li
#Run <code>src/installer/buildRelease</code> to find and fix formatting errors.
#Run <code>src/installer/buildRelease</code> to find and fix formatting errors.
@build_1085_li
@build_1088_li
#Verify the formatting using <code>build docs</code> and <code>build javadoc</code>.
#Verify the formatting using <code>build docs</code> and <code>build javadoc</code>.
@build_1086_li
@build_1089_li
#Submit patches as <code>.patch</code> files (compressed if big). To create a patch using Eclipse, use Team / Create Patch.
#Submit patches as <code>.patch</code> files (compressed if big). To create a patch using Eclipse, use Team / Create Patch.
@build_1087_p
@build_1090_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:
# 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="https://github.com/h2database/h2database/issues">issue report or attachment</a>. Significant contributions need to include the following statement:
@build_1088_p
@build_1091_p
# "I wrote the code, it's mine, and I'm contributing it to H2 for distribution multiple-licensed under the MPL 2.0, and the EPL 1.0 (http://h2database.com/html/license.html)."
# "I wrote the code, it's mine, and I'm contributing it to H2 for distribution multiple-licensed under the MPL 2.0, and the EPL 1.0 (http://h2database.com/html/license.html)."
@build_1089_h2
@build_1092_h2
#Reporting Problems or Requests
#Reporting Problems or Requests
@build_1090_p
@build_1093_p
# Please consider the following checklist if you have a question, want to report a problem, or if you have a feature request:
# Please consider the following checklist if you have a question, want to report a problem, or if you have a feature request:
@build_1091_li
@build_1094_li
#For bug reports, please provide a <a href="http://sscce.org/">short, self contained, correct (compilable), example</a> of the problem.
#For bug reports, please provide a <a href="http://sscce.org/">short, self contained, correct (compilable), example</a> of the problem.
@build_1092_li
@build_1095_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>.
#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_1093_li
@build_1096_li
#Before posting problems, check the <a href="faq.html">FAQ</a> and do a <a href="http://google.com">Google search</a>.
#Before posting problems, check the <a href="faq.html">FAQ</a> and do a <a href="http://google.com">Google search</a>.
@build_1094_li
@build_1097_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).
#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_1095_li
@build_1098_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.
#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="https://github.com/h2database/h2database/tree/master/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_1096_li
@build_1099_li
#For large attachments, use a public temporary storage such as <a href="http://rapidshare.com">Rapidshare</a>.
#For large attachments, use a public temporary storage such as <a href="http://rapidshare.com">Rapidshare</a>.
@build_1097_li
@build_1100_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.
#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="https://github.com/h2database/h2database/issues">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_1098_li
@build_1101_li
#For out-of-memory problems, please analyze the problem yourself first, for example using the command line option <code>-XX:+HeapDumpOnOutOfMemoryError</code> (to create a heap dump file on out of memory) and a memory analysis tool such as the <a href="http://www.eclipse.org/mat">Eclipse Memory Analyzer (MAT)</a>.
#For out-of-memory problems, please analyze the problem yourself first, for example using the command line option <code>-XX:+HeapDumpOnOutOfMemoryError</code> (to create a heap dump file on out of memory) and a memory analysis tool such as the <a href="http://www.eclipse.org/mat">Eclipse Memory Analyzer (MAT)</a>.
@build_1099_li
@build_1102_li
#It may take a few days to get an answers. Please do not double post.
#It may take a few days to get an answers. Please do not double post.
@build_1100_h2
@build_1103_h2
#Automated Build
#Automated Build
@build_1101_p
@build_1104_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:
# 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_1102_a
@build_1105_a
#Test Output
#Test Output
@build_1103_a
@build_1106_a
#Code Coverage Summary
#Code Coverage Summary
@build_1104_a
@build_1107_a
#Code Coverage Details (download, 1.3 MB)
#Code Coverage Details (download, 1.3 MB)
@build_1105_a
@build_1108_a
#Build Newsfeed
#Build Newsfeed
@build_1106_a
@build_1109_a
#Latest Jar File (download, 1 MB)
#Latest Jar File (download, 1 MB)
@build_1107_h2
@build_1110_h2
#Generating Railroad Diagrams
#Generating Railroad Diagrams
@build_1108_p
@build_1111_p
# The railroad diagrams of the <a href="grammar.html">SQL grammar</a> are HTML, formatted as nested tables. The diagrams are generated as follows:
# The railroad diagrams of the <a href="grammar.html">SQL grammar</a> are HTML, formatted as nested tables. The diagrams are generated as follows:
@build_1109_li
@build_1112_li
#The BNF parser (<code>org.h2.bnf.Bnf</code>) reads and parses the BNF from the file <code>help.csv</code>.
#The BNF parser (<code>org.h2.bnf.Bnf</code>) reads and parses the BNF from the file <code>help.csv</code>.
@build_1110_li
@build_1113_li
#The page parser (<code>org.h2.server.web.PageParser</code>) reads the template HTML file and fills in the diagrams.
#The page parser (<code>org.h2.server.web.PageParser</code>) reads the template HTML file and fills in the diagrams.
@build_1111_li
@build_1114_li
#The rail images (one straight, four junctions, two turns) are generated using a simple Java application.
#The rail images (one straight, four junctions, two turns) are generated using a simple Java application.
@build_1112_p
@build_1115_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.
# 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
@changelog_1000_h1
...
@@ -1889,636 +1898,663 @@ Centralリ�?ジトリ�?�利用
...
@@ -1889,636 +1898,663 @@ Centralリ�?ジトリ�?�利用
#Next Version (unreleased)
#Next Version (unreleased)
@changelog_1002_li
@changelog_1002_li
#-
#Granting a schema is now supported.
@changelog_1003_h2
@changelog_1003_li
#Version 1.4.187 Beta (2015-04-10)
#Linked tables did not work when a function-based index is present (Oracle).
@changelog_1004_li
@changelog_1004_li
#MVStore: concurrent changes to the same row could result in the exception "The transaction log might be corrupt for key ...". This could only be reproduced with 3 or more threads.
#Creating a user with a null password, salt, or hash threw a NullPointerException.
@changelog_1005_li
@changelog_1005_li
#Results with CLOB or BLOB data are no longer reused.
#Foreign key: don't add a single column index if column is leading key of existing index.
@changelog_1006_li
@changelog_1006_li
#References to BLOB and CLOB objects now have a timeout. The configuration setting is LOB_TIMEOUT (default 5 minutes). This should avoid growing the database file if there are many queries that return BLOB or CLOB objects, and the database is not closed for a longer time.
#Pull request #4: Creating and removing temporary tables was getting slower and slower over time, because an internal object id was allocated but never de-allocated.
@changelog_1007_li
@changelog_1007_li
#MVStore: when committing a session that removed LOB values, changes were flushed unnecessarily.
#Issue 609: the spatial index did not support NULL with update and delete operations.
@changelog_1008_li
@changelog_1008_li
#Issue 610: possible integer overflow in WriteBuffer.grow().
#Pull request #2: Add external metadata type support (table type "external")
@changelog_1009_li
@changelog_1009_li
#Issue 609: the spatial index did not support NULL (ClassCastException).
#MS SQL Server: the CONVERT method did not work in views and derived tables.
@changelog_1010_li
@changelog_1010_li
#MVStore: in some cases, CLOB/BLOB data blocks were removed incorrectly when opening a database.
#Java 8 compatibility for "regexp_replace".
@changelog_1011_li
@changelog_1011_li
#When in cluster mode, and one of the nodes goes down, we need to log the problem with priority "error", not "debug"
@changelog_1012_h2
#Version 1.4.187 Beta (2015-04-10)
@changelog_1013_li
#MVStore: concurrent changes to the same row could result in the exception "The transaction log might be corrupt for key ...". This could only be reproduced with 3 or more threads.
@changelog_1014_li
#Results with CLOB or BLOB data are no longer reused.
@changelog_1015_li
#References to BLOB and CLOB objects now have a timeout. The configuration setting is LOB_TIMEOUT (default 5 minutes). This should avoid growing the database file if there are many queries that return BLOB or CLOB objects, and the database is not closed for a longer time.
@changelog_1016_li
#MVStore: when committing a session that removed LOB values, changes were flushed unnecessarily.
@changelog_1017_li
#Issue 610: possible integer overflow in WriteBuffer.grow().
@changelog_1018_li
#Issue 609: the spatial index did not support NULL (ClassCastException).
@changelog_1019_li
#MVStore: in some cases, CLOB/BLOB data blocks were removed incorrectly when opening a database.
@changelog_1020_li
#MVStore: updates that affected many rows were were slow in some cases if there was a secondary index.
#MVStore: updates that affected many rows were were slow in some cases if there was a secondary index.
@changelog_1012_li
@changelog_1021_li
#Using "runscript" with autocommit disabled could result in a lock timeout on the internal table "SYS".
#Using "runscript" with autocommit disabled could result in a lock timeout on the internal table "SYS".
@changelog_1013_li
@changelog_1022_li
#Issue 603: there was a memory leak when using H2 in a web application. Apache Tomcat logged an error message: "The web application ... created a ThreadLocal with key of type [org.h2.util.DateTimeUtils$1]".
#Issue 603: there was a memory leak when using H2 in a web application. Apache Tomcat logged an error message: "The web application ... created a ThreadLocal with key of type [org.h2.util.DateTimeUtils$1]".
@changelog_1014_li
@changelog_1023_li
#When using the MVStore, running a SQL script generate by the Recover tool from a PageStore file failed with a strange error message (NullPointerException), now a clear error message is shown.
#When using the MVStore, running a SQL script generate by the Recover tool from a PageStore file failed with a strange error message (NullPointerException), now a clear error message is shown.
@changelog_1015_li
@changelog_1024_li
#Issue 605: with version 1.4.186, opening a database could result in an endless loop in LobStorageMap.init.
#Issue 605: with version 1.4.186, opening a database could result in an endless loop in LobStorageMap.init.
@changelog_1016_li
@changelog_1025_li
#Queries that use the same table alias multiple times now work. Before, the select expression list was expanded incorrectly. Example: "select * from a as x, b as x".
#Queries that use the same table alias multiple times now work. Before, the select expression list was expanded incorrectly. Example: "select * from a as x, b as x".
@changelog_1017_li
@changelog_1026_li
#The MySQL compatibility feature "insert ... on duplicate key update" did not work with a non-default schema.
#The MySQL compatibility feature "insert ... on duplicate key update" did not work with a non-default schema.
@changelog_1018_li
@changelog_1027_li
#Issue 599: the condition "in(x, y)" could not be used in the select list when using "group by".
#Issue 599: the condition "in(x, y)" could not be used in the select list when using "group by".
@changelog_1019_li
@changelog_1028_li
#The LIRS cache could grow larger than the allocated memory.
#The LIRS cache could grow larger than the allocated memory.
@changelog_1020_li
@changelog_1029_li
#A new file system implementation that re-opens the file if it was closed due to the application calling Thread.interrupt(). File name prefix "retry:". Please note it is strongly recommended to avoid calling Thread.interrupt; this is a problem for various libraries, including Apache Lucene.
#A new file system implementation that re-opens the file if it was closed due to the application calling Thread.interrupt(). File name prefix "retry:". Please note it is strongly recommended to avoid calling Thread.interrupt; this is a problem for various libraries, including Apache Lucene.
@changelog_1021_li
@changelog_1030_li
#MVStore: use RandomAccessFile file system if the file name starts with "file:".
#MVStore: use RandomAccessFile file system if the file name starts with "file:".
@changelog_1022_li
@changelog_1031_li
#Allow DATEADD to take a long value for count when manipulating milliseconds.
#Allow DATEADD to take a long value for count when manipulating milliseconds.
@changelog_1023_li
@changelog_1032_li
#When using MV_STORE=TRUE and the SET CACHE_SIZE setting, the cache size was incorrectly set, so that it was effectively 1024 times smaller than it should be.
#When using MV_STORE=TRUE and the SET CACHE_SIZE setting, the cache size was incorrectly set, so that it was effectively 1024 times smaller than it should be.
@changelog_1024_li
@changelog_1033_li
#Concurrent CREATE TABLE... IF NOT EXISTS in the presence of MULTI_THREAD=TRUE could throw an exception.
#Concurrent CREATE TABLE... IF NOT EXISTS in the presence of MULTI_THREAD=TRUE could throw an exception.
@changelog_1025_li
@changelog_1034_li
#Fix bug in MVStore when creating lots of temporary tables, where we could run out of transaction IDs.
#Fix bug in MVStore when creating lots of temporary tables, where we could run out of transaction IDs.
@changelog_1026_li
@changelog_1035_li
#Add support for PostgreSQL STRING_AGG function. Patch by Fred Aquiles.
#Add support for PostgreSQL STRING_AGG function. Patch by Fred Aquiles.
@changelog_1027_li
@changelog_1036_li
#Fix bug in "jdbc:h2:nioMemFS" isRoot() function. Also, the page size was increased to 64 KB.
#Fix bug in "jdbc:h2:nioMemFS" isRoot() function. Also, the page size was increased to 64 KB.
@changelog_1028_h2
@changelog_1037_h2
#Version 1.4.186 Beta (2015-03-02)
#Version 1.4.186 Beta (2015-03-02)
@changelog_1029_li
@changelog_1038_li
#The Servlet API 3.0.1 is now used, instead of 2.4.
#The Servlet API 3.0.1 is now used, instead of 2.4.
@changelog_1030_li
@changelog_1039_li
#MVStore: old chunks no longer removed in append-only mode.
#MVStore: old chunks no longer removed in append-only mode.
@changelog_1031_li
@changelog_1040_li
#MVStore: the cache for page references could grow far too big, resulting in out of memory in some cases.
#MVStore: the cache for page references could grow far too big, resulting in out of memory in some cases.
@changelog_1032_li
@changelog_1041_li
#MVStore: orphaned lob objects were not correctly removed in some cases, making the database grow unnecessarily.
#MVStore: orphaned lob objects were not correctly removed in some cases, making the database grow unnecessarily.
@changelog_1033_li
@changelog_1042_li
#MVStore: the maximum cache size was artificially limited to 2 GB (due to an integer overflow).
#MVStore: the maximum cache size was artificially limited to 2 GB (due to an integer overflow).
@changelog_1034_li
@changelog_1043_li
#MVStore / TransactionStore: concurrent updates could result in a "Too many open transactions" exception.
#MVStore / TransactionStore: concurrent updates could result in a "Too many open transactions" exception.
@changelog_1035_li
@changelog_1044_li
#StringUtils.toUpperEnglish now has a small cache. This should speed up reading from a ResultSet when using the column name.
#StringUtils.toUpperEnglish now has a small cache. This should speed up reading from a ResultSet when using the column name.
@changelog_1036_li
@changelog_1045_li
#MVStore: up to 65535 open transactions are now supported. Previously, the limit was at most 65535 transactions between the oldest open and the newest open transaction (which was quite a strange limit).
#MVStore: up to 65535 open transactions are now supported. Previously, the limit was at most 65535 transactions between the oldest open and the newest open transaction (which was quite a strange limit).
@changelog_1037_li
@changelog_1046_li
#The default limit for in-place LOB objects was changed from 128 to 256 bytes. This is because each read creates a reference to a LOB, and maintaining the references is a big overhead. With the higher limit, less references are needed.
#The default limit for in-place LOB objects was changed from 128 to 256 bytes. This is because each read creates a reference to a LOB, and maintaining the references is a big overhead. With the higher limit, less references are needed.
@changelog_1038_li
@changelog_1047_li
#Tables without columns didn't work. (The use case for such tables is testing.)
#Tables without columns didn't work. (The use case for such tables is testing.)
@changelog_1039_li
@changelog_1048_li
#The LIRS cache now resizes the table automatically in all cases and no longer needs the averageMemory configuration.
#The LIRS cache now resizes the table automatically in all cases and no longer needs the averageMemory configuration.
@changelog_1040_li
@changelog_1049_li
#Creating a linked table from an MVStore database to a non-MVStore database created a second (non-MVStore) database file.
#Creating a linked table from an MVStore database to a non-MVStore database created a second (non-MVStore) database file.
@changelog_1041_li
@changelog_1050_li
#In version 1.4.184, a bug was introduced that broke queries that have both joins and wildcards, for example: select * from dual join(select x from dual) on 1=1
#In version 1.4.184, a bug was introduced that broke queries that have both joins and wildcards, for example: select * from dual join(select x from dual) on 1=1
@changelog_1042_li
@changelog_1051_li
#Issue 598: parser fails on timestamp "24:00:00.1234" - prevent the creation of out-of-range time values.
#Issue 598: parser fails on timestamp "24:00:00.1234" - prevent the creation of out-of-range time values.
@changelog_1043_li
@changelog_1052_li
#Allow declaring triggers as source code (like functions). Patch by Sylvain Cuaz.
#Allow declaring triggers as source code (like functions). Patch by Sylvain Cuaz.
@changelog_1044_li
@changelog_1053_li
#Make the planner use indexes for sorting when doing a GROUP BY where all of the GROUP BY columns are not mentioned in the select. Patch by Frederico (zepfred).
#Make the planner use indexes for sorting when doing a GROUP BY where all of the GROUP BY columns are not mentioned in the select. Patch by Frederico (zepfred).
@changelog_1045_li
@changelog_1054_li
#PostgreSQL compatibility: generate_series (as an alias for system_range). Patch by litailang.
#PostgreSQL compatibility: generate_series (as an alias for system_range). Patch by litailang.
@changelog_1046_li
@changelog_1055_li
#Fix missing "column" type in right-hand parameter in ConditionIn. Patch by Arnaud Thimel.
#Fix missing "column" type in right-hand parameter in ConditionIn. Patch by Arnaud Thimel.
@changelog_1047_h2
@changelog_1056_h2
#Version 1.4.185 Beta (2015-01-16)
#Version 1.4.185 Beta (2015-01-16)
@changelog_1048_li
@changelog_1057_li
#In version 1.4.184, "group by" ignored the table name, and could pick a select column by mistake. Example: select 0 as x from system_range(1, 2) d group by d.x;
#In version 1.4.184, "group by" ignored the table name, and could pick a select column by mistake. Example: select 0 as x from system_range(1, 2) d group by d.x;
@changelog_1049_li
@changelog_1058_li
#New connection setting "REUSE_SPACE" (default: true). If disabled, all changes are appended to the database file, and existing content is never overwritten. This allows to rollback to a previous state of the database by truncating the database file.
#New connection setting "REUSE_SPACE" (default: true). If disabled, all changes are appended to the database file, and existing content is never overwritten. This allows to rollback to a previous state of the database by truncating the database file.
@changelog_1050_li
@changelog_1059_li
#Issue 587: MVStore: concurrent compaction and store operations could result in an IllegalStateException.
#Issue 587: MVStore: concurrent compaction and store operations could result in an IllegalStateException.
@changelog_1051_li
@changelog_1060_li
#Issue 594: Profiler.copyInThread does not work properly.
#Issue 594: Profiler.copyInThread does not work properly.
@changelog_1052_li
@changelog_1061_li
#Script tool: Now, SCRIPT ... TO is always used (for higher speed and lower disk space usage).
#Script tool: Now, SCRIPT ... TO is always used (for higher speed and lower disk space usage).
@changelog_1053_li
@changelog_1062_li
#Script tool: Fix parsing of BLOCKSIZE parameter, original patch by Ken Jorissen.
#Script tool: Fix parsing of BLOCKSIZE parameter, original patch by Ken Jorissen.
@changelog_1054_li
@changelog_1063_li
#Fix bug in PageStore#commit method - when the ignoreBigLog flag was set, the logic that cleared the flag could never be reached, resulting in performance degradation. Reported by Alexander Nesterov.
#Fix bug in PageStore#commit method - when the ignoreBigLog flag was set, the logic that cleared the flag could never be reached, resulting in performance degradation. Reported by Alexander Nesterov.
@changelog_1055_li
@changelog_1064_li
#Issue 552: Implement BIT_AND and BIT_OR aggregate functions.
#Issue 552: Implement BIT_AND and BIT_OR aggregate functions.
@changelog_1056_h2
@changelog_1065_h2
#Version 1.4.184 Beta (2014-12-19)
#Version 1.4.184 Beta (2014-12-19)
@changelog_1057_li
@changelog_1066_li
#In version 1.3.183, indexes were not used if the table contains columns with a default value generated by a sequence. This includes tables with identity and auto-increment columns. This bug was introduced by supporting "rownum" in views and derived tables.
#In version 1.3.183, indexes were not used if the table contains columns with a default value generated by a sequence. This includes tables with identity and auto-increment columns. This bug was introduced by supporting "rownum" in views and derived tables.
@changelog_1058_li
@changelog_1067_li
#MVStore: imported BLOB and CLOB data sometimes disappeared. This was caused by a bug in the ObjectDataType comparison.
#MVStore: imported BLOB and CLOB data sometimes disappeared. This was caused by a bug in the ObjectDataType comparison.
@changelog_1059_li
@changelog_1068_li
#Reading from a StreamStore now throws an IOException if the underlying data doesn't exist.
#Reading from a StreamStore now throws an IOException if the underlying data doesn't exist.
@changelog_1060_li
@changelog_1069_li
#MVStore: if there is an exception while saving, the store is now in all cases immediately closed.
#MVStore: if there is an exception while saving, the store is now in all cases immediately closed.
@changelog_1061_li
@changelog_1070_li
#MVStore: the dump tool could go into an endless loop for some files.
#MVStore: the dump tool could go into an endless loop for some files.
@changelog_1062_li
@changelog_1071_li
#MVStore: recovery for a database with many CLOB or BLOB entries is now much faster.
#MVStore: recovery for a database with many CLOB or BLOB entries is now much faster.
@changelog_1063_li
@changelog_1072_li
#Group by with a quoted select column name alias didn't work. Example: select 1 "a" from dual group by "a"
#Group by with a quoted select column name alias didn't work. Example: select 1 "a" from dual group by "a"
@changelog_1064_li
@changelog_1073_li
#Auto-server mode: the host name is now stored in the .lock.db file.
#Auto-server mode: the host name is now stored in the .lock.db file.
@changelog_1065_h2
@changelog_1074_h2
#Version 1.4.183 Beta (2014-12-13)
#Version 1.4.183 Beta (2014-12-13)
@changelog_1066_li
@changelog_1075_li
#MVStore: the default auto-commit buffer size is now about twice as big. This should reduce the database file size after inserting a lot of data.
#MVStore: the default auto-commit buffer size is now about twice as big. This should reduce the database file size after inserting a lot of data.
@changelog_1067_li
@changelog_1076_li
#The built-in functions "power" and "radians" now always return a double.
#The built-in functions "power" and "radians" now always return a double.
@changelog_1068_li
@changelog_1077_li
#Using "row_number" or "rownum" in views or derived tables had unexpected results if the outer query contained constraints for the given view. Example: select b.nr, b.id from (select row_number() over() as nr, a.id as id from (select id from test order by name) as a) as b where b.id = 1
#Using "row_number" or "rownum" in views or derived tables had unexpected results if the outer query contained constraints for the given view. Example: select b.nr, b.id from (select row_number() over() as nr, a.id as id from (select id from test order by name) as a) as b where b.id = 1
@changelog_1069_li
@changelog_1078_li
#MVStore: the Recover tool can now deal with more types of corruption in the file.
#MVStore: the Recover tool can now deal with more types of corruption in the file.
@changelog_1070_li
@changelog_1079_li
#MVStore: the TransactionStore now first needs to be initialized before it can be used.
#MVStore: the TransactionStore now first needs to be initialized before it can be used.
@changelog_1071_li
@changelog_1080_li
#Views and derived tables with equality and range conditions on the same columns did not work properly. example: select x from (select x from (select 1 as x) where x > 0 and x < 2) where x = 1
#Views and derived tables with equality and range conditions on the same columns did not work properly. example: select x from (select x from (select 1 as x) where x > 0 and x < 2) where x = 1
@changelog_1072_li
@changelog_1081_li
#The database URL setting PAGE_SIZE setting is now also used for the MVStore.
#The database URL setting PAGE_SIZE setting is now also used for the MVStore.
@changelog_1073_li
@changelog_1082_li
#MVStore: the default page split size for persistent stores is now 4096 (it was 16 KB so far). This should reduce the database file size for most situations (in some cases, less than half the size of the previous version).
#MVStore: the default page split size for persistent stores is now 4096 (it was 16 KB so far). This should reduce the database file size for most situations (in some cases, less than half the size of the previous version).
@changelog_1074_li
@changelog_1083_li
#With query literals disabled, auto-analyze of a table with CLOB or BLOB did not work.
#With query literals disabled, auto-analyze of a table with CLOB or BLOB did not work.
@changelog_1075_li
@changelog_1084_li
#MVStore: use a mark and sweep GC algorithm instead of reference counting, to ensure used chunks are never overwrite, even if the reference counting algorithm does not work properly.
#MVStore: use a mark and sweep GC algorithm instead of reference counting, to ensure used chunks are never overwrite, even if the reference counting algorithm does not work properly.
@changelog_1076_li
@changelog_1085_li
#In the multi-threaded mode, updating the column selectivity ("analyze") in the background sometimes did not work.
#In the multi-threaded mode, updating the column selectivity ("analyze") in the background sometimes did not work.
@changelog_1077_li
@changelog_1086_li
#In the multi-threaded mode, database metadata operations did sometimes not work if the schema was changed at the same time (for example, if tables were dropped).
#In the multi-threaded mode, database metadata operations did sometimes not work if the schema was changed at the same time (for example, if tables were dropped).
@changelog_1078_li
@changelog_1087_li
#Some CLOB and BLOB values could no longer be read when the original row was removed (even when using the MVCC mode).
#Some CLOB and BLOB values could no longer be read when the original row was removed (even when using the MVCC mode).
@changelog_1079_li
@changelog_1088_li
#The MVStoreTool could throw an IllegalArgumentException.
#The MVStoreTool could throw an IllegalArgumentException.
@changelog_1080_li
@changelog_1089_li
#Improved performance for some date / time / timestamp conversion operations. Thanks to Sergey Evdokimov for reporting the problem.
#Improved performance for some date / time / timestamp conversion operations. Thanks to Sergey Evdokimov for reporting the problem.
@changelog_1081_li
@changelog_1090_li
#H2 Console: the built-in web server did not work properly if an unknown file was requested.
#H2 Console: the built-in web server did not work properly if an unknown file was requested.
@changelog_1082_li
@changelog_1091_li
#MVStore: the jar file is renamed to "h2-mvstore-*.jar" and is deployed to Maven separately.
#MVStore: the jar file is renamed to "h2-mvstore-*.jar" and is deployed to Maven separately.
@changelog_1083_li
@changelog_1092_li
#MVStore: support for concurrent reads and writes is now enabled by default.
#MVStore: support for concurrent reads and writes is now enabled by default.
@changelog_1084_li
@changelog_1093_li
#Server mode: the transfer buffer size has been changed from 16 KB to 64 KB, after it was found that this improves performance on Linux quite a lot.
#Server mode: the transfer buffer size has been changed from 16 KB to 64 KB, after it was found that this improves performance on Linux quite a lot.
@changelog_1085_li
@changelog_1094_li
#H2 Console and server mode: SSL is now disabled and TLS is used to protect against the Poodle SSLv3 vulnerability. The system property to disable secure anonymous connections is now "h2.enableAnonymousTLS". The default certificate is still self-signed, so you need to manually install another one if you want to avoid man in the middle attacks.
#H2 Console and server mode: SSL is now disabled and TLS is used to protect against the Poodle SSLv3 vulnerability. The system property to disable secure anonymous connections is now "h2.enableAnonymousTLS". The default certificate is still self-signed, so you need to manually install another one if you want to avoid man in the middle attacks.
@changelog_1086_li
@changelog_1095_li
#MVStore: the R-tree did not correctly measure the memory usage.
#MVStore: the R-tree did not correctly measure the memory usage.
@changelog_1087_li
@changelog_1096_li
#MVStore: compacting a store with an R-tree did not always work.
#MVStore: compacting a store with an R-tree did not always work.
@changelog_1088_li
@changelog_1097_li
#Issue 581: When running in LOCK_MODE=0, JdbcDatabaseMetaData#supportsTransactionIsolationLevel(TRANSACTION_READ_UNCOMMITTED) should return false
#Issue 581: When running in LOCK_MODE=0, JdbcDatabaseMetaData#supportsTransactionIsolationLevel(TRANSACTION_READ_UNCOMMITTED) should return false
@changelog_1089_li
@changelog_1098_li
#Fix bug which could generate deadlocks when multiple connections accessed the same table.
#Fix bug which could generate deadlocks when multiple connections accessed the same table.
@changelog_1090_li
@changelog_1099_li
#Some places in the code were not respecting the value set in the "SET MAX_MEMORY_ROWS x" command
#Some places in the code were not respecting the value set in the "SET MAX_MEMORY_ROWS x" command
@changelog_1091_li
@changelog_1100_li
#Fix bug which could generate a NegativeArraySizeException when performing large (>40M) row union operations
#Fix bug which could generate a NegativeArraySizeException when performing large (>40M) row union operations
@changelog_1092_li
@changelog_1101_li
#Fix "USE schema" command for MySQL compatibility, patch by mfulton
#Fix "USE schema" command for MySQL compatibility, patch by mfulton
@changelog_1093_li
@changelog_1102_li
#Parse and ignore the ROW_FORMAT=DYNAMIC MySQL syntax, patch by mfulton
#Parse and ignore the ROW_FORMAT=DYNAMIC MySQL syntax, patch by mfulton
@changelog_1094_h2
@changelog_1103_h2
#Version 1.4.182 Beta (2014-10-17)
#Version 1.4.182 Beta (2014-10-17)
@changelog_1095_li
@changelog_1104_li
#MVStore: improved error messages and logging; improved behavior if there is an error when serializing objects.
#MVStore: improved error messages and logging; improved behavior if there is an error when serializing objects.
@changelog_1096_li
@changelog_1105_li
#OSGi: the MVStore packages are now exported.
#OSGi: the MVStore packages are now exported.
@changelog_1097_li
@changelog_1106_li
#With the MVStore option, when using multiple threads that concurrently create indexes or tables, it was relatively easy to get a lock timeout on the "SYS" table.
#With the MVStore option, when using multiple threads that concurrently create indexes or tables, it was relatively easy to get a lock timeout on the "SYS" table.
@changelog_1098_li
@changelog_1107_li
#When using the multi-threaded option, the exception "Unexpected code path" could be thrown, specially if the option "analyze_auto" was set to a low value.
#When using the multi-threaded option, the exception "Unexpected code path" could be thrown, specially if the option "analyze_auto" was set to a low value.
@changelog_1099_li
@changelog_1108_li
#In the server mode, when reading from a CLOB or BLOB, if the connection was closed, a NullPointerException could be thrown instead of an exception saying the connection is closed.
#In the server mode, when reading from a CLOB or BLOB, if the connection was closed, a NullPointerException could be thrown instead of an exception saying the connection is closed.
@changelog_1100_li
@changelog_1109_li
#DatabaseMetaData.getProcedures and getProcedureColumns could throw an exception if a user defined class is not available.
#DatabaseMetaData.getProcedures and getProcedureColumns could throw an exception if a user defined class is not available.
@changelog_1101_li
@changelog_1110_li
#Issue 584: the error message for a wrong sequence definition was wrong.
#Issue 584: the error message for a wrong sequence definition was wrong.
@changelog_1102_li
@changelog_1111_li
#CSV tool: the rowSeparator option is no longer supported, as the same can be achieved with the lineSeparator.
#CSV tool: the rowSeparator option is no longer supported, as the same can be achieved with the lineSeparator.
@changelog_1103_li
@changelog_1112_li
#Descending indexes on MVStore tables did not work properly.
#Descending indexes on MVStore tables did not work properly.
@changelog_1104_li
@changelog_1113_li
#Issue 579: Conditions on the "_rowid_" pseudo-column didn't use an index when using the MVStore.
#Issue 579: Conditions on the "_rowid_" pseudo-column didn't use an index when using the MVStore.
@changelog_1105_li
@changelog_1114_li
#Fixed documentation that "offset" and "fetch" are also keywords since version 1.4.x.
#Fixed documentation that "offset" and "fetch" are also keywords since version 1.4.x.
@changelog_1106_li
@changelog_1115_li
#The Long.MIN_VALUE could not be parsed for auto-increment (identity) columns.
#The Long.MIN_VALUE could not be parsed for auto-increment (identity) columns.
@changelog_1107_li
@changelog_1116_li
#Issue 573: Add implementation for Methods "isWrapperFor()" and "unwrap()" in other JDBC classes.
#Issue 573: Add implementation for Methods "isWrapperFor()" and "unwrap()" in other JDBC classes.
@changelog_1108_li
@changelog_1117_li
#Issue 572: MySQL compatibility for "order by" in update statements.
#Issue 572: MySQL compatibility for "order by" in update statements.
@changelog_1109_li
@changelog_1118_li
#The change in JDBC escape processing in version 1.4.181 affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax "{t 'time}", or "{ts 'timestamp'}", or "{d 'data'}", then both the client and the server need to be upgraded to version 1.4.181 or later.
#The change in JDBC escape processing in version 1.4.181 affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax "{t 'time}", or "{ts 'timestamp'}", or "{d 'data'}", then both the client and the server need to be upgraded to version 1.4.181 or later.
@changelog_1110_h2
@changelog_1119_h2
#Version 1.4.181 Beta (2014-08-06)
#Version 1.4.181 Beta (2014-08-06)
@changelog_1111_li
@changelog_1120_li
#Improved MySQL compatibility by supporting "use schema". Thanks a lot to Karl Pietrzak for the patch!
#Improved MySQL compatibility by supporting "use schema". Thanks a lot to Karl Pietrzak for the patch!
@changelog_1112_li
@changelog_1121_li
#Writing to the trace file is now faster, specially with the debug level.
#Writing to the trace file is now faster, specially with the debug level.
@changelog_1113_li
@changelog_1122_li
#The database option "defrag_always=true" did not work with the MVStore.
#The database option "defrag_always=true" did not work with the MVStore.
@changelog_1114_li
@changelog_1123_li
#The JDBC escape syntax {ts 'value'} did not interpret the value as a timestamp. The same for {d 'value'} (for date) and {t 'value'} (for time). Thanks to Lukas Eder for reporting the issue. The following problem was detected after version 1.4.181 was released: The change in JDBC escape processing affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax {t 'time'}, or {ts 'timestamp'}, or {d 'date'}, then both the client and the server need to be upgraded to version 1.4.181 or later.
#The JDBC escape syntax {ts 'value'} did not interpret the value as a timestamp. The same for {d 'value'} (for date) and {t 'value'} (for time). Thanks to Lukas Eder for reporting the issue. The following problem was detected after version 1.4.181 was released: The change in JDBC escape processing affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax {t 'time'}, or {ts 'timestamp'}, or {d 'date'}, then both the client and the server need to be upgraded to version 1.4.181 or later.
@changelog_1115_li
@changelog_1124_li
#File system abstraction: support replacing existing files using move (currently not for Windows).
#File system abstraction: support replacing existing files using move (currently not for Windows).
@changelog_1116_li
@changelog_1125_li
#The statement "shutdown defrag" now compresses the database (with the MVStore). This command can greatly reduce the file size, and is relatively fast, but is not incremental.
#The statement "shutdown defrag" now compresses the database (with the MVStore). This command can greatly reduce the file size, and is relatively fast, but is not incremental.
@changelog_1117_li
@changelog_1126_li
#The MVStore now automatically compacts the store in the background if there is no read or write activity, which should (after some time; sometimes about one minute) reduce the file size. This is still work in progress, feedback is welcome!
#The MVStore now automatically compacts the store in the background if there is no read or write activity, which should (after some time; sometimes about one minute) reduce the file size. This is still work in progress, feedback is welcome!
@changelog_1118_li
@changelog_1127_li
#Change default value of PAGE_SIZE from 2048 to 4096 to more closely match most file systems block size (PageStore only; the MVStore already used 4096).
#Change default value of PAGE_SIZE from 2048 to 4096 to more closely match most file systems block size (PageStore only; the MVStore already used 4096).
@changelog_1119_li
@changelog_1128_li
#Auto-scale MAX_MEMORY_ROWS and CACHE_SIZE settings by the amount of available RAM. Gives a better out of box experience for people with more powerful machines.
#Auto-scale MAX_MEMORY_ROWS and CACHE_SIZE settings by the amount of available RAM. Gives a better out of box experience for people with more powerful machines.
@changelog_1120_li
@changelog_1129_li
#Handle tabs like 4 spaces in web console, patch by Martin Grajcar.
#Handle tabs like 4 spaces in web console, patch by Martin Grajcar.
@changelog_1121_li
@changelog_1130_li
#Issue 573: Add implementation for Methods "isWrapperFor()" and "unwrap()" in JdbcConnection.java, patch by BigMichi1.
#Issue 573: Add implementation for Methods "isWrapperFor()" and "unwrap()" in JdbcConnection.java, patch by BigMichi1.
@changelog_1122_h2
@changelog_1131_h2
#Version 1.4.180 Beta (2014-07-13)
#Version 1.4.180 Beta (2014-07-13)
@changelog_1123_li
@changelog_1132_li
#MVStore: the store is now auto-compacted automatically up to some point, to avoid very large file sizes. This area is still work in progress.
#MVStore: the store is now auto-compacted automatically up to some point, to avoid very large file sizes. This area is still work in progress.
@changelog_1124_li
@changelog_1133_li
#Sequences of temporary tables (auto-increment or identity columns) were persisted unnecessarily in the database file, and were not removed when re-opening the database.
#Sequences of temporary tables (auto-increment or identity columns) were persisted unnecessarily in the database file, and were not removed when re-opening the database.
@changelog_1125_li
@changelog_1134_li
#MVStore: an IndexOutOfBoundsException could sometimes occur MVMap.openVersion when concurrently accessing the store.
#MVStore: an IndexOutOfBoundsException could sometimes occur MVMap.openVersion when concurrently accessing the store.
@changelog_1126_li
@changelog_1135_li
#The LIRS cache now re-sizes the internal hash map if needed.
#The LIRS cache now re-sizes the internal hash map if needed.
@changelog_1127_li
@changelog_1136_li
#Optionally persist session history in the H2 console. (patch from Martin Grajcar)
#Optionally persist session history in the H2 console. (patch from Martin Grajcar)
@changelog_1128_li
@changelog_1137_li
#Add client-info property to get the number of servers currently in the cluster and which servers that are available. (patch from Nikolaj Fogh)
#Add client-info property to get the number of servers currently in the cluster and which servers that are available. (patch from Nikolaj Fogh)
@changelog_1129_li
@changelog_1138_li
#Fix bug in changing encrypted DB password that kept the file handle open when the wrong password was supplied. (test case from Jens Hohmuth).
#Fix bug in changing encrypted DB password that kept the file handle open when the wrong password was supplied. (test case from Jens Hohmuth).
@changelog_1130_li
@changelog_1139_li
#Issue 567: H2 hangs for a long time then (sometimes) recovers. Introduce a queue when doing table locking to prevent session starvation.
#Issue 567: H2 hangs for a long time then (sometimes) recovers. Introduce a queue when doing table locking to prevent session starvation.
@changelog_1131_h2
@changelog_1140_h2
#Version 1.4.179 Beta (2014-06-23)
#Version 1.4.179 Beta (2014-06-23)
@changelog_1132_li
@changelog_1141_li
#The license was changed to MPL 2.0 (from 1.0) and EPL 1.0.
#The license was changed to MPL 2.0 (from 1.0) and EPL 1.0.
@changelog_1133_li
@changelog_1142_li
#Issue 565: MVStore: concurrently adding LOB objects (with MULTI_THREADED option) resulted in a NullPointerException.
#Issue 565: MVStore: concurrently adding LOB objects (with MULTI_THREADED option) resulted in a NullPointerException.
@changelog_1134_li
@changelog_1143_li
#MVStore: reduced dependencies to other H2 classes.
#MVStore: reduced dependencies to other H2 classes.
@changelog_1135_li
@changelog_1144_li
#There was a way to prevent a database from being re-opened, by creating a column constraint that references a table with a higher id, for example with "check" constraints that contains queries. This is now detected, and creating the table is prohibited. In future versions of H2, most likely creating references to other tables will no longer be supported because of such problems.
#There was a way to prevent a database from being re-opened, by creating a column constraint that references a table with a higher id, for example with "check" constraints that contains queries. This is now detected, and creating the table is prohibited. In future versions of H2, most likely creating references to other tables will no longer be supported because of such problems.
@changelog_1136_li
@changelog_1145_li
#MVStore: descending indexes with "nulls first" did not work as expected (null was ordered last).
#MVStore: descending indexes with "nulls first" did not work as expected (null was ordered last).
@changelog_1137_li
@changelog_1146_li
#Large result sets now always create temporary tables instead of temporary files.
#Large result sets now always create temporary tables instead of temporary files.
@changelog_1138_li
@changelog_1147_li
#When using the PageStore, opening a database failed in some cases with a NullPointerException if temporary tables were used (explicitly, or implicitly when using large result sets).
#When using the PageStore, opening a database failed in some cases with a NullPointerException if temporary tables were used (explicitly, or implicitly when using large result sets).
@changelog_1139_li
@changelog_1148_li
#If a database file in the PageStore file format exists, this file and this mode is now used, even if the database URL does not contain "MV_STORE=FALSE". If a MVStore file exists, it is used.
#If a database file in the PageStore file format exists, this file and this mode is now used, even if the database URL does not contain "MV_STORE=FALSE". If a MVStore file exists, it is used.
@changelog_1140_li
@changelog_1149_li
#Databases created with version 1.3.175 and earlier that contained foreign keys in combination with multi-column indexes could not be opened in some cases. This was due to a bugfix in version 1.3.176: Referential integrity constraints sometimes used the wrong index.
#Databases created with version 1.3.175 and earlier that contained foreign keys in combination with multi-column indexes could not be opened in some cases. This was due to a bugfix in version 1.3.176: Referential integrity constraints sometimes used the wrong index.
@changelog_1141_li
@changelog_1150_li
#MVStore: the ObjectDataType comparison method was incorrect if one key was Serializable and the other was of a common class.
#MVStore: the ObjectDataType comparison method was incorrect if one key was Serializable and the other was of a common class.
@changelog_1142_li
@changelog_1151_li
#Recursive queries with many result rows (more than the setting "max_memory_rows") did not work correctly.
#Recursive queries with many result rows (more than the setting "max_memory_rows") did not work correctly.
@changelog_1143_li
@changelog_1152_li
#The license has changed to MPL 2.0 + EPL 1.0.
#The license has changed to MPL 2.0 + EPL 1.0.
@changelog_1144_li
@changelog_1153_li
#MVStore: temporary tables from result sets could survive re-opening a database, which could result in a ClassCastException.
#MVStore: temporary tables from result sets could survive re-opening a database, which could result in a ClassCastException.
@changelog_1145_li
@changelog_1154_li
#Issue 566: MVStore: unique indexes that were created later on did not work correctly if there were over 5000 rows in the table. Existing databases need to be re-created (at least the broken index need to be re-built).
#Issue 566: MVStore: unique indexes that were created later on did not work correctly if there were over 5000 rows in the table. Existing databases need to be re-created (at least the broken index need to be re-built).
@changelog_1146_li
@changelog_1155_li
#MVStore: creating secondary indexes on large tables results in missing rows in the index.
#MVStore: creating secondary indexes on large tables results in missing rows in the index.
@changelog_1147_li
@changelog_1156_li
#Metadata: the password of linked tables is now only visible for admin users.
#Metadata: the password of linked tables is now only visible for admin users.
@changelog_1148_li
@changelog_1157_li
#For Windows, database URLs of the form "jdbc:h2:/test" where considered relative and did not work unless the system property "h2.implicitRelativePath" was used.
#For Windows, database URLs of the form "jdbc:h2:/test" where considered relative and did not work unless the system property "h2.implicitRelativePath" was used.
@changelog_1149_li
@changelog_1158_li
#Windows: using a base directory of "C:/" and similar did not work as expected.
#Windows: using a base directory of "C:/" and similar did not work as expected.
@changelog_1150_li
@changelog_1159_li
#Follow JDBC specification on Procedures MetaData, use P0 as return type of procedure.
#Follow JDBC specification on Procedures MetaData, use P0 as return type of procedure.
@changelog_1151_li
@changelog_1160_li
#Issue 531: IDENTITY ignored for added column.
#Issue 531: IDENTITY ignored for added column.
@changelog_1152_li
@changelog_1161_li
#FileSystem: improve exception throwing compatibility with JDK
#FileSystem: improve exception throwing compatibility with JDK
@changelog_1153_li
@changelog_1162_li
#Spatial Index: adjust costs so we do not use the spatial index if the query does not contain an intersects operator.
#Spatial Index: adjust costs so we do not use the spatial index if the query does not contain an intersects operator.
@changelog_1154_li
@changelog_1163_li
#Fix multi-threaded deadlock when using a View that includes a TableFunction.
#Fix multi-threaded deadlock when using a View that includes a TableFunction.
@changelog_1155_li
@changelog_1164_li
#Fix bug in dividing very-small BigDecimal numbers.
#Fix bug in dividing very-small BigDecimal numbers.
@changelog_1156_h2
@changelog_1165_h2
#Version 1.4.178 Beta (2014-05-02)
#Version 1.4.178 Beta (2014-05-02)
@changelog_1157_li
@changelog_1166_li
#Issue 559: Make dependency on org.osgi.service.jdbc optional.
#Issue 559: Make dependency on org.osgi.service.jdbc optional.
@changelog_1158_li
@changelog_1167_li
#Improve error message when the user specifies an unsupported combination of database settings.
#Improve error message when the user specifies an unsupported combination of database settings.
@changelog_1159_li
@changelog_1168_li
#MVStore: in the multi-threaded mode, NullPointerException and other exceptions could occur.
#MVStore: in the multi-threaded mode, NullPointerException and other exceptions could occur.
@changelog_1160_li
@changelog_1169_li
#MVStore: some database file could not be compacted due to a bug in the bookkeeping of the fill rate. Also, database file were compacted quite slowly. This has been improved; but more changes in this area are expected.
#MVStore: some database file could not be compacted due to a bug in the bookkeeping of the fill rate. Also, database file were compacted quite slowly. This has been improved; but more changes in this area are expected.
@changelog_1161_li
@changelog_1170_li
#MVStore: support for volatile maps (that don't store changes).
#MVStore: support for volatile maps (that don't store changes).
@changelog_1162_li
@changelog_1171_li
#MVStore mode: in-memory databases now also use the MVStore.
#MVStore mode: in-memory databases now also use the MVStore.
@changelog_1163_li
@changelog_1172_li
#In server mode, appending ";autocommit=false" to the database URL was working, but the return value of Connection.getAutoCommit() was wrong.
#In server mode, appending ";autocommit=false" to the database URL was working, but the return value of Connection.getAutoCommit() was wrong.
@changelog_1164_li
@changelog_1173_li
#Issue 561: OSGi: the import package declaration of org.h2 excluded version 1.4.
#Issue 561: OSGi: the import package declaration of org.h2 excluded version 1.4.
@changelog_1165_li
@changelog_1174_li
#Issue 558: with the MVStore, a NullPointerException could occur when using LOBs at session commit (LobStorageMap.removeLob).
#Issue 558: with the MVStore, a NullPointerException could occur when using LOBs at session commit (LobStorageMap.removeLob).
@changelog_1166_li
@changelog_1175_li
#Remove the "h2.MAX_MEMORY_ROWS_DISTINCT" system property to reduce confusion. We already have the MAX_MEMORY_ROWS setting which does a very similar thing, and is better documented.
#Remove the "h2.MAX_MEMORY_ROWS_DISTINCT" system property to reduce confusion. We already have the MAX_MEMORY_ROWS setting which does a very similar thing, and is better documented.
@changelog_1167_li
@changelog_1176_li
#Issue 554: Web Console in an IFrame was not fully supported.
#Issue 554: Web Console in an IFrame was not fully supported.
@changelog_1168_h2
@changelog_1177_h2
#Version 1.4.177 Beta (2014-04-12)
#Version 1.4.177 Beta (2014-04-12)
@changelog_1169_li
@changelog_1178_li
#By default, the MV_STORE option is enabled, so it is using the new MVStore storage. The MVCC setting is by default set to the same values as the MV_STORE setting, so it is also enabled by default. For testing, both settings can be disabled by appending ";MV_STORE=FALSE" and/or ";MVCC=FALSE" to the database URL.
#By default, the MV_STORE option is enabled, so it is using the new MVStore storage. The MVCC setting is by default set to the same values as the MV_STORE setting, so it is also enabled by default. For testing, both settings can be disabled by appending ";MV_STORE=FALSE" and/or ";MVCC=FALSE" to the database URL.
@changelog_1170_li
@changelog_1179_li
#The file locking method 'serialized' is no longer supported. This mode might return in a future version, however this is not clear right now. A new implementation and new tests would be needed.
#The file locking method 'serialized' is no longer supported. This mode might return in a future version, however this is not clear right now. A new implementation and new tests would be needed.
@changelog_1171_li
@changelog_1180_li
#Enable the new storage format for dates (system property "h2.storeLocalTime"). For the MVStore mode, this is always enabled, but with version 1.4 this is even enabled in the PageStore mode.
#Enable the new storage format for dates (system property "h2.storeLocalTime"). For the MVStore mode, this is always enabled, but with version 1.4 this is even enabled in the PageStore mode.
@changelog_1172_li
@changelog_1181_li
#Implicit relative paths are disabled (system property "h2.implicitRelativePath"), so that the database URL jdbc:h2:test now needs to be written as jdbc:h2:./test.
#Implicit relative paths are disabled (system property "h2.implicitRelativePath"), so that the database URL jdbc:h2:test now needs to be written as jdbc:h2:./test.
@changelog_1173_li
@changelog_1182_li
#"select ... fetch first 1 row only" is supported with the regular mode. This was disabled so far because "fetch" and "offset" are now keywords. See also Mode.supportOffsetFetch.
#"select ... fetch first 1 row only" is supported with the regular mode. This was disabled so far because "fetch" and "offset" are now keywords. See also Mode.supportOffsetFetch.
@changelog_1174_li
@changelog_1183_li
#Byte arrays are now sorted in unsigned mode (x'99' is larger than x'09'). (System property "h2.sortBinaryUnsigned", Mode.binaryUnsigned, setting "binary_collation").
#Byte arrays are now sorted in unsigned mode (x'99' is larger than x'09'). (System property "h2.sortBinaryUnsigned", Mode.binaryUnsigned, setting "binary_collation").
@changelog_1175_li
@changelog_1184_li
#Csv.getInstance will be removed in future versions of 1.4. Use the public constructor instead.
#Csv.getInstance will be removed in future versions of 1.4. Use the public constructor instead.
@changelog_1176_li
@changelog_1185_li
#Remove support for the limited old-style outer join syntax using "(+)". Use "outer join" instead. System property "h2.oldStyleOuterJoin".
#Remove support for the limited old-style outer join syntax using "(+)". Use "outer join" instead. System property "h2.oldStyleOuterJoin".
@changelog_1177_li
@changelog_1186_li
#Support the data type "DATETIME2" as an alias for "DATETIME", for MS SQL Server compatibility.
#Support the data type "DATETIME2" as an alias for "DATETIME", for MS SQL Server compatibility.
@changelog_1178_li
@changelog_1187_li
#Add Oracle-compatible TRANSLATE function, patch by Eric Chatellier.
#Add Oracle-compatible TRANSLATE function, patch by Eric Chatellier.
@changelog_1179_h2
@changelog_1188_h2
#Version 1.3.176 (2014-04-05)
#Version 1.3.176 (2014-04-05)
@changelog_1180_li
@changelog_1189_li
#The file locking method 'serialized' is no longer documented, as it will not be available in version 1.4.
#The file locking method 'serialized' is no longer documented, as it will not be available in version 1.4.
@changelog_1181_li
@changelog_1190_li
#The static method Csv.getInstance() was removed. Use the public constructor instead.
#The static method Csv.getInstance() was removed. Use the public constructor instead.
@changelog_1182_li
@changelog_1191_li
#The default user name for the Script, RunScript, Shell, and CreateCluster tools are no longer "sa" but an empty string.
#The default user name for the Script, RunScript, Shell, and CreateCluster tools are no longer "sa" but an empty string.
@changelog_1183_li
@changelog_1192_li
#The stack trace of the exception "The object is already closed" is no longer logged by default.
#The stack trace of the exception "The object is already closed" is no longer logged by default.
@changelog_1184_li
@changelog_1193_li
#If a value of a result set was itself a result set, the result could only be read once.
#If a value of a result set was itself a result set, the result could only be read once.
@changelog_1185_li
@changelog_1194_li
#Column constraints are also visible in views (patch from Nicolas Fortin for H2GIS).
#Column constraints are also visible in views (patch from Nicolas Fortin for H2GIS).
@changelog_1186_li
@changelog_1195_li
#Granting a additional right to a role that already had a right for that table was not working.
#Granting a additional right to a role that already had a right for that table was not working.
@changelog_1187_li
@changelog_1196_li
#Spatial index: a few bugs have been fixed (using spatial constraints in views, transferring geometry objects over TCP/IP, the returned geometry object is copied when needed).
#Spatial index: a few bugs have been fixed (using spatial constraints in views, transferring geometry objects over TCP/IP, the returned geometry object is copied when needed).
@changelog_1188_li
@changelog_1197_li
#Issue 551: the datatype documentation was incorrect (found by Bernd Eckenfels).
#Issue 551: the datatype documentation was incorrect (found by Bernd Eckenfels).
@changelog_1189_li
@changelog_1198_li
#Issue 368: ON DUPLICATE KEY UPDATE did not work for multi-row inserts. Test case from Angus Macdonald.
#Issue 368: ON DUPLICATE KEY UPDATE did not work for multi-row inserts. Test case from Angus Macdonald.
@changelog_1190_li
@changelog_1199_li
#OSGi: the package javax.tools is now imported (as an optional).
#OSGi: the package javax.tools is now imported (as an optional).
@changelog_1191_li
@changelog_1200_li
#H2 Console: auto-complete is now disabled by default, but there is a hot-key (Ctrl+Space).
#H2 Console: auto-complete is now disabled by default, but there is a hot-key (Ctrl+Space).
@changelog_1192_li
@changelog_1201_li
#H2 Console: auto-complete did not work with multi-line statements.
#H2 Console: auto-complete did not work with multi-line statements.
@changelog_1193_li
@changelog_1202_li
#CLOB and BLOB data was not immediately removed after a rollback.
#CLOB and BLOB data was not immediately removed after a rollback.
@changelog_1194_li
@changelog_1203_li
#There is a new Aggregate API that supports the internal H2 data types (GEOMETRY for example). Thanks a lot to Nicolas Fortin for the patch!
#There is a new Aggregate API that supports the internal H2 data types (GEOMETRY for example). Thanks a lot to Nicolas Fortin for the patch!
@changelog_1195_li
@changelog_1204_li
#Referential integrity constraints sometimes used the wrong index, such that updating a row in the referenced table incorrectly failed with a constraint violation.
#Referential integrity constraints sometimes used the wrong index, such that updating a row in the referenced table incorrectly failed with a constraint violation.
@changelog_1196_li
@changelog_1205_li
#The Polish translation was completed and corrected by Wojtek Jurczyk. Thanks a lot!
#The Polish translation was completed and corrected by Wojtek Jurczyk. Thanks a lot!
@changelog_1197_li
@changelog_1206_li
#Issue 545: Unnecessary duplicate code was removed.
#Issue 545: Unnecessary duplicate code was removed.
@changelog_1198_li
@changelog_1207_li
#The profiler tool can now process files with full thread dumps.
#The profiler tool can now process files with full thread dumps.
@changelog_1199_li
@changelog_1208_li
#MVStore: the file format was changed slightly.
#MVStore: the file format was changed slightly.
@changelog_1200_li
@changelog_1209_li
#MVStore mode: the CLOB and BLOB storage was re-implemented and is now much faster than with the PageStore (which is still the default storage).
#MVStore mode: the CLOB and BLOB storage was re-implemented and is now much faster than with the PageStore (which is still the default storage).
@changelog_1201_li
@changelog_1210_li
#MVStore mode: creating indexes is now much faster (in many cases faster than with the default PageStore).
#MVStore mode: creating indexes is now much faster (in many cases faster than with the default PageStore).
@changelog_1202_li
@changelog_1211_li
#Various bugs in the MVStore storage and have been fixed, including a bug in the R-tree implementation. The database could get corrupt if there were transient IO exceptions while storing.
#Various bugs in the MVStore storage and have been fixed, including a bug in the R-tree implementation. The database could get corrupt if there were transient IO exceptions while storing.
@changelog_1203_li
@changelog_1212_li
#The method org.h2.expression.Function.getCost could throw a NullPointException.
#The method org.h2.expression.Function.getCost could throw a NullPointException.
@changelog_1204_li
@changelog_1213_li
#Storing LOBs in separate files (outside of the main database file) is no longer supported for new databases.
#Storing LOBs in separate files (outside of the main database file) is no longer supported for new databases.
@changelog_1205_li
@changelog_1214_li
#Lucene 2 is no longer supported.
#Lucene 2 is no longer supported.
@changelog_1206_li
@changelog_1215_li
#Fix bug in calculating default MIN and MAX values for SEQUENCE.
#Fix bug in calculating default MIN and MAX values for SEQUENCE.
@changelog_1207_li
@changelog_1216_li
#Fix bug in performing IN queries with multiple values when IGNORECASE=TRUE
#Fix bug in performing IN queries with multiple values when IGNORECASE=TRUE
@changelog_1208_li
@changelog_1217_li
#Add entry-point to org.h2.tools.Shell so it can be called from inside an application. patch by Thomas Gillet.
#Add entry-point to org.h2.tools.Shell so it can be called from inside an application. patch by Thomas Gillet.
@changelog_1209_li
@changelog_1218_li
#Fix bug that prevented the PgServer from being stopped and started multiple times.
#Fix bug that prevented the PgServer from being stopped and started multiple times.
@changelog_1210_li
@changelog_1219_li
#Support some more DDL syntax for MySQL, patch from Peter Jentsch.
#Support some more DDL syntax for MySQL, patch from Peter Jentsch.
@changelog_1211_li
@changelog_1220_li
#Issue 548: TO_CHAR does not format MM and DD correctly when the month or day of the month is 1 digit, patch from "the.tucc"
#Issue 548: TO_CHAR does not format MM and DD correctly when the month or day of the month is 1 digit, patch from "the.tucc"
@changelog_1212_li
@changelog_1221_li
#Fix bug in varargs support in ALIAS's, patch from Nicolas Fortin
#Fix bug in varargs support in ALIAS's, patch from Nicolas Fortin
@cheatSheet_1000_h1
@cheatSheet_1000_h1
...
@@ -2531,7 +2567,7 @@ Centralリ�?ジトリ�?�利用
...
@@ -2531,7 +2567,7 @@ Centralリ�?ジトリ�?�利用
H2
H2
@cheatSheet_1003_li
@cheatSheet_1003_li
# is <a href="http://code.google.com/p/h2database/source">open source</a>, <a href="license.html">free to use and distribute</a>.
# is <a href="https://github.com/h2database/h2database">open source</a>, <a href="license.html">free to use and distribute</a>.
@cheatSheet_1004_a
@cheatSheet_1004_a
ダウンロード
ダウンロード
...
@@ -2693,7 +2729,7 @@ Windows Installer
...
@@ -2693,7 +2729,7 @@ Windows Installer
Platform-Independent Zip
Platform-Independent Zip
@download_1007_h3
@download_1007_h3
#Download Mirror and Older Versions
#Old Versions
@download_1008_a
@download_1008_a
Platform-Independent Zip
Platform-Independent Zip
...
@@ -2729,10 +2765,10 @@ Platform-Independent Zip
...
@@ -2729,10 +2765,10 @@ Platform-Independent Zip
#Upgrade database from 1.1 to the current version
#Upgrade database from 1.1 to the current version
@download_1019_h3
@download_1019_h3
サブ�?ージョン�?�ソースリ�?ジトリ
#Git Source Repository
@download_1020_a
@download_1020_a
Google Code
#Github
@download_1021_p
@download_1021_p
# For details about changes, see the <a href="changelog.html">Change Log</a>.
# For details about changes, see the <a href="changelog.html">Change Log</a>.
...
@@ -2834,7 +2870,7 @@ F A Q
...
@@ -2834,7 +2870,7 @@ F A Q
#When using Install4j before 4.1.4 on Linux and enabling <code>pack200</code>, the <code>h2*.jar</code> becomes corrupted by the install process, causing application failure. A workaround is to add an empty file <code>h2*.jar.nopack</code> next to the <code>h2*.jar</code> file. This problem is solved in Install4j 4.1.4.
#When using Install4j before 4.1.4 on Linux and enabling <code>pack200</code>, the <code>h2*.jar</code> becomes corrupted by the install process, causing application failure. A workaround is to add an empty file <code>h2*.jar.nopack</code> next to the <code>h2*.jar</code> file. This problem is solved in Install4j 4.1.4.
@faq_1027_p
@faq_1027_p
# For a complete list, see <a href="http://code.google.com/p/h2database/issues/list">Open Issues</a>.
# For a complete list, see <a href="https://github.com/h2database/h2database/issues">Open Issues</a>.
@faq_1028_h3
@faq_1028_h3
�?��?�データベースエンジン�?�オープンソース�?��?��?�？
�?��?�データベースエンジン�?�オープンソース�?��?��?�？
...
@@ -3794,7 +3830,7 @@ ODBCドライ�?
...
@@ -3794,7 +3830,7 @@ ODBCドライ�?
# *10 Derby and HSQLDB <a href="http://en.wikipedia.org/wiki/Block_cipher_modes_of_operation#Electronic_codebook_.28ECB.29">don't hide data patterns well</a>.
# *10 Derby and HSQLDB <a href="http://en.wikipedia.org/wiki/Block_cipher_modes_of_operation#Electronic_codebook_.28ECB.29">don't hide data patterns well</a>.
@features_1260_p
@features_1260_p
# *11 The MULTI_THREADED option is not enabled by default, and not yet supported when using MVCC.
# *11 The MULTI_THREADED option is not enabled by default, and with version 1.3.x not supported when using MVCC.
@features_1261_p
@features_1261_p
# *12 Derby doesn't support the <code>EXPLAIN</code> statement, but it supports runtime statistics and retrieving statement execution plans.
# *12 Derby doesn't support the <code>EXPLAIN</code> statement, but it supports runtime statistics and retrieving statement execution plans.
...
@@ -4211,10 +4247,10 @@ jdbc:h2:mem:
...
@@ -4211,10 +4247,10 @@ jdbc:h2:mem:
マル�?スレッドサ�?ート
マル�?スレッドサ�?ート
@features_1399_p
@features_1399_p
# This database is multithreading-safe. That means, if an application is multi-threaded, it does not need to worry about synchronizing access to the database. Internally, most requests to the same database are synchronized. That means an application can use multiple threads that access the same database at the same time, however if one thread executes a long running query, the other threads need to wait.
# This database is multithreading-safe. If an application is multi-threaded, it does not need to worry about synchronizing access to the database. An application should normally use one connection per thread. This database synchronizes access to the same connection, but other databases may not do this. To get higher concurrency, you need to use multiple connections.
@features_1400_p
@features_1400_p
# An application should normally use one connection per thread. This database synchronizes access to the same connection, but other databases may not do this.
# By default, requests to the same database are synchronized. That means an application can use multiple threads that access the same database at the same time, however if one thread executes a long running query, the other threads need to wait. To enable concurrent database usage, see the setting <code>MULTI_THREADED</code>.
@features_1401_h3
@features_1401_h3
ロック�?ロックタイムアウト�?デッドロック
ロック�?ロックタイムアウト�?デッドロック
...
@@ -4685,7 +4721,7 @@ Javaコード生�?
...
@@ -4685,7 +4721,7 @@ Javaコード生�?
# Databases in zip files are read-only. The performance for some queries will be slower than when using a regular database, because random access in zip files is not supported (only streaming). How much this affects the performance depends on the queries and the data. The database is not read in memory; therefore large databases are supported as well. The same indexes are used as when using a regular database.
# Databases in zip files are read-only. The performance for some queries will be slower than when using a regular database, because random access in zip files is not supported (only streaming). How much this affects the performance depends on the queries and the data. The database is not read in memory; therefore large databases are supported as well. The same indexes are used as when using a regular database.
@features_1557_p
@features_1557_p
# If the database is larger than a few megabytes, performance is much better if the database file is split into multiple smaller files, because random access in compressed files is not possible. See also the sample application <a href="http://code.google.com/p/h2database/source/browse/trunk/h2/src/test/org/h2/samples/ReadOnlyDatabaseInZip.java">ReadOnlyDatabaseInZip</a>.
# If the database is larger than a few megabytes, performance is much better if the database file is split into multiple smaller files, because random access in compressed files is not possible. See also the sample application <a href="https://github.com/h2database/h2database/tree/master/h2/src/test/org/h2/samples/ReadOnlyDatabaseInZip.java">ReadOnlyDatabaseInZip</a>.
#Support index-only when doing selects (i.e. without needing to load the actual table data)
@roadmap_1511_h2
#Not Planned
#Not Planned
@roadmap_1512_li
@roadmap_1511_li
#HSQLDB (did) support this: select id i from test where i<0 (other databases don't). Supporting it may break compatibility.
#HSQLDB (did) support this: select id i from test where i<0 (other databases don't). Supporting it may break compatibility.
@roadmap_1513_li
@roadmap_1512_li
#String.intern (so that Strings can be compared with ==) will not be used because some VMs have problems when used extensively.
#String.intern (so that Strings can be compared with ==) will not be used because some VMs have problems when used extensively.
@roadmap_1514_li
@roadmap_1513_li
#In prepared statements, identifier names (table names and so on) can not be parameterized. Adding such a feature would complicate the source code without providing reasonable speedup, and would slow down regular prepared statements.
#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.
build_1062_li=Download all dependencies (Windows)\:
build_1062_li=Download all dependencies\:
build_1063_code=build.bat download
build_1063_code=build.bat download
build_1064_li=In Eclipse, create a new Java project from existing source code\:<code>File, New, Project, Java Project, Create project from existing source</code>.
build_1064_li=(Windows)
build_1065_li=Select the <code>h2</code> folder, click <code>Next</code> and <code>Finish</code>.
build_1065_code=./build.sh download
build_1066_li=To resolve <code>com.sun.javadoc</code> import statements, you may need to manually add the file <code><java.home>/../lib/tools.jar</code> to the build path.
build_1066_li=(otherwise)
build_1067_h2=Translating
build_1067_li=In Eclipse, create a new Java project from existing source code\:<code>File, New, Project, Java Project, Create project from existing source</code>.
build_1068_p=\ The translation of this software is split into the following parts\:
build_1068_li=Select the <code>h2</code> folder, click <code>Next</code> and <code>Finish</code>.
build_1069_li=To resolve <code>com.sun.javadoc</code> import statements, you may need to manually add the file <code><java.home>/../lib/tools.jar</code> to the build path.
build_1071_p=\ 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_1071_p=\ The translation of this software is split into the following parts\:
build_1074_li=Only use Java 6 features (do not use Java 7) (see <a href\="\#environment">Environment</a>).
build_1074_p=\ 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_1075_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_1075_h2=Providing Patches
build_1076_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_1076_p=\ If you like to provide patches, please consider the following guidelines to simplify merging them\:
build_1077_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_1077_li=Only use Java 6 features (do not use Java 7) (see <a href\="\#environment">Environment</a>).
build_1078_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_1078_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_1079_li=Verify that you did not break other features\:run the test cases by executing <code>build test</code>.
build_1079_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_1080_li=Provide end user documentation if required (<code>src/docsrc/html/*</code>).
build_1080_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_1081_li=Document grammar changes in <code>src/docsrc/help/help.csv</code>
build_1081_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_1082_li=Provide a change log entry (<code>src/docsrc/html/changelog.html</code>).
build_1082_li=Verify that you did not break other features\:run the test cases by executing <code>build test</code>.
build_1083_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_1083_li=Provide end user documentation if required (<code>src/docsrc/html/*</code>).
build_1084_li=Run <code>src/installer/buildRelease</code> to find and fix formatting errors.
build_1084_li=Document grammar changes in <code>src/docsrc/help/help.csv</code>
build_1085_li=Verify the formatting using <code>build docs</code> and <code>build javadoc</code>.
build_1085_li=Provide a change log entry (<code>src/docsrc/html/changelog.html</code>).
build_1086_li=Submit patches as <code>.patch</code> files (compressed if big). To create a patch using Eclipse, use Team / Create Patch.
build_1086_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_1087_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_1087_li=Run <code>src/installer/buildRelease</code> to find and fix formatting errors.
build_1088_p=\ "I wrote the code, it's mine, and I'm contributing it to H2 for distribution multiple-licensed under the MPL 2.0, and the EPL 1.0 (http\://h2database.com/html/license.html)."
build_1088_li=Verify the formatting using <code>build docs</code> and <code>build javadoc</code>.
build_1089_h2=Reporting Problems or Requests
build_1089_li=Submit patches as <code>.patch</code> files (compressed if big). To create a patch using Eclipse, use Team / Create Patch.
build_1090_p=\ Please consider the following checklist if you have a question, want to report a problem, or if you have a feature request\:
build_1090_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\="https\://github.com/h2database/h2database/issues">issue report or attachment</a>. Significant contributions need to include the following statement\:
build_1091_li=For bug reports, please provide a <a href\="http\://sscce.org/">short, self contained, correct (compilable), example</a> of the problem.
build_1091_p=\ "I wrote the code, it's mine, and I'm contributing it to H2 for distribution multiple-licensed under the MPL 2.0, and the EPL 1.0 (http\://h2database.com/html/license.html)."
build_1092_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_1092_h2=Reporting Problems or Requests
build_1093_li=Before posting problems, check the <a href\="faq.html">FAQ</a> and do a <a href\="http\://google.com">Google search</a>.
build_1093_p=\ Please consider the following checklist if you have a question, want to report a problem, or if you have a feature request\:
build_1094_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_1094_li=For bug reports, please provide a <a href\="http\://sscce.org/">short, self contained, correct (compilable), example</a> of the problem.
build_1095_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_1095_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_1096_li=For large attachments, use a public temporary storage such as <a href\="http\://rapidshare.com">Rapidshare</a>.
build_1096_li=Before posting problems, check the <a href\="faq.html">FAQ</a> and do a <a href\="http\://google.com">Google search</a>.
build_1097_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_1097_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_1098_li=For out-of-memory problems, please analyze the problem yourself first, for example using the command line option <code>-XX\:+HeapDumpOnOutOfMemoryError</code> (to create a heap dump file on out of memory) and a memory analysis tool such as the <a href\="http\://www.eclipse.org/mat">Eclipse Memory Analyzer (MAT)</a>.
build_1098_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\="https\://github.com/h2database/h2database/tree/master/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_1099_li=It may take a few days to get an answers. Please do not double post.
build_1099_li=For large attachments, use a public temporary storage such as <a href\="http\://rapidshare.com">Rapidshare</a>.
build_1100_h2=Automated Build
build_1100_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\="https\://github.com/h2database/h2database/issues">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_1101_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_1101_li=For out-of-memory problems, please analyze the problem yourself first, for example using the command line option <code>-XX\:+HeapDumpOnOutOfMemoryError</code> (to create a heap dump file on out of memory) and a memory analysis tool such as the <a href\="http\://www.eclipse.org/mat">Eclipse Memory Analyzer (MAT)</a>.
build_1102_a=Test Output
build_1102_li=It may take a few days to get an answers. Please do not double post.
build_1104_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_1108_p=\ The railroad diagrams of the <a href\="grammar.html">SQL grammar</a> are HTML, formatted as nested tables. The diagrams are generated as follows\:
build_1108_a=Build Newsfeed
build_1109_li=The BNF parser (<code>org.h2.bnf.Bnf</code>) reads and parses the BNF from the file <code>help.csv</code>.
build_1109_a=Latest Jar File (download, 1 MB)
build_1110_li=The page parser (<code>org.h2.server.web.PageParser</code>) reads the template HTML file and fills in the diagrams.
build_1110_h2=Generating Railroad Diagrams
build_1111_li=The rail images (one straight, four junctions, two turns) are generated using a simple Java application.
build_1111_p=\ The railroad diagrams of the <a href\="grammar.html">SQL grammar</a> are HTML, formatted as nested tables. The diagrams are generated as follows\:
build_1112_p=\ To generate railroad diagrams for other grammars, see the package <code>org.h2.jcr</code>. This package is used to generate the SQL-2 railroad diagrams for the JCR 2.0 specification.
build_1112_li=The BNF parser (<code>org.h2.bnf.Bnf</code>) reads and parses the BNF from the file <code>help.csv</code>.
build_1113_li=The page parser (<code>org.h2.server.web.PageParser</code>) reads the template HTML file and fills in the diagrams.
build_1114_li=The rail images (one straight, four junctions, two turns) are generated using a simple Java application.
build_1115_p=\ To generate railroad diagrams for other grammars, see the package <code>org.h2.jcr</code>. This package is used to generate the SQL-2 railroad diagrams for the JCR 2.0 specification.
changelog_1000_h1=Change Log
changelog_1000_h1=Change Log
changelog_1001_h2=Next Version (unreleased)
changelog_1001_h2=Next Version (unreleased)
changelog_1002_li=-
changelog_1002_li=Granting a schema is now supported.
changelog_1003_li=Linked tables did not work when a function-based index is present (Oracle).
changelog_1004_li=MVStore\:concurrent changes to the same row could result in the exception "The transaction log might be corrupt for key ...". This could only be reproduced with 3 or more threads.
changelog_1004_li=Creating a user with a null password, salt, or hash threw a NullPointerException.
changelog_1005_li=Results with CLOB or BLOB data are no longer reused.
changelog_1005_li=Foreign key\:don't add a single column index if column is leading key of existing index.
changelog_1006_li=References to BLOB and CLOB objects now have a timeout. The configuration setting is LOB_TIMEOUT (default 5 minutes). This should avoid growing the database file if there are many queries that return BLOB or CLOB objects, and the database is not closed for a longer time.
changelog_1006_li=Pull request \#4\:Creating and removing temporary tables was getting slower and slower over time, because an internal object id was allocated but never de-allocated.
changelog_1007_li=MVStore\:when committing a session that removed LOB values, changes were flushed unnecessarily.
changelog_1007_li=Issue 609\:the spatial index did not support NULL with update and delete operations.
changelog_1008_li=Issue 610\:possible integer overflow in WriteBuffer.grow().
changelog_1008_li=Pull request \#2\:Add external metadata type support (table type "external")
changelog_1009_li=Issue 609\:the spatial index did not support NULL (ClassCastException).
changelog_1009_li=MS SQL Server\:the CONVERT method did not work in views and derived tables.
changelog_1010_li=MVStore\:in some cases, CLOB/BLOB data blocks were removed incorrectly when opening a database.
changelog_1010_li=Java 8 compatibility for "regexp_replace".
changelog_1011_li=MVStore\:updates that affected many rows were were slow in some cases if there was a secondary index.
changelog_1011_li=When in cluster mode, and one of the nodes goes down, we need to log the problem with priority "error", not "debug"
changelog_1012_li=Using "runscript" with autocommit disabled could result in a lock timeout on the internal table "SYS".
changelog_1013_li=Issue 603\:there was a memory leak when using H2 in a web application. Apache Tomcat logged an error message\:"The web application ... created a ThreadLocal with key of type [org.h2.util.DateTimeUtils$1]".
changelog_1013_li=MVStore\:concurrent changes to the same row could result in the exception "The transaction log might be corrupt for key ...". This could only be reproduced with 3 or more threads.
changelog_1014_li=When using the MVStore, running a SQL script generate by the Recover tool from a PageStore file failed with a strange error message (NullPointerException), now a clear error message is shown.
changelog_1014_li=Results with CLOB or BLOB data are no longer reused.
changelog_1015_li=Issue 605\:with version 1.4.186, opening a database could result in an endless loop in LobStorageMap.init.
changelog_1015_li=References to BLOB and CLOB objects now have a timeout. The configuration setting is LOB_TIMEOUT (default 5 minutes). This should avoid growing the database file if there are many queries that return BLOB or CLOB objects, and the database is not closed for a longer time.
changelog_1016_li=Queries that use the same table alias multiple times now work. Before, the select expression list was expanded incorrectly. Example\:"select * from a as x, b as x".
changelog_1016_li=MVStore\:when committing a session that removed LOB values, changes were flushed unnecessarily.
changelog_1017_li=The MySQL compatibility feature "insert ... on duplicate key update" did not work with a non-default schema.
changelog_1017_li=Issue 610\:possible integer overflow in WriteBuffer.grow().
changelog_1018_li=Issue 599\:the condition "in(x, y)" could not be used in the select list when using "group by".
changelog_1018_li=Issue 609\:the spatial index did not support NULL (ClassCastException).
changelog_1019_li=The LIRS cache could grow larger than the allocated memory.
changelog_1019_li=MVStore\:in some cases, CLOB/BLOB data blocks were removed incorrectly when opening a database.
changelog_1020_li=A new file system implementation that re-opens the file if it was closed due to the application calling Thread.interrupt(). File name prefix "retry\:". Please note it is strongly recommended to avoid calling Thread.interrupt; this is a problem for various libraries, including Apache Lucene.
changelog_1020_li=MVStore\:updates that affected many rows were were slow in some cases if there was a secondary index.
changelog_1021_li=MVStore\: use RandomAccessFile file system if the file name starts with "file\:".
changelog_1021_li=Using "runscript" with autocommit disabled could result in a lock timeout on the internal table "SYS".
changelog_1022_li=Allow DATEADD to take a long value for count when manipulating milliseconds.
changelog_1022_li=Issue 603\:there was a memory leak when using H2 in a web application. Apache Tomcat logged an error message\:"The web application ... created a ThreadLocal with key of type [org.h2.util.DateTimeUtils$1]".
changelog_1023_li=When using MV_STORE\=TRUE and the SET CACHE_SIZE setting, the cache size was incorrectly set, so that it was effectively 1024 times smaller than it should be.
changelog_1023_li=When using the MVStore, running a SQL script generate by the Recover tool from a PageStore file failed with a strange error message (NullPointerException), now a clear error message is shown.
changelog_1024_li=Concurrent CREATE TABLE... IF NOT EXISTS in the presence of MULTI_THREAD\=TRUE could throw an exception.
changelog_1024_li=Issue 605\:with version 1.4.186, opening a database could result in an endless loop in LobStorageMap.init.
changelog_1025_li=Fix bug in MVStore when creating lots of temporary tables, where we could run out of transaction IDs.
changelog_1025_li=Queries that use the same table alias multiple times now work. Before, the select expression list was expanded incorrectly. Example\:"select * from a as x, b as x".
changelog_1026_li=Add support for PostgreSQL STRING_AGG function. Patch by Fred Aquiles.
changelog_1026_li=The MySQL compatibility feature "insert ... on duplicate key update" did not work with a non-default schema.
changelog_1027_li=Fix bug in "jdbc\:h2\:nioMemFS" isRoot() function. Also, the page size was increased to 64 KB.
changelog_1027_li=Issue 599\:the condition "in(x, y)" could not be used in the select list when using "group by".
changelog_1028_li=The LIRS cache could grow larger than the allocated memory.
changelog_1029_li=The Servlet API 3.0.1 is now used, instead of 2.4.
changelog_1029_li=A new file system implementation that re-opens the file if it was closed due to the application calling Thread.interrupt(). File name prefix "retry\:". Please note it is strongly recommended to avoid calling Thread.interrupt; this is a problem for various libraries, including Apache Lucene.
changelog_1030_li=MVStore\:old chunks no longer removed in append-only mode.
changelog_1030_li=MVStore\: use RandomAccessFile file system if the file name starts with "file\:".
changelog_1031_li=MVStore\:the cache for page references could grow far too big, resulting in out of memory in some cases.
changelog_1031_li=Allow DATEADD to take a long value for count when manipulating milliseconds.
changelog_1032_li=MVStore\:orphaned lob objects were not correctly removed in some cases, making the database grow unnecessarily.
changelog_1032_li=When using MV_STORE\=TRUE and the SET CACHE_SIZE setting, the cache size was incorrectly set, so that it was effectively 1024 times smaller than it should be.
changelog_1033_li=MVStore\:the maximum cache size was artificially limited to 2 GB (due to an integer overflow).
changelog_1033_li=Concurrent CREATE TABLE... IF NOT EXISTS in the presence of MULTI_THREAD\=TRUE could throw an exception.
changelog_1034_li=MVStore / TransactionStore\:concurrent updates could result in a "Too many open transactions" exception.
changelog_1034_li=Fix bug in MVStore when creating lots of temporary tables, where we could run out of transaction IDs.
changelog_1035_li=StringUtils.toUpperEnglish now has a small cache. This should speed up reading from a ResultSet when using the column name.
changelog_1035_li=Add support for PostgreSQL STRING_AGG function. Patch by Fred Aquiles.
changelog_1036_li=MVStore\:up to 65535 open transactions are now supported. Previously, the limit was at most 65535 transactions between the oldest open and the newest open transaction (which was quite a strange limit).
changelog_1036_li=Fix bug in "jdbc\:h2\:nioMemFS" isRoot() function. Also, the page size was increased to 64 KB.
changelog_1037_li=The default limit for in-place LOB objects was changed from 128 to 256 bytes. This is because each read creates a reference to a LOB, and maintaining the references is a big overhead. With the higher limit, less references are needed.
changelog_1038_li=Tables without columns didn't work. (The use case for such tables is testing.)
changelog_1038_li=The Servlet API 3.0.1 is now used, instead of 2.4.
changelog_1039_li=The LIRS cache now resizes the table automatically in all cases and no longer needs the averageMemory configuration.
changelog_1039_li=MVStore\:old chunks no longer removed in append-only mode.
changelog_1040_li=Creating a linked table from an MVStore database to a non-MVStore database created a second (non-MVStore) database file.
changelog_1040_li=MVStore\:the cache for page references could grow far too big, resulting in out of memory in some cases.
changelog_1041_li=In version 1.4.184, a bug was introduced that broke queries that have both joins and wildcards, for example\:select * from dual join(select x from dual) on 1\=1
changelog_1041_li=MVStore\:orphaned lob objects were not correctly removed in some cases, making the database grow unnecessarily.
changelog_1042_li=Issue 598\:parser fails on timestamp "24\:00\:00.1234" - prevent the creation of out-of-range time values.
changelog_1042_li=MVStore\:the maximum cache size was artificially limited to 2 GB (due to an integer overflow).
changelog_1043_li=Allow declaring triggers as source code (like functions). Patch by Sylvain Cuaz.
changelog_1043_li=MVStore / TransactionStore\:concurrent updates could result in a "Too many open transactions" exception.
changelog_1044_li=Make the planner use indexes for sorting when doing a GROUP BY where all of the GROUP BY columns are not mentioned in the select. Patch by Frederico (zepfred).
changelog_1044_li=StringUtils.toUpperEnglish now has a small cache. This should speed up reading from a ResultSet when using the column name.
changelog_1045_li=PostgreSQL compatibility\:generate_series (as an alias for system_range). Patch by litailang.
changelog_1045_li=MVStore\:up to 65535 open transactions are now supported. Previously, the limit was at most 65535 transactions between the oldest open and the newest open transaction (which was quite a strange limit).
changelog_1046_li=Fix missing "column" type in right-hand parameter in ConditionIn. Patch by Arnaud Thimel.
changelog_1046_li=The default limit for in-place LOB objects was changed from 128 to 256 bytes. This is because each read creates a reference to a LOB, and maintaining the references is a big overhead. With the higher limit, less references are needed.
changelog_1047_li=Tables without columns didn't work. (The use case for such tables is testing.)
changelog_1048_li=In version 1.4.184, "group by" ignored the table name, and could pick a select column by mistake. Example\:select 0 as x from system_range(1, 2) d group by d.x;
changelog_1048_li=The LIRS cache now resizes the table automatically in all cases and no longer needs the averageMemory configuration.
changelog_1049_li=New connection setting "REUSE_SPACE" (default\:true). If disabled, all changes are appended to the database file, and existing content is never overwritten. This allows to rollback to a previous state of the database by truncating the database file.
changelog_1049_li=Creating a linked table from an MVStore database to a non-MVStore database created a second (non-MVStore) database file.
changelog_1050_li=Issue 587\:MVStore\:concurrent compaction and store operations could result in an IllegalStateException.
changelog_1050_li=In version 1.4.184, a bug was introduced that broke queries that have both joins and wildcards, for example\:select * from dual join(select x from dual) on 1\=1
changelog_1051_li=Issue 594\:Profiler.copyInThread does not work properly.
changelog_1051_li=Issue 598\:parser fails on timestamp "24\:00\:00.1234" - prevent the creation of out-of-range time values.
changelog_1052_li=Script tool\:Now, SCRIPT ... TO is always used (for higher speed and lower disk space usage).
changelog_1052_li=Allow declaring triggers as source code (like functions). Patch by Sylvain Cuaz.
changelog_1053_li=Script tool\:Fix parsing of BLOCKSIZE parameter, original patch by Ken Jorissen.
changelog_1053_li=Make the planner use indexes for sorting when doing a GROUP BY where all of the GROUP BY columns are not mentioned in the select. Patch by Frederico (zepfred).
changelog_1054_li=Fix bug in PageStore\#commit method - when the ignoreBigLog flag was set, the logic that cleared the flag could never be reached, resulting in performance degradation. Reported by Alexander Nesterov.
changelog_1054_li=PostgreSQL compatibility\:generate_series (as an alias for system_range). Patch by litailang.
changelog_1055_li=Issue 552\:Implement BIT_AND and BIT_OR aggregate functions.
changelog_1055_li=Fix missing "column" type in right-hand parameter in ConditionIn. Patch by Arnaud Thimel.
changelog_1057_li=In version 1.3.183, indexes were not used if the table contains columns with a default value generated by a sequence. This includes tables with identity and auto-increment columns. This bug was introduced by supporting "rownum" in views and derived tables.
changelog_1057_li=In version 1.4.184, "group by" ignored the table name, and could pick a select column by mistake. Example\:select 0 as x from system_range(1, 2) d group by d.x;
changelog_1058_li=MVStore\:imported BLOB and CLOB data sometimes disappeared. This was caused by a bug in the ObjectDataType comparison.
changelog_1058_li=New connection setting "REUSE_SPACE" (default\:true). If disabled, all changes are appended to the database file, and existing content is never overwritten. This allows to rollback to a previous state of the database by truncating the database file.
changelog_1059_li=Reading from a StreamStore now throws an IOException if the underlying data doesn't exist.
changelog_1059_li=Issue 587\:MVStore\:concurrent compaction and store operations could result in an IllegalStateException.
changelog_1060_li=MVStore\:if there is an exception while saving, the store is now in all cases immediately closed.
changelog_1060_li=Issue 594\:Profiler.copyInThread does not work properly.
changelog_1061_li=MVStore\:the dump tool could go into an endless loop for some files.
changelog_1061_li=Script tool\:Now, SCRIPT ... TO is always used (for higher speed and lower disk space usage).
changelog_1062_li=MVStore\:recovery for a database with many CLOB or BLOB entries is now much faster.
changelog_1062_li=Script tool\:Fix parsing of BLOCKSIZE parameter, original patch by Ken Jorissen.
changelog_1063_li=Group by with a quoted select column name alias didn't work. Example\:select 1 "a" from dual group by "a"
changelog_1063_li=Fix bug in PageStore\#commit method - when the ignoreBigLog flag was set, the logic that cleared the flag could never be reached, resulting in performance degradation. Reported by Alexander Nesterov.
changelog_1064_li=Auto-server mode\:the host name is now stored in the .lock.db file.
changelog_1064_li=Issue 552\:Implement BIT_AND and BIT_OR aggregate functions.
changelog_1066_li=MVStore\:the default auto-commit buffer size is now about twice as big. This should reduce the database file size after inserting a lot of data.
changelog_1066_li=In version 1.3.183, indexes were not used if the table contains columns with a default value generated by a sequence. This includes tables with identity and auto-increment columns. This bug was introduced by supporting "rownum" in views and derived tables.
changelog_1067_li=The built-in functions "power" and "radians" now always return a double.
changelog_1067_li=MVStore\:imported BLOB and CLOB data sometimes disappeared. This was caused by a bug in the ObjectDataType comparison.
changelog_1068_li=Using "row_number" or "rownum" in views or derived tables had unexpected results if the outer query contained constraints for the given view. Example\:select b.nr, b.id from (select row_number() over() as nr, a.id as id from (select id from test order by name) as a) as b where b.id \=1
changelog_1068_li=Reading from a StreamStore now throws an IOException if the underlying data doesn't exist.
changelog_1069_li=MVStore\:the Recover tool can now deal with more types of corruption in the file.
changelog_1069_li=MVStore\:if there is an exception while saving, the store is now in all cases immediately closed.
changelog_1070_li=MVStore\:the TransactionStore now first needs to be initialized before it can be used.
changelog_1070_li=MVStore\:the dump tool could go into an endless loop for some files.
changelog_1071_li=Views and derived tables with equality and range conditions on the same columns did not work properly. example\:select x from (select x from (select 1 as x) where x > 0 and x < 2) where x \=1
changelog_1071_li=MVStore\:recovery for a database with many CLOB or BLOB entries is now much faster.
changelog_1072_li=The database URL setting PAGE_SIZE setting is now also used for the MVStore.
changelog_1072_li=Group by with a quoted select column name alias didn't work. Example\:select 1 "a" from dual group by "a"
changelog_1073_li=MVStore\:the default page split size for persistent stores is now 4096 (it was 16 KB so far). This should reduce the database file size for most situations (in some cases, less than half the size of the previous version).
changelog_1073_li=Auto-server mode\:the host name is now stored in the .lock.db file.
changelog_1074_li=With query literals disabled, auto-analyze of a table with CLOB or BLOB did not work.
changelog_1075_li=MVStore\:use a mark and sweep GC algorithm instead of reference counting, to ensure used chunks are never overwrite, even if the reference counting algorithm does not work properly.
changelog_1075_li=MVStore\:the default auto-commit buffer size is now about twice as big. This should reduce the database file size after inserting a lot of data.
changelog_1076_li=In the multi-threaded mode, updating the column selectivity ("analyze") in the background sometimes did not work.
changelog_1076_li=The built-in functions "power" and "radians" now always return a double.
changelog_1077_li=In the multi-threaded mode, database metadata operations did sometimes not work if the schema was changed at the same time (for example, if tables were dropped).
changelog_1077_li=Using "row_number" or "rownum" in views or derived tables had unexpected results if the outer query contained constraints for the given view. Example\:select b.nr, b.id from (select row_number() over() as nr, a.id as id from (select id from test order by name) as a) as b where b.id \=1
changelog_1078_li=Some CLOB and BLOB values could no longer be read when the original row was removed (even when using the MVCC mode).
changelog_1078_li=MVStore\:the Recover tool can now deal with more types of corruption in the file.
changelog_1079_li=The MVStoreTool could throw an IllegalArgumentException.
changelog_1079_li=MVStore\:the TransactionStore now first needs to be initialized before it can be used.
changelog_1080_li=Improved performance for some date / time / timestamp conversion operations. Thanks to Sergey Evdokimov for reporting the problem.
changelog_1080_li=Views and derived tables with equality and range conditions on the same columns did not work properly. example\:select x from (select x from (select 1 as x) where x > 0 and x < 2) where x \=1
changelog_1081_li=H2 Console\:the built-in web server did not work properly if an unknown file was requested.
changelog_1081_li=The database URL setting PAGE_SIZE setting is now also used for the MVStore.
changelog_1082_li=MVStore\:the jar file is renamed to "h2-mvstore-*.jar" and is deployed to Maven separately.
changelog_1082_li=MVStore\:the default page split size for persistent stores is now 4096 (it was 16 KB so far). This should reduce the database file size for most situations (in some cases, less than half the size of the previous version).
changelog_1083_li=MVStore\:support for concurrent reads and writes is now enabled by default.
changelog_1083_li=With query literals disabled, auto-analyze of a table with CLOB or BLOB did not work.
changelog_1084_li=Server mode\:the transfer buffer size has been changed from 16 KB to 64 KB, after it was found that this improves performance on Linux quite a lot.
changelog_1084_li=MVStore\:use a mark and sweep GC algorithm instead of reference counting, to ensure used chunks are never overwrite, even if the reference counting algorithm does not work properly.
changelog_1085_li=H2 Console and server mode\:SSL is now disabled and TLS is used to protect against the Poodle SSLv3 vulnerability. The system property to disable secure anonymous connections is now "h2.enableAnonymousTLS". The default certificate is still self-signed, so you need to manually install another one if you want to avoid man in the middle attacks.
changelog_1085_li=In the multi-threaded mode, updating the column selectivity ("analyze") in the background sometimes did not work.
changelog_1086_li=MVStore\:the R-tree did not correctly measure the memory usage.
changelog_1086_li=In the multi-threaded mode, database metadata operations did sometimes not work if the schema was changed at the same time (for example, if tables were dropped).
changelog_1087_li=MVStore\:compacting a store with an R-tree did not always work.
changelog_1087_li=Some CLOB and BLOB values could no longer be read when the original row was removed (even when using the MVCC mode).
changelog_1088_li=Issue 581\:When running in LOCK_MODE\=0, JdbcDatabaseMetaData\#supportsTransactionIsolationLevel(TRANSACTION_READ_UNCOMMITTED) should return false
changelog_1088_li=The MVStoreTool could throw an IllegalArgumentException.
changelog_1089_li=Fix bug which could generate deadlocks when multiple connections accessed the same table.
changelog_1089_li=Improved performance for some date / time / timestamp conversion operations. Thanks to Sergey Evdokimov for reporting the problem.
changelog_1090_li=Some places in the code were not respecting the value set in the "SET MAX_MEMORY_ROWS x" command
changelog_1090_li=H2 Console\:the built-in web server did not work properly if an unknown file was requested.
changelog_1091_li=Fix bug which could generate a NegativeArraySizeException when performing large (>40M) row union operations
changelog_1091_li=MVStore\:the jar file is renamed to "h2-mvstore-*.jar" and is deployed to Maven separately.
changelog_1092_li=Fix "USE schema" command for MySQL compatibility, patch by mfulton
changelog_1092_li=MVStore\:support for concurrent reads and writes is now enabled by default.
changelog_1093_li=Parse and ignore the ROW_FORMAT\=DYNAMIC MySQL syntax, patch by mfulton
changelog_1093_li=Server mode\:the transfer buffer size has been changed from 16 KB to 64 KB, after it was found that this improves performance on Linux quite a lot.
changelog_1094_li=H2 Console and server mode\:SSL is now disabled and TLS is used to protect against the Poodle SSLv3 vulnerability. The system property to disable secure anonymous connections is now "h2.enableAnonymousTLS". The default certificate is still self-signed, so you need to manually install another one if you want to avoid man in the middle attacks.
changelog_1095_li=MVStore\:improved error messages and logging; improved behavior if there is an error when serializing objects.
changelog_1095_li=MVStore\:the R-tree did not correctly measure the memory usage.
changelog_1096_li=OSGi\:the MVStore packages are now exported.
changelog_1096_li=MVStore\:compacting a store with an R-tree did not always work.
changelog_1097_li=With the MVStore option, when using multiple threads that concurrently create indexes or tables, it was relatively easy to get a lock timeout on the "SYS" table.
changelog_1097_li=Issue 581\:When running in LOCK_MODE\=0, JdbcDatabaseMetaData\#supportsTransactionIsolationLevel(TRANSACTION_READ_UNCOMMITTED) should return false
changelog_1098_li=When using the multi-threaded option, the exception "Unexpected code path" could be thrown, specially if the option "analyze_auto" was set to a low value.
changelog_1098_li=Fix bug which could generate deadlocks when multiple connections accessed the same table.
changelog_1099_li=In the server mode, when reading from a CLOB or BLOB, if the connection was closed, a NullPointerException could be thrown instead of an exception saying the connection is closed.
changelog_1099_li=Some places in the code were not respecting the value set in the "SET MAX_MEMORY_ROWS x" command
changelog_1100_li=DatabaseMetaData.getProcedures and getProcedureColumns could throw an exception if a user defined class is not available.
changelog_1100_li=Fix bug which could generate a NegativeArraySizeException when performing large (>40M) row union operations
changelog_1101_li=Issue 584\:the error message for a wrong sequence definition was wrong.
changelog_1101_li=Fix "USE schema" command for MySQL compatibility, patch by mfulton
changelog_1102_li=CSV tool\:the rowSeparator option is no longer supported, as the same can be achieved with the lineSeparator.
changelog_1102_li=Parse and ignore the ROW_FORMAT\=DYNAMIC MySQL syntax, patch by mfulton
changelog_1103_li=Descending indexes on MVStore tables did not work properly.
changelog_1104_li=Issue 579\:Conditions on the "_rowid_" pseudo-column didn't use an index when using the MVStore.
changelog_1104_li=MVStore\:improved error messages and logging; improved behavior if there is an error when serializing objects.
changelog_1105_li=Fixed documentation that "offset" and "fetch" are also keywords since version 1.4.x.
changelog_1105_li=OSGi\:the MVStore packages are now exported.
changelog_1106_li=The Long.MIN_VALUE could not be parsed for auto-increment (identity) columns.
changelog_1106_li=With the MVStore option, when using multiple threads that concurrently create indexes or tables, it was relatively easy to get a lock timeout on the "SYS" table.
changelog_1107_li=Issue 573\:Add implementation for Methods "isWrapperFor()" and "unwrap()" in other JDBC classes.
changelog_1107_li=When using the multi-threaded option, the exception "Unexpected code path" could be thrown, specially if the option "analyze_auto" was set to a low value.
changelog_1108_li=Issue 572\:MySQL compatibility for "order by" in update statements.
changelog_1108_li=In the server mode, when reading from a CLOB or BLOB, if the connection was closed, a NullPointerException could be thrown instead of an exception saying the connection is closed.
changelog_1109_li=The change in JDBC escape processing in version 1.4.181 affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax "{t 'time}", or "{ts 'timestamp'}", or "{d 'data'}", then both the client and the server need to be upgraded to version 1.4.181 or later.
changelog_1109_li=DatabaseMetaData.getProcedures and getProcedureColumns could throw an exception if a user defined class is not available.
changelog_1110_li=Issue 584\:the error message for a wrong sequence definition was wrong.
changelog_1111_li=Improved MySQL compatibility by supporting "use schema". Thanks a lot to Karl Pietrzak for the patch\!
changelog_1111_li=CSV tool\:the rowSeparator option is no longer supported, as the same can be achieved with the lineSeparator.
changelog_1112_li=Writing to the trace file is now faster, specially with the debug level.
changelog_1112_li=Descending indexes on MVStore tables did not work properly.
changelog_1113_li=The database option "defrag_always\=true" did not work with the MVStore.
changelog_1113_li=Issue 579\:Conditions on the "_rowid_" pseudo-column didn't use an index when using the MVStore.
changelog_1114_li=The JDBC escape syntax {ts 'value'} did not interpret the value as a timestamp. The same for {d 'value'} (for date) and {t 'value'} (for time). Thanks to Lukas Eder for reporting the issue. The following problem was detected after version 1.4.181 was released\:The change in JDBC escape processing affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax {t 'time'}, or {ts 'timestamp'}, or {d 'date'}, then both the client and the server need to be upgraded to version 1.4.181 or later.
changelog_1114_li=Fixed documentation that "offset" and "fetch" are also keywords since version 1.4.x.
changelog_1115_li=File system abstraction\:support replacing existing files using move (currently not for Windows).
changelog_1115_li=The Long.MIN_VALUE could not be parsed for auto-increment (identity) columns.
changelog_1116_li=The statement "shutdown defrag" now compresses the database (with the MVStore). This command can greatly reduce the file size, and is relatively fast, but is not incremental.
changelog_1116_li=Issue 573\:Add implementation for Methods "isWrapperFor()" and "unwrap()" in other JDBC classes.
changelog_1117_li=The MVStore now automatically compacts the store in the background if there is no read or write activity, which should (after some time; sometimes about one minute) reduce the file size. This is still work in progress, feedback is welcome\!
changelog_1117_li=Issue 572\:MySQL compatibility for "order by" in update statements.
changelog_1118_li=Change default value of PAGE_SIZE from 2048 to 4096 to more closely match most file systems block size (PageStore only; the MVStore already used 4096).
changelog_1118_li=The change in JDBC escape processing in version 1.4.181 affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax "{t 'time}", or "{ts 'timestamp'}", or "{d 'data'}", then both the client and the server need to be upgraded to version 1.4.181 or later.
changelog_1119_li=Auto-scale MAX_MEMORY_ROWS and CACHE_SIZE settings by the amount of available RAM. Gives a better out of box experience for people with more powerful machines.
changelog_1122_li=The database option "defrag_always\=true" did not work with the MVStore.
changelog_1123_li=MVStore\:the store is now auto-compacted automatically up to some point, to avoid very large file sizes. This area is still work in progress.
changelog_1123_li=The JDBC escape syntax {ts 'value'} did not interpret the value as a timestamp. The same for {d 'value'} (for date) and {t 'value'} (for time). Thanks to Lukas Eder for reporting the issue. The following problem was detected after version 1.4.181 was released\:The change in JDBC escape processing affects both the parser (which is running on the server) and the JDBC API (which is running on the client). If you (or a tool you use) use the syntax {t 'time'}, or {ts 'timestamp'}, or {d 'date'}, then both the client and the server need to be upgraded to version 1.4.181 or later.
changelog_1124_li=Sequences of temporary tables (auto-increment or identity columns) were persisted unnecessarily in the database file, and were not removed when re-opening the database.
changelog_1124_li=File system abstraction\:support replacing existing files using move (currently not for Windows).
changelog_1125_li=MVStore\:an IndexOutOfBoundsException could sometimes occur MVMap.openVersion when concurrently accessing the store.
changelog_1125_li=The statement "shutdown defrag" now compresses the database (with the MVStore). This command can greatly reduce the file size, and is relatively fast, but is not incremental.
changelog_1126_li=The LIRS cache now re-sizes the internal hash map if needed.
changelog_1126_li=The MVStore now automatically compacts the store in the background if there is no read or write activity, which should (after some time; sometimes about one minute) reduce the file size. This is still work in progress, feedback is welcome\!
changelog_1127_li=Optionally persist session history in the H2 console. (patch from Martin Grajcar)
changelog_1127_li=Change default value of PAGE_SIZE from 2048 to 4096 to more closely match most file systems block size (PageStore only; the MVStore already used 4096).
changelog_1128_li=Add client-info property to get the number of servers currently in the cluster and which servers that are available. (patch from Nikolaj Fogh)
changelog_1128_li=Auto-scale MAX_MEMORY_ROWS and CACHE_SIZE settings by the amount of available RAM. Gives a better out of box experience for people with more powerful machines.
changelog_1129_li=Fix bug in changing encrypted DB password that kept the file handle open when the wrong password was supplied. (test case from Jens Hohmuth).
changelog_1129_li=Handle tabs like 4 spaces in web console, patch by Martin Grajcar.
changelog_1130_li=Issue 567\:H2 hangs for a long time then (sometimes) recovers. Introduce a queue when doing table locking to prevent session starvation.
changelog_1130_li=Issue 573\:Add implementation for Methods "isWrapperFor()" and "unwrap()" in JdbcConnection.java, patch by BigMichi1.
changelog_1132_li=The license was changed to MPL 2.0 (from 1.0) and EPL 1.0.
changelog_1132_li=MVStore\:the store is now auto-compacted automatically up to some point, to avoid very large file sizes. This area is still work in progress.
changelog_1133_li=Issue 565\:MVStore\:concurrently adding LOB objects (with MULTI_THREADED option) resulted in a NullPointerException.
changelog_1133_li=Sequences of temporary tables (auto-increment or identity columns) were persisted unnecessarily in the database file, and were not removed when re-opening the database.
changelog_1134_li=MVStore\:reduced dependencies to other H2 classes.
changelog_1134_li=MVStore\:an IndexOutOfBoundsException could sometimes occur MVMap.openVersion when concurrently accessing the store.
changelog_1135_li=There was a way to prevent a database from being re-opened, by creating a column constraint that references a table with a higher id, for example with "check" constraints that contains queries. This is now detected, and creating the table is prohibited. In future versions of H2, most likely creating references to other tables will no longer be supported because of such problems.
changelog_1135_li=The LIRS cache now re-sizes the internal hash map if needed.
changelog_1136_li=MVStore\:descending indexes with "nulls first" did not work as expected (null was ordered last).
changelog_1136_li=Optionally persist session history in the H2 console. (patch from Martin Grajcar)
changelog_1137_li=Large result sets now always create temporary tables instead of temporary files.
changelog_1137_li=Add client-info property to get the number of servers currently in the cluster and which servers that are available. (patch from Nikolaj Fogh)
changelog_1138_li=When using the PageStore, opening a database failed in some cases with a NullPointerException if temporary tables were used (explicitly, or implicitly when using large result sets).
changelog_1138_li=Fix bug in changing encrypted DB password that kept the file handle open when the wrong password was supplied. (test case from Jens Hohmuth).
changelog_1139_li=If a database file in the PageStore file format exists, this file and this mode is now used, even if the database URL does not contain "MV_STORE\=FALSE". If a MVStore file exists, it is used.
changelog_1139_li=Issue 567\:H2 hangs for a long time then (sometimes) recovers. Introduce a queue when doing table locking to prevent session starvation.
changelog_1140_li=Databases created with version 1.3.175 and earlier that contained foreign keys in combination with multi-column indexes could not be opened in some cases. This was due to a bugfix in version 1.3.176\:Referential integrity constraints sometimes used the wrong index.
changelog_1141_li=MVStore\:the ObjectDataType comparison method was incorrect if one key was Serializable and the other was of a common class.
changelog_1141_li=The license was changed to MPL 2.0 (from 1.0) and EPL 1.0.
changelog_1142_li=Recursive queries with many result rows (more than the setting "max_memory_rows") did not work correctly.
changelog_1142_li=Issue 565\:MVStore\:concurrently adding LOB objects (with MULTI_THREADED option) resulted in a NullPointerException.
changelog_1143_li=The license has changed to MPL 2.0 + EPL 1.0.
changelog_1143_li=MVStore\:reduced dependencies to other H2 classes.
changelog_1144_li=MVStore\:temporary tables from result sets could survive re-opening a database, which could result in a ClassCastException.
changelog_1144_li=There was a way to prevent a database from being re-opened, by creating a column constraint that references a table with a higher id, for example with "check" constraints that contains queries. This is now detected, and creating the table is prohibited. In future versions of H2, most likely creating references to other tables will no longer be supported because of such problems.
changelog_1145_li=Issue 566\:MVStore\:unique indexes that were created later on did not work correctly if there were over 5000 rows in the table. Existing databases need to be re-created (at least the broken index need to be re-built).
changelog_1145_li=MVStore\:descending indexes with "nulls first" did not work as expected (null was ordered last).
changelog_1146_li=MVStore\:creating secondary indexes on large tables results in missing rows in the index.
changelog_1146_li=Large result sets now always create temporary tables instead of temporary files.
changelog_1147_li=Metadata\:the password of linked tables is now only visible for admin users.
changelog_1147_li=When using the PageStore, opening a database failed in some cases with a NullPointerException if temporary tables were used (explicitly, or implicitly when using large result sets).
changelog_1148_li=For Windows, database URLs of the form "jdbc\:h2\:/test" where considered relative and did not work unless the system property "h2.implicitRelativePath" was used.
changelog_1148_li=If a database file in the PageStore file format exists, this file and this mode is now used, even if the database URL does not contain "MV_STORE\=FALSE". If a MVStore file exists, it is used.
changelog_1149_li=Windows\:using a base directory of "C\:/" and similar did not work as expected.
changelog_1149_li=Databases created with version 1.3.175 and earlier that contained foreign keys in combination with multi-column indexes could not be opened in some cases. This was due to a bugfix in version 1.3.176\:Referential integrity constraints sometimes used the wrong index.
changelog_1150_li=Follow JDBC specification on Procedures MetaData, use P0 as return type of procedure.
changelog_1150_li=MVStore\:the ObjectDataType comparison method was incorrect if one key was Serializable and the other was of a common class.
changelog_1151_li=Issue 531\:IDENTITY ignored for added column.
changelog_1151_li=Recursive queries with many result rows (more than the setting "max_memory_rows") did not work correctly.
changelog_1152_li=FileSystem\:improve exception throwing compatibility with JDK
changelog_1152_li=The license has changed to MPL 2.0 + EPL 1.0.
changelog_1153_li=Spatial Index\:adjust costs so we do not use the spatial index if the query does not contain an intersects operator.
changelog_1153_li=MVStore\:temporary tables from result sets could survive re-opening a database, which could result in a ClassCastException.
changelog_1154_li=Fix multi-threaded deadlock when using a View that includes a TableFunction.
changelog_1154_li=Issue 566\:MVStore\:unique indexes that were created later on did not work correctly if there were over 5000 rows in the table. Existing databases need to be re-created (at least the broken index need to be re-built).
changelog_1155_li=Fix bug in dividing very-small BigDecimal numbers.
changelog_1155_li=MVStore\:creating secondary indexes on large tables results in missing rows in the index.
changelog_1156_li=Metadata\:the password of linked tables is now only visible for admin users.
changelog_1157_li=Issue 559\:Make dependency on org.osgi.service.jdbc optional.
changelog_1157_li=For Windows, database URLs of the form "jdbc\:h2\:/test" where considered relative and did not work unless the system property "h2.implicitRelativePath" was used.
changelog_1158_li=Improve error message when the user specifies an unsupported combination of database settings.
changelog_1158_li=Windows\:using a base directory of "C\:/" and similar did not work as expected.
changelog_1159_li=MVStore\:in the multi-threaded mode, NullPointerException and other exceptions could occur.
changelog_1159_li=Follow JDBC specification on Procedures MetaData, use P0 as return type of procedure.
changelog_1160_li=MVStore\:some database file could not be compacted due to a bug in the bookkeeping of the fill rate. Also, database file were compacted quite slowly. This has been improved; but more changes in this area are expected.
changelog_1160_li=Issue 531\:IDENTITY ignored for added column.
changelog_1161_li=MVStore\:support for volatile maps (that don't store changes).
changelog_1161_li=FileSystem\:improve exception throwing compatibility with JDK
changelog_1162_li=MVStore mode\:in-memory databases now also use the MVStore.
changelog_1162_li=Spatial Index\:adjust costs so we do not use the spatial index if the query does not contain an intersects operator.
changelog_1163_li=In server mode, appending ";autocommit\=false" to the database URL was working, but the return value of Connection.getAutoCommit() was wrong.
changelog_1163_li=Fix multi-threaded deadlock when using a View that includes a TableFunction.
changelog_1164_li=Issue 561\:OSGi\:the import package declaration of org.h2 excluded version 1.4.
changelog_1164_li=Fix bug in dividing very-small BigDecimal numbers.
changelog_1165_li=Issue 558\:with the MVStore, a NullPointerException could occur when using LOBs at session commit (LobStorageMap.removeLob).
changelog_1166_li=Remove the "h2.MAX_MEMORY_ROWS_DISTINCT" system property to reduce confusion. We already have the MAX_MEMORY_ROWS setting which does a very similar thing, and is better documented.
changelog_1166_li=Issue 559\:Make dependency on org.osgi.service.jdbc optional.
changelog_1167_li=Issue 554\:Web Console in an IFrame was not fully supported.
changelog_1167_li=Improve error message when the user specifies an unsupported combination of database settings.
changelog_1168_li=MVStore\:in the multi-threaded mode, NullPointerException and other exceptions could occur.
changelog_1169_li=By default, the MV_STORE option is enabled, so it is using the new MVStore storage. The MVCC setting is by default set to the same values as the MV_STORE setting, so it is also enabled by default. For testing, both settings can be disabled by appending ";MV_STORE\=FALSE" and/or ";MVCC\=FALSE" to the database URL.
changelog_1169_li=MVStore\:some database file could not be compacted due to a bug in the bookkeeping of the fill rate. Also, database file were compacted quite slowly. This has been improved; but more changes in this area are expected.
changelog_1170_li=The file locking method 'serialized' is no longer supported. This mode might return in a future version, however this is not clear right now. A new implementation and new tests would be needed.
changelog_1170_li=MVStore\:support for volatile maps (that don't store changes).
changelog_1171_li=Enable the new storage format for dates (system property "h2.storeLocalTime"). For the MVStore mode, this is always enabled, but with version 1.4 this is even enabled in the PageStore mode.
changelog_1171_li=MVStore mode\:in-memory databases now also use the MVStore.
changelog_1172_li=Implicit relative paths are disabled (system property "h2.implicitRelativePath"), so that the database URL jdbc\:h2\:test now needs to be written as jdbc\:h2\:./test.
changelog_1172_li=In server mode, appending ";autocommit\=false" to the database URL was working, but the return value of Connection.getAutoCommit() was wrong.
changelog_1173_li="select ... fetch first 1 row only"is supported with the regular mode. This was disabled so far because "fetch" and "offset" are now keywords. See also Mode.supportOffsetFetch.
changelog_1173_li=Issue 561\:OSGi\:the import package declaration of org.h2 excluded version 1.4.
changelog_1174_li=Byte arrays are now sorted in unsigned mode (x'99' is larger than x'09'). (System property "h2.sortBinaryUnsigned", Mode.binaryUnsigned, setting "binary_collation").
changelog_1174_li=Issue 558\:with the MVStore, a NullPointerException could occur when using LOBs at session commit (LobStorageMap.removeLob).
changelog_1175_li=Csv.getInstance will be removed in future versions of 1.4. Use the public constructor instead.
changelog_1175_li=Remove the "h2.MAX_MEMORY_ROWS_DISTINCT" system property to reduce confusion. We already have the MAX_MEMORY_ROWS setting which does a very similar thing, and is better documented.
changelog_1176_li=Remove support for the limited old-style outer join syntax using "(+)". Use "outer join" instead. System property "h2.oldStyleOuterJoin".
changelog_1176_li=Issue 554\:Web Console in an IFrame was not fully supported.
changelog_1177_li=Support the data type "DATETIME2" as an alias for "DATETIME", for MS SQL Server compatibility.
changelog_1178_li=Add Oracle-compatible TRANSLATE function, patch by Eric Chatellier.
changelog_1178_li=By default, the MV_STORE option is enabled, so it is using the new MVStore storage. The MVCC setting is by default set to the same values as the MV_STORE setting, so it is also enabled by default. For testing, both settings can be disabled by appending ";MV_STORE\=FALSE" and/or ";MVCC\=FALSE" to the database URL.
changelog_1179_h2=Version 1.3.176 (2014-04-05)
changelog_1179_li=The file locking method 'serialized' is no longer supported. This mode might return in a future version, however this is not clear right now. A new implementation and new tests would be needed.
changelog_1180_li=The file locking method 'serialized' is no longer documented, as it will not be available in version 1.4.
changelog_1180_li=Enable the new storage format for dates (system property "h2.storeLocalTime"). For the MVStore mode, this is always enabled, but with version 1.4 this is even enabled in the PageStore mode.
changelog_1181_li=The static method Csv.getInstance() was removed. Use the public constructor instead.
changelog_1181_li=Implicit relative paths are disabled (system property "h2.implicitRelativePath"), so that the database URL jdbc\:h2\:test now needs to be written as jdbc\:h2\:./test.
changelog_1182_li=The default user name for the Script, RunScript, Shell, and CreateCluster tools are no longer "sa" but an empty string.
changelog_1182_li="select ... fetch first 1 row only"is supported with the regular mode. This was disabled so far because "fetch" and "offset" are now keywords. See also Mode.supportOffsetFetch.
changelog_1183_li=The stack trace of the exception "The object is already closed" is no longer logged by default.
changelog_1183_li=Byte arrays are now sorted in unsigned mode (x'99' is larger than x'09'). (System property "h2.sortBinaryUnsigned", Mode.binaryUnsigned, setting "binary_collation").
changelog_1184_li=If a value of a result set was itself a result set, the result could only be read once.
changelog_1184_li=Csv.getInstance will be removed in future versions of 1.4. Use the public constructor instead.
changelog_1185_li=Column constraints are also visible in views (patch from Nicolas Fortin for H2GIS).
changelog_1185_li=Remove support for the limited old-style outer join syntax using "(+)". Use "outer join" instead. System property "h2.oldStyleOuterJoin".
changelog_1186_li=Granting a additional right to a role that already had a right for that table was not working.
changelog_1186_li=Support the data type "DATETIME2" as an alias for "DATETIME", for MS SQL Server compatibility.
changelog_1187_li=Spatial index\:a few bugs have been fixed (using spatial constraints in views, transferring geometry objects over TCP/IP, the returned geometry object is copied when needed).
changelog_1187_li=Add Oracle-compatible TRANSLATE function, patch by Eric Chatellier.
changelog_1188_li=Issue 551\:the datatype documentation was incorrect (found by Bernd Eckenfels).
changelog_1188_h2=Version 1.3.176 (2014-04-05)
changelog_1189_li=Issue 368\:ON DUPLICATE KEY UPDATE did not work for multi-row inserts. Test case from Angus Macdonald.
changelog_1189_li=The file locking method 'serialized' is no longer documented, as it will not be available in version 1.4.
changelog_1190_li=OSGi\:the package javax.tools is now imported (as an optional).
changelog_1190_li=The static method Csv.getInstance() was removed. Use the public constructor instead.
changelog_1191_li=H2 Console\:auto-complete is now disabled by default, but there is a hot-key (Ctrl+Space).
changelog_1191_li=The default user name for the Script, RunScript, Shell, and CreateCluster tools are no longer "sa" but an empty string.
changelog_1192_li=H2 Console\:auto-complete did not work with multi-line statements.
changelog_1192_li=The stack trace of the exception "The object is already closed" is no longer logged by default.
changelog_1193_li=CLOB and BLOB data was not immediately removed after a rollback.
changelog_1193_li=If a value of a result set was itself a result set, the result could only be read once.
changelog_1194_li=There is a new Aggregate API that supports the internal H2 data types (GEOMETRY for example). Thanks a lot to Nicolas Fortin for the patch\!
changelog_1194_li=Column constraints are also visible in views (patch from Nicolas Fortin for H2GIS).
changelog_1195_li=Referential integrity constraints sometimes used the wrong index, such that updating a row in the referenced table incorrectly failed with a constraint violation.
changelog_1195_li=Granting a additional right to a role that already had a right for that table was not working.
changelog_1196_li=The Polish translation was completed and corrected by Wojtek Jurczyk. Thanks a lot\!
changelog_1196_li=Spatial index\:a few bugs have been fixed (using spatial constraints in views, transferring geometry objects over TCP/IP, the returned geometry object is copied when needed).
changelog_1197_li=Issue 545\:Unnecessary duplicate code was removed.
changelog_1197_li=Issue 551\:the datatype documentation was incorrect (found by Bernd Eckenfels).
changelog_1198_li=The profiler tool can now process files with full thread dumps.
changelog_1198_li=Issue 368\:ON DUPLICATE KEY UPDATE did not work for multi-row inserts. Test case from Angus Macdonald.
changelog_1199_li=MVStore\:the file format was changed slightly.
changelog_1199_li=OSGi\:the package javax.tools is now imported (as an optional).
changelog_1200_li=MVStore mode\:the CLOB and BLOB storage was re-implemented and is now much faster than with the PageStore (which is still the default storage).
changelog_1200_li=H2 Console\:auto-complete is now disabled by default, but there is a hot-key (Ctrl+Space).
changelog_1201_li=MVStore mode\:creating indexes is now much faster (in many cases faster than with the default PageStore).
changelog_1201_li=H2 Console\:auto-complete did not work with multi-line statements.
changelog_1202_li=Various bugs in the MVStore storage and have been fixed, including a bug in the R-tree implementation. The database could get corrupt if there were transient IO exceptions while storing.
changelog_1202_li=CLOB and BLOB data was not immediately removed after a rollback.
changelog_1203_li=The method org.h2.expression.Function.getCost could throw a NullPointException.
changelog_1203_li=There is a new Aggregate API that supports the internal H2 data types (GEOMETRY for example). Thanks a lot to Nicolas Fortin for the patch\!
changelog_1204_li=Storing LOBs in separate files (outside of the main database file) is no longer supported for new databases.
changelog_1204_li=Referential integrity constraints sometimes used the wrong index, such that updating a row in the referenced table incorrectly failed with a constraint violation.
changelog_1205_li=Lucene 2 is no longer supported.
changelog_1205_li=The Polish translation was completed and corrected by Wojtek Jurczyk. Thanks a lot\!
changelog_1206_li=Fix bug in calculating default MIN and MAX values for SEQUENCE.
changelog_1206_li=Issue 545\:Unnecessary duplicate code was removed.
changelog_1207_li=Fix bug in performing IN queries with multiple values when IGNORECASE\=TRUE
changelog_1207_li=The profiler tool can now process files with full thread dumps.
changelog_1208_li=Add entry-point to org.h2.tools.Shell so it can be called from inside an application. patch by Thomas Gillet.
changelog_1208_li=MVStore\:the file format was changed slightly.
changelog_1209_li=Fix bug that prevented the PgServer from being stopped and started multiple times.
changelog_1209_li=MVStore mode\:the CLOB and BLOB storage was re-implemented and is now much faster than with the PageStore (which is still the default storage).
changelog_1210_li=Support some more DDL syntax for MySQL, patch from Peter Jentsch.
changelog_1210_li=MVStore mode\:creating indexes is now much faster (in many cases faster than with the default PageStore).
changelog_1211_li=Issue 548\:TO_CHAR does not format MM and DD correctly when the month or day of the month is 1 digit, patch from "the.tucc"
changelog_1211_li=Various bugs in the MVStore storage and have been fixed, including a bug in the R-tree implementation. The database could get corrupt if there were transient IO exceptions while storing.
changelog_1212_li=Fix bug in varargs support in ALIAS's, patch from Nicolas Fortin
changelog_1212_li=The method org.h2.expression.Function.getCost could throw a NullPointException.
changelog_1213_li=Storing LOBs in separate files (outside of the main database file) is no longer supported for new databases.
changelog_1214_li=Lucene 2 is no longer supported.
changelog_1215_li=Fix bug in calculating default MIN and MAX values for SEQUENCE.
changelog_1216_li=Fix bug in performing IN queries with multiple values when IGNORECASE\=TRUE
changelog_1217_li=Add entry-point to org.h2.tools.Shell so it can be called from inside an application. patch by Thomas Gillet.
changelog_1218_li=Fix bug that prevented the PgServer from being stopped and started multiple times.
changelog_1219_li=Support some more DDL syntax for MySQL, patch from Peter Jentsch.
changelog_1220_li=Issue 548\:TO_CHAR does not format MM and DD correctly when the month or day of the month is 1 digit, patch from "the.tucc"
changelog_1221_li=Fix bug in varargs support in ALIAS's, patch from Nicolas Fortin
cheatSheet_1000_h1=H2 Database Engine Cheat Sheet
cheatSheet_1000_h1=H2 Database Engine Cheat Sheet
cheatSheet_1001_h2=Using H2
cheatSheet_1001_h2=Using H2
cheatSheet_1002_a=H2
cheatSheet_1002_a=H2
cheatSheet_1003_li=\ is <a href\="http\://code.google.com/p/h2database/source">open source</a>, <a href\="license.html">free to use and distribute</a>.
cheatSheet_1003_li=\ is <a href\="https\://github.com/h2database/h2database">open source</a>, <a href\="license.html">free to use and distribute</a>.
cheatSheet_1006_li=To start the <a href\="quickstart.html\#h2_console">H2 Console tool</a>, double click the jar file, or run <code>java -jar h2*.jar</code>, <code>h2.bat</code>, or <code>h2.sh</code>.
cheatSheet_1006_li=To start the <a href\="quickstart.html\#h2_console">H2 Console tool</a>, double click the jar file, or run <code>java -jar h2*.jar</code>, <code>h2.bat</code>, or <code>h2.sh</code>.
...
@@ -896,7 +908,7 @@ download_1003_a=Platform-Independent Zip
...
@@ -896,7 +908,7 @@ download_1003_a=Platform-Independent Zip
download_1004_h3=Version 1.3.176 (2014-04-05), Last Stable
download_1004_h3=Version 1.3.176 (2014-04-05), Last Stable
download_1005_a=Windows Installer
download_1005_a=Windows Installer
download_1006_a=Platform-Independent Zip
download_1006_a=Platform-Independent Zip
download_1007_h3=Download Mirror and Older Versions
download_1007_h3=Old Versions
download_1008_a=Platform-Independent Zip
download_1008_a=Platform-Independent Zip
download_1009_h3=Jar File
download_1009_h3=Jar File
download_1010_a=Maven.org
download_1010_a=Maven.org
...
@@ -908,8 +920,8 @@ download_1015_a=Javadoc
...
@@ -908,8 +920,8 @@ download_1015_a=Javadoc
download_1016_a=Sources
download_1016_a=Sources
download_1017_h3=Database Upgrade Helper File
download_1017_h3=Database Upgrade Helper File
download_1018_a=Upgrade database from 1.1 to the current version
download_1018_a=Upgrade database from 1.1 to the current version
download_1019_h3=Subversion Source Repository
download_1019_h3=Git Source Repository
download_1020_a=Google Code
download_1020_a=Github
download_1021_p=\ For details about changes, see the <a href\="changelog.html">Change Log</a>.
download_1021_p=\ For details about changes, see the <a href\="changelog.html">Change Log</a>.
download_1022_h3=News and Project Information
download_1022_h3=News and Project Information
download_1023_a=Atom Feed
download_1023_a=Atom Feed
...
@@ -943,7 +955,7 @@ faq_1023_li=Apache Harmony\: there seems to be a bug in Harmony that affects H2.
...
@@ -943,7 +955,7 @@ faq_1023_li=Apache Harmony\: there seems to be a bug in Harmony that affects H2.
faq_1024_li=Tomcat and Glassfish 3 set most static fields (final or non-final) to <code>null</code> when unloading a web application. This can cause a <code>NullPointerException</code> in H2 versions 1.1.107 and older, and may still not work in newer versions. Please report it if you run into this issue. In Tomcat >\=6.0 this behavior can be disabled by setting the system property <code>org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES\=false</code>, however Tomcat may then run out of memory. A known workaround is to put the <code>h2*.jar</code> file in a shared <code>lib</code> directory (<code>common/lib</code>).
faq_1024_li=Tomcat and Glassfish 3 set most static fields (final or non-final) to <code>null</code> when unloading a web application. This can cause a <code>NullPointerException</code> in H2 versions 1.1.107 and older, and may still not work in newer versions. Please report it if you run into this issue. In Tomcat >\=6.0 this behavior can be disabled by setting the system property <code>org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES\=false</code>, however Tomcat may then run out of memory. A known workaround is to put the <code>h2*.jar</code> file in a shared <code>lib</code> directory (<code>common/lib</code>).
faq_1025_li=Some problems have been found with right outer join. Internally, it is converted to left outer join, which does not always produce the same results as other databases when used in combination with other joins. This problem is fixed in H2 version 1.3.
faq_1025_li=Some problems have been found with right outer join. Internally, it is converted to left outer join, which does not always produce the same results as other databases when used in combination with other joins. This problem is fixed in H2 version 1.3.
faq_1026_li=When using Install4j before 4.1.4 on Linux and enabling <code>pack200</code>, the <code>h2*.jar</code> becomes corrupted by the install process, causing application failure. A workaround is to add an empty file <code>h2*.jar.nopack</code> next to the <code>h2*.jar</code> file. This problem is solved in Install4j 4.1.4.
faq_1026_li=When using Install4j before 4.1.4 on Linux and enabling <code>pack200</code>, the <code>h2*.jar</code> becomes corrupted by the install process, causing application failure. A workaround is to add an empty file <code>h2*.jar.nopack</code> next to the <code>h2*.jar</code> file. This problem is solved in Install4j 4.1.4.
faq_1027_p=\ For a complete list, see <a href\="http\://code.google.com/p/h2database/issues/list">Open Issues</a>.
faq_1027_p=\ For a complete list, see <a href\="https\://github.com/h2database/h2database/issues">Open Issues</a>.
faq_1028_h3=Is this Database Engine Open Source?
faq_1028_h3=Is this Database Engine Open Source?
faq_1029_p=\ Yes. It is free to use and distribute, and the source code is included. See also under license.
faq_1029_p=\ Yes. It is free to use and distribute, and the source code is included. See also under license.
faq_1030_h3=Is Commercial Support Available?
faq_1030_h3=Is Commercial Support Available?
...
@@ -1263,7 +1275,7 @@ features_1256_p=\ *7 Derby only supports updatable result sets if the query is n
...
@@ -1263,7 +1275,7 @@ features_1256_p=\ *7 Derby only supports updatable result sets if the query is n
features_1257_p=\ *8 Derby doesn't support standard compliant information schema tables.
features_1257_p=\ *8 Derby doesn't support standard compliant information schema tables.
features_1258_p=\ *9 When using MVCC (multi version concurrency).
features_1258_p=\ *9 When using MVCC (multi version concurrency).
features_1259_p=\ *10 Derby and HSQLDB <a href\="http\://en.wikipedia.org/wiki/Block_cipher_modes_of_operation\#Electronic_codebook_.28ECB.29">don't hide data patterns well</a>.
features_1259_p=\ *10 Derby and HSQLDB <a href\="http\://en.wikipedia.org/wiki/Block_cipher_modes_of_operation\#Electronic_codebook_.28ECB.29">don't hide data patterns well</a>.
features_1260_p=\ *11 The MULTI_THREADED option is not enabled by default, and not yet supported when using MVCC.
features_1260_p=\ *11 The MULTI_THREADED option is not enabled by default, and with version 1.3.x not supported when using MVCC.
features_1261_p=\ *12 Derby doesn't support the <code>EXPLAIN</code> statement, but it supports runtime statistics and retrieving statement execution plans.
features_1261_p=\ *12 Derby doesn't support the <code>EXPLAIN</code> statement, but it supports runtime statistics and retrieving statement execution plans.
features_1262_p=\ *13 Derby doesn't support the syntax <code>LIMIT .. [OFFSET ..]</code>, however it supports <code>FETCH FIRST .. ROW[S] ONLY</code>.
features_1262_p=\ *13 Derby doesn't support the syntax <code>LIMIT .. [OFFSET ..]</code>, however it supports <code>FETCH FIRST .. ROW[S] ONLY</code>.
features_1263_p=\ *14 Using collations. *15 Derby and H2 support <code>ROW_NUMBER() OVER()</code>.
features_1263_p=\ *14 Using collations. *15 Derby and H2 support <code>ROW_NUMBER() OVER()</code>.
...
@@ -1402,8 +1414,8 @@ features_1395_p=\ An application can open multiple databases at the same time, i
...
@@ -1402,8 +1414,8 @@ features_1395_p=\ An application can open multiple databases at the same time, i
features_1396_h3=Multiple Connections to the Same Database\:Client/Server
features_1396_h3=Multiple Connections to the Same Database\:Client/Server
features_1397_p=\ If you want to access the same database at the same time from different processes or computers, you need to use the client / server mode. In this case, one process acts as the server, and the other processes (that could reside on other computers as well) connect to the server via TCP/IP (or TLS over TCP/IP for improved security).
features_1397_p=\ If you want to access the same database at the same time from different processes or computers, you need to use the client / server mode. In this case, one process acts as the server, and the other processes (that could reside on other computers as well) connect to the server via TCP/IP (or TLS over TCP/IP for improved security).
features_1398_h3=Multithreading Support
features_1398_h3=Multithreading Support
features_1399_p=\ This database is multithreading-safe. That means, if an application is multi-threaded, it does not need to worry about synchronizing access to the database. Internally, most requests to the same database are synchronized. That means an application can use multiple threads that access the same database at the same time, however if one thread executes a long running query, the other threads need to wait.
features_1399_p=\ This database is multithreading-safe. If an application is multi-threaded, it does not need to worry about synchronizing access to the database. An application should normally use one connection per thread. This database synchronizes access to the same connection, but other databases may not do this. To get higher concurrency, you need to use multiple connections.
features_1400_p=\ An application should normally use one connection per thread. This database synchronizes access to the same connection, but other databases may not do this.
features_1400_p=\ By default, requests to the same database are synchronized. That means an application can use multiple threads that access the same database at the same time, however if one thread executes a long running query, the other threads need to wait. To enable concurrent database usage, see the setting <code>MULTI_THREADED</code>.
features_1401_h3=Locking, Lock-Timeout, Deadlocks
features_1401_h3=Locking, Lock-Timeout, Deadlocks
features_1402_p=\ Please note MVCC is enabled in version 1.4.x by default, when using the MVStore. In this case, table level locking is not used. If <a href\="advanced.html\#mvcc">multi-version concurrency</a> is not used, the database uses table level locks to give each connection a consistent state of the data. There are two kinds of locks\:read locks (shared locks) and write locks (exclusive locks). All locks are released when the transaction commits or rolls back. When using the default transaction isolation level 'read committed', read locks are already released after each statement.
features_1402_p=\ Please note MVCC is enabled in version 1.4.x by default, when using the MVStore. In this case, table level locking is not used. If <a href\="advanced.html\#mvcc">multi-version concurrency</a> is not used, the database uses table level locks to give each connection a consistent state of the data. There are two kinds of locks\:read locks (shared locks) and write locks (exclusive locks). All locks are released when the transaction commits or rolls back. When using the default transaction isolation level 'read committed', read locks are already released after each statement.
features_1403_p=\ If a connection wants to reads from a table, and there is no write lock on the table, then a read lock is added to the table. If there is a write lock, then this connection waits for the other connection to release the lock. If a connection cannot get a lock for a specified time, then a lock timeout exception is thrown.
features_1403_p=\ If a connection wants to reads from a table, and there is no write lock on the table, then a read lock is added to the table. If there is a write lock, then this connection waits for the other connection to release the lock. If a connection cannot get a lock for a specified time, then a lock timeout exception is thrown.
...
@@ -1560,7 +1572,7 @@ features_1553_h2=Read Only Databases in Zip or Jar File
...
@@ -1560,7 +1572,7 @@ features_1553_h2=Read Only Databases in Zip or Jar File
features_1554_p=\ To create a read-only database in a zip file, first create a regular persistent database, and then create a backup. The database must not have pending changes, that means you need to close all connections to the database first. To speed up opening the read-only database and running queries, the database should be closed using <code>SHUTDOWN DEFRAG</code>. If you are using a database named <code>test</code>, an easy way to create a zip file is using the <code>Backup</code> tool. You can start the tool from the command line, or from within the H2 Console (Tools - Backup). Please note that the database must be closed when the backup is created. Therefore, the SQL statement <code>BACKUP TO</code> can not be used.
features_1554_p=\ To create a read-only database in a zip file, first create a regular persistent database, and then create a backup. The database must not have pending changes, that means you need to close all connections to the database first. To speed up opening the read-only database and running queries, the database should be closed using <code>SHUTDOWN DEFRAG</code>. If you are using a database named <code>test</code>, an easy way to create a zip file is using the <code>Backup</code> tool. You can start the tool from the command line, or from within the H2 Console (Tools - Backup). Please note that the database must be closed when the backup is created. Therefore, the SQL statement <code>BACKUP TO</code> can not be used.
features_1555_p=\ When the zip file is created, you can open the database in the zip file using the following database URL\:
features_1555_p=\ When the zip file is created, you can open the database in the zip file using the following database URL\:
features_1556_p=\ Databases in zip files are read-only. The performance for some queries will be slower than when using a regular database, because random access in zip files is not supported (only streaming). How much this affects the performance depends on the queries and the data. The database is not read in memory; therefore large databases are supported as well. The same indexes are used as when using a regular database.
features_1556_p=\ Databases in zip files are read-only. The performance for some queries will be slower than when using a regular database, because random access in zip files is not supported (only streaming). How much this affects the performance depends on the queries and the data. The database is not read in memory; therefore large databases are supported as well. The same indexes are used as when using a regular database.
features_1557_p=\ If the database is larger than a few megabytes, performance is much better if the database file is split into multiple smaller files, because random access in compressed files is not possible. See also the sample application <a href\="http\://code.google.com/p/h2database/source/browse/trunk/h2/src/test/org/h2/samples/ReadOnlyDatabaseInZip.java">ReadOnlyDatabaseInZip</a>.
features_1557_p=\ If the database is larger than a few megabytes, performance is much better if the database file is split into multiple smaller files, because random access in compressed files is not possible. See also the sample application <a href\="https\://github.com/h2database/h2database/tree/master/h2/src/test/org/h2/samples/ReadOnlyDatabaseInZip.java">ReadOnlyDatabaseInZip</a>.
features_1558_h3=Opening a Corrupted Database
features_1558_h3=Opening a Corrupted Database
features_1559_p=\ If a database cannot be opened because the boot info (the SQL script that is run at startup) is corrupted, then the database can be opened by specifying a database event listener. The exceptions are logged, but opening the database will continue.
features_1559_p=\ If a database cannot be opened because the boot info (the SQL script that is run at startup) is corrupted, then the database can be opened by specifying a database event listener. The exceptions are logged, but opening the database will continue.
features_1560_h2=Computed Columns / Function Based Index
features_1560_h2=Computed Columns / Function Based Index
...
@@ -3604,11 +3616,10 @@ roadmap_1506_li=Sybase SQL Anywhere compatibility\: SELECT TOP ... START AT ...
...
@@ -3604,11 +3616,10 @@ roadmap_1506_li=Sybase SQL Anywhere compatibility\: SELECT TOP ... START AT ...
roadmap_1510_li=Support index-only when doing selects (i.e. without needing to load the actual table data)
roadmap_1510_h2=Not Planned
roadmap_1511_h2=Not Planned
roadmap_1511_li=HSQLDB (did) support this\:select id i from test where i<0 (other databases don't). Supporting it may break compatibility.
roadmap_1512_li=HSQLDB (did) support this\:select id i from test where i<0 (other databases don't). Supporting it may break compatibility.
roadmap_1512_li=String.intern (so that Strings can be compared with \=\=) will not be used because some VMs have problems when used extensively.
roadmap_1513_li=String.intern (so that Strings can be compared with \=\=) will not be used because some VMs have problems when used extensively.
roadmap_1513_li=In prepared statements, identifier names (table names and so on) can not be parameterized. Adding such a feature would complicate the source code without providing reasonable speedup, and would slow down regular prepared statements.
roadmap_1514_li=In prepared statements, identifier names (table names and so on) can not be parameterized. Adding such a feature would complicate the source code without providing reasonable speedup, and would slow down regular prepared statements.
