I would second this question, and elaborate on it -- is there a way to handle DB schema updates without having to wipe everything and start over with fresh empty new version of the database?
On Sun, Nov 14, 2010 at 3:03 PM, Afshar Mohebbi <[email protected]>wrote: > Hi, > > Suppose I have a database that is just created based on some hbms. I > add a field to one of entities and use SchemaUpdate to update databse > with current change. Unfortunately UpdateSchema in addition to > generating ascript to add the new field, gnerates mostly all foregin > key constraints again as duplicate. > > Am I missing something or is it a bug? > > > Regards, > Afshar Mohebbi > > -- > 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]<nhusers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > > -- 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.
