I appreciate all your responses, but I don't think we're getting very far. I started this thread because between 2.0.0 to 2.0.1 to 2.0.2 the generateSchemaUpdateScript (the key code in SchemaUpdate) is changing signatures. In 2.0.1 it changed to JdbcDatabaseInfo, and now it's DatabaseMetadata (an unfortunate name since it's just a capitalization difference from java.sql.DatabaseMetaData).
Max Rydahl Andersen wrote:
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 ;)
Are you the CVS user 'oneovthafew'? This is the person making all the mods to this code, so he/she would be able to explain the changes and plans.
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 ;)
I'm not sure what you mean. Configuration is part of the published javadocs. It's method generateSchemaUpdateScript is in the published javadoc. This method's signature depends on classes in the tool package that are not published, and this method's signature keeps changing.
So are you saying the code we're discussing is in the public api or not?
-- Serge Knystautas President Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
------------------------------------------------------- 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
