Hello, I don't see how http://db.apache.org/ddlutils/ would be useful - how would it know about the exact table/column etc. types and other information that OpenJPA holds?
But: Have you seen https://issues.apache.org/jira/browse/OPENJPA-601 ? It seems that problem that I ran into and ranted about on http://markmail.org/message/fff4bjphzizeufsq (RE: generate DDL script without database acces), which I'm assuming is also what's bothering you (and others...) has been addressed in OpenJPA v1.2.0 ... We haven't had time to verify and integrate that yet, but assuming it works more sensibly now than it used to (this problem already existing in Kodo BTW, as far as I remember... ;-), I was hoping we'll simply be able to use the mappingtool in the normal OpenJPA intended way, but run it several times, giving it a different DBDictionary configuration each time, to get the DDL scripts for the databases you want to support. Makes sense? Regards, Michael -----Original Message----- From: Venu Kadari [mailto:[EMAIL PROTECTED] Sent: dimanche, 31. août 2008 02:53 To: Michael Vorburger Subject: Generate DDL Script without database access Hi Michael, I am currently tackling a problem where we have to maintain DDL scripts for all different databases. Obviously, this is not desirable and we want to move away from it. I saw your mail here. http://markmail.org/message/fff4bjphzizeufsq I am thinking of using "The Appache DB Project (DDLUtils)" to solve this problem. Where you successful in using DDLUtils? Can you generate DDL script for various databases without an actual connection to the database? Thank You Venu Kadari ____________________________________________________________ This email and any files transmitted with it are CONFIDENTIAL and intended solely for the use of the individual or entity to which they are addressed. Any unauthorized copying, disclosure, or distribution of the material within this email is strictly forbidden. Any views or opinions presented within this e-mail are solely those of the author and do not necessarily represent those of Odyssey Financial Technologies SA unless otherwise specifically stated. An electronic message is not binding on its sender. Any message referring to a binding engagement must be confirmed in writing and duly signed. If you have received this email in error, please notify the sender immediately and delete the original.
