Eh, well the SchemaUpdate code is pretty trivial, if you look at it. Here are the salient lines (I think this is from the 2.0.1 version... 2.0.0 and 2.0.2 use DatabaseMetadata instead of JdbcDatabaseInfo)
JdbcDatabaseInfo info = new JdbcDatabaseInfo(connection, dialect); String[] createSQL = cfg.generateSchemaUpdateScript(dialect, info);
See know i understand your request much better - examples says so much more than words ;)
I don't even know what JdbcDatabaseInfo is (can't find it in my hibernate or jdk source tree ;) - so, I reckon the generateSchemaUpdateScript is "stabilized"....but i would say that is not that big a change to
cope with IMHO ;)
Hibernate doesn't have a solid a barrier between public and private API also (there really has been no need to date). Notice that the relevant method is on Configuration (assume would be a public API) but takes a class from the tool.hbm2ddl class that varies on the version.
Well - it might not be a solid barrier, but whatever is part of the generated public javadoc is the public api ...or even more so, what is NOT part of the generated public javadoc is not part of the public api ;)
/max
------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
