Hi, > Because of Java 1.4 we're currently still at 1.1.111.
Did you try Retrotranslator? See also http://www.h2database.com/html/build.html#portability > I also don't see anything in the change log of later versions that is clearly > related > to this problem. That's true, I don't see what it could be... You are not using views that use GROUP BY? If yes it could be the problem described in version 1.1.112: "GROUP BY queries with a self-join (join to the same table) that were grouped by columns with indexes returned the wrong result in some cases." > SELECT count(*) FROM embedded_events; --> count = 2 > SELECT * FROM embedded_events ORDER BY ID; --> 'no rows' In theory it could be a corrupted index file, after a power failure... If that's the case the problem will disappear after deleting the .index.db file. To avoid corrupted index files, append ;LOG=2 to the database URL. See also http://www.h2database.com/html/grammar.html#set_log > (I've placed it on another machine and am not seeing the problem anymore). The reason could be that the index was re-built when opening due to a bug that was fixed in version 1.1.112: "...indexes were always re-built unnecessarily when opening" Regards, Thomas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/h2-database?hl=en -~----------~----~----~----~------~----~------~--~---
