@@ -1106,7 +1106,7 @@ To build the database executables, the following software stack was used. Newer
Windows XP
@build_1012_li
Sun JDK Version 1.4 or 1.5
Sun JDK Version 1.4
@build_1013_li
Apache Ant Version 1.6.5
...
...
@@ -1178,7 +1178,7 @@ The conversion between UTF-8 and Java encoding (using the \u syntax), as well as
Downloads
@download_1001_h3
Version 1.0.63 (2007-12-02, Current)
Version 1.0.64 (2007-12-26, Current)
@download_1002_a
Windows Installer
...
...
@@ -1187,18 +1187,27 @@ Windows Installer
Platform-Independent Zip
@download_1004_h3
Download Mirror and Older Versions
Version 1.0.63 (2007-12-02, Last Stable)
@download_1005_a
Windows Installer
@download_1006_a
Platform-Independent Zip
@download_1006_h3
@download_1007_h3
Download Mirror and Older Versions
@download_1008_a
Platform-Independent Zip
@download_1009_h3
Subversion Source Repository
@download_1007_a
@download_1010_a
Google Code
@download_1008_p
@download_1011_p
For details about changes, see the <a href="history.html">Change Log</a> .
@faq_1000_h1
...
...
@@ -1298,22 +1307,22 @@ The maximum file size for FAT or FAT32 file systems is 4 GB. So if you use FAT o
Is it Reliable?
@faq_1032_p
That is not easy to say. It is still a quite new product. A lot of tests have been written, and the code coverage of these tests is very high. Randomized stress tests are run regularly. But as this is a relatively new product, there are probably some problems that have not yet been found. Areas that are not 100% tested:
That is not easy to say. It is still a quite new product. A lot of tests have been written, and the code coverage of these tests is very high. Randomized stress tests are run regularly. But as this is a relatively new product, there are probably some problems that have not yet been found. Areas that are not fully tested:
@faq_1033_li
Platforms other than Windows XP and the Sun JVM 1.4 and 1.5
@faq_1034_li
Data types BLOB, CLOB, VARCHAR_IGNORECASE, OTHER
The MVCC (multi version concurrency) mode
@faq_1035_li
Cluster mode, 2-Phase Commit, Savepoints
@faq_1036_li
Server mode (well tested, but not as well as Embedded mode)
Multi-Threading and using multiple connections
@faq_1037_li
Multi-Threading and using multiple connections
24/7 operation and large databases (500 MB and up)
@faq_1038_li
Updatable result sets
...
...
@@ -1331,36 +1340,39 @@ Not all built-in functions are completely tested
The Optimizer may not always select the best plan
@faq_1043_li
24/7 operation and large databases (500 MB and up)
Data types BLOB, CLOB, VARCHAR_IGNORECASE, OTHER
@faq_1044_li
Server mode (well tested, but not as well as Embedded mode)
@faq_1045_li
Wide indexes with large VARCHAR or VARBINARY columns and / or with a lot of columns
@faq_1045_p
@faq_1046_p
Areas considered Experimental:
@faq_1046_li
ODBC driver and the GCJ native version on Windows
@faq_1047_li
Linear Hash Index
The PostgreSQL server
@faq_1048_li
Compatibility modes for other databases (only some features are implemented)
Linear Hash Index
@faq_1049_li
The ARRAY data type and related functionality.
Compatibility modes for other databases (only some features are implemented)
@faq_1050_li
The ARRAY data type and related functionality
@faq_1050_h3
@faq_1051_h3
Is the GCJ version stable? Faster?
@faq_1051_p
@faq_1052_p
The GCJ version is not as stable as the Java version. When running the regression test with the GCJ version, sometimes the application just stops at what seems to be a random point without error message. Currently, the GCJ version is also slower than when using the Sun VM. However, the startup of the GCJ version is faster than when using a VM.
@faq_1052_h3
@faq_1053_h3
How to Translate this Project?
@faq_1053_p
@faq_1054_p
For more information, see <a href="build.html#translating">Build/Translating</a> .
@features_1000_h1
...
...
@@ -3206,7 +3218,7 @@ JDBC and (partial) ODBC API; Web Client application
#That is not easy to say. It is still a quite new product. A lot of tests have been written, and the code coverage of these tests is very high. Randomized stress tests are run regularly. But as this is a relatively new product, there are probably some problems that have not yet been found. Areas that are not fully tested:
@faq_1033_li
WindowsXP以外のプラットフォーム、及びSUN JVM1.4、1.5での動作確認
@faq_1034_li
データ型 BLOB、CLOB、VARCHAR_IGNORECASE、OTHER
#The MVCC (multi version concurrency) mode
@faq_1035_li
クラスタモード、2フェーズコミット、セーブポイント
@faq_1036_li
サーバーモード(十分にテストはしてありますが、組み込みモードほどではありません)
マルチスレッドと複数接続の利用
@faq_1037_li
マルチスレッドと複数接続の利用
24/7オペレーション、大容量データベース (500MB以上)
@faq_1038_li
Updatable result sets
...
...
@@ -1333,36 +1342,39 @@ ALTER TABLE ステートメント、ビュー、リンクテーブル、スキ
アプリケーションから結果が返される前に、全ての行はデータベースによって読み取られます。 サーバー側のカーソルは現在サポートされていません。もし最初の数行がアプリケーションに読み取られたら、 result setサイズはパフォーマンスを改善するために制限されます。これは、クエリーの LIMIT を使用することで 実現できます (例: SELECT * FROM TEST LIMIT 100)、または Statement.setMaxRows(max) を使用します。
@~advanced_1023_h3
大きなResult Set と外部ソート
@~advanced_1024_p
1000行以上のresult setのために、結果はディスクにバッファーされます。 もし ORDER BY が使用されていたら、ソートは、外部ソートアルゴリズムを使用して 完了しています。このケースでは、それぞれの行のブロックはクイックソートを使用してソートされ、 ディスクに書き込まれています; データを読み込んでいる時、ブロックは一緒にマージされます。
#The database allows multiple concurrent connections to the same database. To make sure all connections only see consistent data, table level locking is used by default. This mechanism does not allow high concurrency, but is very fast. Shared locks and exclusive locks are supported. Before reading from a table, the database tries to add a shared lock to the table (this is only possible if there is no exclusive lock on the object by another connection). If the shared lock is added successfully, the table can be read. It is allowed that other connections also have a shared lock on the same object. If a connection wants to write to a table (update or delete a row), an exclusive lock is required. To get the exclusive lock, other connection must not have any locks on the object. After the connection commits, all locks are released. This database keeps all locks in memory.
#The MVCC feature allows higher concurrency than using (table level or row level) locks. When using MVCC in this database, delete, insert and update operations will only issue a shared lock on the table. Table are still locked exclusively when adding or removing columns, when dropping the table, and when using SELECT ... FOR UPDATE. Connections only 'see' committed data, and own changes. That means, if connection A updates a row but doesn't commit this change yet, connection B will see the old value. Only when the change is committed, the new value is visible by other connections (read committed). If multiple connections concurrently try to update the same row, this database fails fast: a concurrent update exception is thrown.
JavaのGNUコンパイラー<a href="http://gcc.gnu.org/java/">http://gcc.gnu.org/java/</a> and <a href="http://nativej.mtsystems.ch">http://nativej.mtsystems.ch/ (not free any more)</a>
build_1034_p=The conversion between UTF-8 and Java encoding (using the \\u syntax), as well as the HTML entities (&\#..;) is automated by running the tool PropertiesToUTF8. The web site translation is automated as well, using <code>ant docs</code> .
download_1004_h3=Download Mirror and Older Versions
download_1005_a=Platform-Independent Zip
download_1006_h3=Subversion Source Repository
download_1007_a=Google Code
download_1008_p=For details about changes, see the <a href\="history.html">Change Log</a> .
download_1004_h3=Version 1.0.63 (2007-12-02, Last Stable)
download_1005_a=Windows Installer
download_1006_a=Platform-Independent Zip
download_1007_h3=Download Mirror and Older Versions
download_1008_a=Platform-Independent Zip
download_1009_h3=Subversion Source Repository
download_1010_a=Google Code
download_1011_p=For details about changes, see the <a href\="history.html">Change Log</a> .
faq_1000_h1=Frequently Asked Questions
faq_1001_a=Are there any known bugs? When is the next release?
faq_1002_a=Is this Database Engine Open Source?
...
...
@@ -431,28 +434,29 @@ faq_1028_h3=What is the Size Limit (maximum size) of a Database?
faq_1029_p=The theoretical limit is currently 256 GB for the data. This number is excluding BLOB and CLOB data\:Every CLOB or BLOB can be up to 256 GB as well. The size limit of the index data is 256 GB as well.
faq_1030_p=The maximum file size for FAT or FAT32 file systems is 4 GB. So if you use FAT or FAT32, the limit is 4 GB for the data.
faq_1031_h3=Is it Reliable?
faq_1032_p=That is not easy to say. It is still a quite new product. A lot of tests have been written, and the code coverage of these tests is very high. Randomized stress tests are run regularly. But as this is a relatively new product, there are probably some problems that have not yet been found. Areas that are not 100% tested\:
faq_1032_p=That is not easy to say. It is still a quite new product. A lot of tests have been written, and the code coverage of these tests is very high. Randomized stress tests are run regularly. But as this is a relatively new product, there are probably some problems that have not yet been found. Areas that are not fully tested\:
faq_1033_li=Platforms other than Windows XP and the Sun JVM 1.4 and 1.5
faq_1034_li=Data types BLOB, CLOB, VARCHAR_IGNORECASE, OTHER
faq_1034_li=The MVCC (multi version concurrency) mode
faq_1036_li=Server mode (well tested, but not as well as Embedded mode)
faq_1037_li=Multi-Threading and using multiple connections
faq_1036_li=Multi-Threading and using multiple connections
faq_1037_li=24/7 operation and large databases (500 MB and up)
faq_1038_li=Updatable result sets
faq_1039_li=Referential integrity and check constraints, Triggers
faq_1040_li=ALTER TABLE statements, Views, Linked Tables, Schema, UNION
faq_1041_li=Not all built-in functions are completely tested
faq_1042_li=The Optimizer may not always select the best plan
faq_1043_li=24/7 operation and large databases (500 MB and up)
faq_1044_li=Wide indexes with large VARCHAR or VARBINARY columns and / or with a lot of columns
faq_1045_p=Areas considered Experimental\:
faq_1046_li=ODBC driver and the GCJ native version on Windows
faq_1047_li=Linear Hash Index
faq_1048_li=Compatibility modes for other databases (only some features are implemented)
faq_1049_li=The ARRAY data type and related functionality.
faq_1050_h3=Is the GCJ version stable? Faster?
faq_1051_p=The GCJ version is not as stable as the Java version. When running the regression test with the GCJ version, sometimes the application just stops at what seems to be a random point without error message. Currently, the GCJ version is also slower than when using the Sun VM. However, the startup of the GCJ version is faster than when using a VM.
faq_1052_h3=How to Translate this Project?
faq_1053_p=For more information, see <a href\="build.html\#translating">Build/Translating</a> .
faq_1043_li=Data types BLOB, CLOB, VARCHAR_IGNORECASE, OTHER
faq_1044_li=Server mode (well tested, but not as well as Embedded mode)
faq_1045_li=Wide indexes with large VARCHAR or VARBINARY columns and / or with a lot of columns
faq_1046_p=Areas considered Experimental\:
faq_1047_li=The PostgreSQL server
faq_1048_li=Linear Hash Index
faq_1049_li=Compatibility modes for other databases (only some features are implemented)
faq_1050_li=The ARRAY data type and related functionality
faq_1051_h3=Is the GCJ version stable? Faster?
faq_1052_p=The GCJ version is not as stable as the Java version. When running the regression test with the GCJ version, sometimes the application just stops at what seems to be a random point without error message. Currently, the GCJ version is also slower than when using the Sun VM. However, the startup of the GCJ version is faster than when using a VM.
faq_1053_h3=How to Translate this Project?
faq_1054_p=For more information, see <a href\="build.html\#translating">Build/Translating</a> .
features_1000_h1=Features
features_1001_a=Feature List
features_1002_a=Limitations
...
...
@@ -1067,7 +1071,7 @@ mainWeb_1003_li=Written Java; can be compiled with GCJ (Linux)
mainWeb_1004_li=Embedded, Server and Cluster modes
mainWeb_1005_li=JDBC and (partial) ODBC API; Web Client application
@@ -28,6 +28,9 @@ I am sorry to say that, but it looks like a corruption problem. I am very intere
- What is your database URL?
- What version H2 are you using?
- The first workarounds is: append ;RECOVER=1 to the database URL. Does it work when you do this?
- The second workarounds is: delete the index.db file (it is re-created automatically) and try again. Does it work when you do this?
- The third workarounds is: use the tool org.h2.tools.Recover to create the SQL script file, and then re-create the database using this script. Does it work when you do this?
- Do you use any settings or special features (for example, the setting LOG=0, or two phase commit, linked tables, cache settings)?
- On what operating system, file system, and virtual machine?
