Hi Derek, Have a look in the targets in the build.xml There are separate targets for creating your schema sql (project-sql), your OR classes (project-om). what i do after I have data in the tables and I have to alter the schema is run these two targets. I keep the project-sql output as a reference but actually use DDL (ALTER TABEL... ) to change the tables. The project-om target gives me all my OM classes for the new model.
David -----Original Message----- From: Gaasch, Derek [mailto:[EMAIL PROTECTED]] Sent: 11 October 2002 18:37 To: 'Turbine Users List' Subject: schema question Hello, I'm new to Turbine & trying to get my head around how it works / evaluate its use for a new project. I've looked for an answer to this question in a few places, and couldn't find the answer, and apologize in advance if this is either obvious or a topic covered somewhere that I didn't find in my searching... In relation to Turbine/Torque: if I have a schema defined in newapp-schema.xml, which was used to generate my initial tables and the object-relational maps... now, lets say 3 months down the line when I have a million entries in those tables, but for one reason or another need to extend the existing tables is my only method of doing so to: 1) export existing data 2) modify newapp-schema.xml 3) ant init (to create new tables and the OM) 4) import data Seems like there should be some way to modify the schema without doing a full-blown rebuild - is there? I was trying to do this by doing something like: 1) alter the table(s) manually 2) use torque to create XML files (ant jdbc) 3) use torque to create OM (ant om) However, step 2 creates schema of the whole DB (including turbine tables, not just the newapp tables) Any advice or suggestions would be greatly appreciated. Thanks -d -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
