although I'm not sure I want to deal with the modeler upgrade issues at the same time.
Modeler preference directories are versioned. So you can change the version subdir from 1.2 to 3.0, avoiding any upgrade issues - the new db will be created in the different directory.
Having said that, I am contemplating a migration to Derby from HSQLDB - in my tests it seems much more stable and never corrupts the data. Also "kill -9" on the app does not permanently lock the DB, like HSQL does. But I am not at this point yet.
Andrus On Jul 20, 2006, at 3:44 PM, Mike Kienenberger wrote:
Heh. Ok. So it wasn't an original idea :) Thanks. I'll see what I can do, although I'm not sure I want to deal with the modeler upgrade issues at the same time. On 7/20/06, Andrus Adamchik (JIRA) <[EMAIL PROTECTED]> wrote:Andrus Adamchik updated CAY-351: -------------------------------- Fix Version: 3.0 (was: UNDEFINED FUTURE) Version: 3.0 (was: 1.2 [STABLE]) Assign To: Mike Kienenberger (was: Andrus Adamchik)Assigning to Mike per http://objectstyle.org/cayenne/lists/cayenne- devel/current/0177.html
