|
From: Ben A. <ben...@ac...> - 2004-11-13 01:04:55
|
Colin Sampaleanu wrote: > I was going to try slipping in 1.7.2 in our own codebase, which you > would think would not be an issue going from 1.7.1 to 1.7.2, but in > fact there are some major changes internally, and the new version > barfs on the stored db as well as the setup script for petclinic for > example, with an error on some of the formerly legal SQL. > http://hsqldb.sourceforge.net/web/changelog.html > I think this kind of incompatibility is an major bad move for the > developer of HSQLDB; this should have been called 1.8 then... > Both Spring Rich and Acegi Security are using HSQLDB 1.7.2 RC 6D because it provides a more robust in-memory database implementation. Whilst these projects don't push HSQLDB's features, it was only a minor couple of changes to get the later version running successfully. Also, in Spring Rich there's an InMemoryClinic that extends HsqlJdbcClinic, so it runs fine with 1.7.2 RC 6D at least. I agree users will want to move to the later versions (as the above projects needed to), so it's probably desirable to perform the upgrade. Best regards Ben |