You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Jamie Bisotti (JIRA)" <ji...@codehaus.org> on 2005/05/18 15:57:34 UTC
[jira] Created: (MPHIBERNATE-16) hibernate:schema-update does not delete tables
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPHIBERNATE-16) hibernate:schema-update does not delete tables
Posted by "Brill Pappin (JIRA)" <ji...@codehaus.org>.
[ 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPHIBERNATE-16) hibernate:schema-update does not delete tables
Posted by "Jamie Bisotti (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPHIBERNATE-16?page=comments#action_40427 ]
Jamie Bisotti commented on MPHIBERNATE-16:
------------------------------------------
Anyone? Anyone?
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPHIBERNATE-16) hibernate:schema-update does not delete tables
Posted by "Dan Tran (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPHIBERNATE-16?page=comments#action_40428 ]
Dan Tran commented on MPHIBERNATE-16:
-------------------------------------
It is hibernate's issue. Check out the hibernate site
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org