提交 7aa917b7 authored 作者: Thomas Mueller's avatar Thomas Mueller

Documentation.

上级 20691b56
...@@ -19,7 +19,9 @@ Change Log ...@@ -19,7 +19,9 @@ Change Log
<h2>Next Version (unreleased)</h2> <h2>Next Version (unreleased)</h2>
<ul><li>On out of disk space, the database could get corrupt sometimes, <ul><li>On out of disk space, the database could get corrupt sometimes,
if later write operations succeeded. Now the file is closed on the first unsuccessful if later write operations succeeded. The same problem happened on other
kinds of I/O exceptions (where one or some of the writes fail, but subsequent writes
succeed). Now the file is closed on the first unsuccessful
write operation, so that later requests fail consistently. write operation, so that later requests fail consistently.
</li><li>DatabaseEventListener.diskSpaceIsLow() is no longer supported because </li><li>DatabaseEventListener.diskSpaceIsLow() is no longer supported because
it can't be guaranteed that it always works correctly. it can't be guaranteed that it always works correctly.
......
...@@ -50,6 +50,8 @@ Hi, ...@@ -50,6 +50,8 @@ Hi,
This looks like a corrupt database. To recover the data, 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? This looks like a corrupt database. To recover the data, 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?
With version 1.3.162 and older: on out of disk space, the database can get corrupt sometimes, if later write operations succeed. The same problem happens on other kinds of I/O exceptions (where one or some of the writes fail, but subsequent writes succeed). Now the file is closed on the first unsuccessful write operation, so that later requests fail consistently.
Important corruption problems were fixed in version 1.2.135 and version 1.2.140 (see the change log). Known causes for corrupt databases are: if the database was created or used with a version older than 1.2.135, and the process was killed while the database was closing or writing a checkpoint. Using the transaction isolation level READ_UNCOMMITTED (LOCK_MODE 0) while at the same time using multiple connections. Disabling database file protection using (setting FILE_LOCK to NO in the database URL). Some other areas that are not fully tested are: Platforms other than Windows XP, Linux, Mac OS X, or JVMs other than Sun 1.5 or 1.6; the feature MULTI_THREADED; the features AUTO_SERVER and AUTO_RECONNECT; the file locking method 'Serialized'. Important corruption problems were fixed in version 1.2.135 and version 1.2.140 (see the change log). Known causes for corrupt databases are: if the database was created or used with a version older than 1.2.135, and the process was killed while the database was closing or writing a checkpoint. Using the transaction isolation level READ_UNCOMMITTED (LOCK_MODE 0) while at the same time using multiple connections. Disabling database file protection using (setting FILE_LOCK to NO in the database URL). Some other areas that are not fully tested are: Platforms other than Windows XP, Linux, Mac OS X, or JVMs other than Sun 1.5 or 1.6; the feature MULTI_THREADED; the features AUTO_SERVER and AUTO_RECONNECT; the file locking method 'Serialized'.
I am very interested in analyzing and solving this problem. Corruption problems have top priority for me. I have a few questions: I am very interested in analyzing and solving this problem. Corruption problems have top priority for me. I have a few questions:
......
1.3.162 2011-11-26
1.3.161 2011-10-28
1.3.160 2011-09-11
1.3.159 2011-08-13
1.3.158 2011-07-17
1.3.157 2011-06-25
1.3.156 2011-06-17
1.3.155 2011-05-27
1.3.154 2011-04-04
1.3.153 2011-03-14
1.3.152 2011-03-01 Beta
1.3.151 2011-02-12 Beta
1.3.150 2011-01-28 Beta
1.3.149 2011-01-07 Beta
1.3.148 2010-12-12 Beta
1.2.147 2010-11-21
1.3.146 2010-11-08 Beta
1.2.145 2010-11-02
1.0.78 2008-08-28 1.0.78 2008-08-28
1.0.77 2008-08-16 1.0.77 2008-08-16
......
Markdown 格式
0%
您添加了 0 到此讨论。请谨慎行事。
请先完成此评论的编辑!
注册 或者 后发表评论