There's a SchemaUpdate too, which might be of use. On Mon, Jun 8, 2009 at 12:52 PM, Niclas Pehrsson <[email protected]> wrote:
> > Hi Im evaluating the SchemaExport possibilities for using it as an > database upgrading tool while the application is in production. > > What can it do and what can it not do? > > Earlier when I'm has been developing applications we have used our own > versioning management, with one upgradeclass per version. Which > allowed us to change the tables, manipulate data and then change the > tables again if we wanted to add for example a new not null column > field in some table. Can I make something similar to the SchemaExport > functionality or is it more limited? > > Anything else I need to think about, it had been pretty neat to use > SchemaExport as upgradetool :). > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
