[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-2008) SchemaUpdate
Max Rydahl Andersen (JIRA)
noreply at atlassian.com
Thu Aug 17 07:10:19 EDT 2006
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2008?page=all ]
Max Rydahl Andersen closed HHH-2008:
------------------------------------
Resolution: Rejected
changing a column to be unique requires data changes in the general case and is not dependent on the jdbc metadata api and storing a "previous version" would also not help.
In any case, closing since no real issue reported and the idea of storing a "previous schema" does not provide anything that cannot be done to day.
> SchemaUpdate
> ------------
>
> Key: HHH-2008
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2008
> Project: Hibernate3
> Type: Improvement
> Versions: 3.2.0.cr2
> Reporter: Marvin Herman Froeder
>
>
> According Hibernate Reference Guide - 20.1.5. Incremental schema updates:
> "Note that SchemaUpdate depends heavily upon the JDBC metadata API, so it will not work with all JDBC drivers."
> I use the SchemaUpdate in a emply database, and at the first run they create all database (generate a full ddl).
> Why dont store the ddl at the disk to be used on the update?
> VELO
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list