[ http://jira.codehaus.org/browse/MPHIBERNATE-16?page=comments#action_45874 ]
Brill Pappin commented on MPHIBERNATE-16: ----------------------------------------- I very much hope that it never removes tables and dumps data... or at least if it ever has the option, it's off by default. When I do a schema update, I *do not* expect data to vanish in fact that would make ting difficult during development because I wouldn't be able to migrate the old data to the new structure. If you want to tables removed, use schema-export and you'll get exactly what you expect. > hibernate:schema-update does not delete tables > ---------------------------------------------- > > Key: MPHIBERNATE-16 > URL: http://jira.codehaus.org/browse/MPHIBERNATE-16 > Project: maven-hibernate-plugin > Type: Bug > Versions: 1.3 > Environment: WinXP(SP2), JDK 5.0, Maven 1.0.2 > Reporter: Jamie Bisotti > > > The first time hibernate:schema-update is run, it works fine. However, if > the *.hbm.xml files are modified so that one of the original tables no longer > exists, a subsequent run of hibernate:schema-update does not remove that > table. Seems like an "update" should make sure the DB's schema exactly > matches what is specified by the *.hbm.xml files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
