2014-06-02 18:04 GMT+02:00 Thomas Mueller <[email protected]>:
> Yes, this problem was introduced in version 1.3.176, actually by fixing > another bug. It happens when upgrading a database with a special kind of > foreign key constraint from an older version to 1.3.176. I found the > problem now and have a fix for it. I will need to release a new version; a > workaround is to stay with the older version, or upgrade to the newer > version by first converting to a SQL script and then creating a new > database. > ​Just to be sure. In the new version the problem is solved and I do not need to convert the db? I do not think there are important changes (for me) in 176, so I just wait until the new version is deployed. -- Cecil Westerhof -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
