Hi, I agree that compatibility is a big issue when H2 is used in embedded mode as part of a distributable.
I asked a question about this before: http://groups.google.com/group/h2-database/browse_thread/thread/701be62a95fb1f4/101fb2d262fa864f?lnk=gst&q=upgrading#101fb2d262fa864f I'd really like to know what the H2 policy is with regard to upgrading. At the very least the change log should always mention all compatibility issues. I don't think anybody can disagree with that? It looks like that there is no mention of this compatibility issue at all? Has this particular issue been previously discussed on the group? If not, can anyone explain what the exact problem is and in what situations it occurs? Kind Regards, Vasco On Mon, Mar 12, 2012 at 7:42 PM, Maxim Geraskin <[email protected]> wrote: > I think that broken backward compatibility is too serious issue and > should be mentioned somehow on the main H2 page. As I understand it is > not only me who met this problem, potentially each user can. In fact, > this blocks our next release - we may not allow to release a version > which would not work at all on H2 databases, we can use previous H2 > version but as I understand there is a bug which alreasy existed and > it just became visible. We support also others database but H2 has > been used as default option due to its speed. We also noticied a lot > of deadlock problems in connection to BLOB handling, so in previous > release we had to make Derby as default. Now I think we have to get > rid of H2. > > On Mar 12, 6:48 pm, Noel Grandin <[email protected]> wrote: >> I believe this is one of those places where it was too hard to write >> automatic upgrade code. >> >> You could probably make your program run the recover tool programmatically. >> >> On 2012-03-12 15:49, Maxim Geraskin wrote: >> >> >> >> >> >> >> >> > Hi, >> >> > when h2-1.3.164 version is used with databases, created with older >> > versions we get the following error: >> >> > File corrupted while reading record: "-1 of 16079". Possible solution: >> > use the recovery tool; SQL statement: >> > CREATE CACHED TABLE IF NOT EXISTS INFORMATION_SCHEMA.LOB_MAP( >> > LOB BIGINT NOT NULL, >> > SEQ INT NOT NULL, >> > HASH INT, >> > BLOCK BIGINT >> > ) >> >> > As I understand from >> >> >http://groups.google.com/group/h2-database/browse_thread/thread/be21e... >> >http://h2-database.66688.n3.nabble.com/Recovery-failed-td3089905.html >> >> > to fix this we have to run recovery tool, but we have a lot of >> > installs which use h2 as embedded, should we and our users run >> > recovery tool manually on every location? Or it will be fixed in next >> > releases somehow? It is strange that every user should use recovery >> > tool during upgrade. >> >> > Maxim > > -- > 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. > -- 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.
