[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2008?page=c...
]
Max Rydahl Andersen commented on HHH-2008:
------------------------------------------
that "saved schema" would be your previous mapping files (or even a previously
saved Configuration object)
Yes I have thought about doing that, but it would still not give you the delta needed to
do it in the case of you not
having a previous Configuration or that the jdbc db actually have something that was not
previously mapped...
So schemaupdate will work fine with most db's which is fine :)
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira