</li><li>DISTINCT: support large result sets by sorting on all columns (additionally) and then removing duplicates.
...
...
@@ -495,6 +496,8 @@ See also <a href="build.html#providing_patches">Providing Patches</a>.
</li><li>Improve documentation of system properties: only list the property names, default values, and description.
</li><li>Support running totals / cumulative sum using SUM(..) OVER(..).
</li><li>Improve object memory size calculation. Use constants for known VMs, or use reflection to call java.lang.instrument.Instrumentation.getObjectSize(Object objectToSize)
</li><li>Triggers: NOT NULL checks should be done after running triggers (Oracle behavior, maybe others).
</li><li>Log long running transactions (similar to long running statements).
This looks like a corrupt database. A 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?
As far as I see, you are using version 1.2.128. An important corruption problem was fixed in version 1.2.135 (see the change log). Known causes for corrupt databases are:
An important corruption problem was fixed in version 1.2.135 (see the change log). Known causes for corrupt databases are:
- If the database was used with a version older than 1.2.135, and the process was killed while the database was closing or writing a checkpoint.
- 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.