You will have to keep the xml file in sync with the database schema. When it changes, just regenerate your OM objects again. As long as you do not make modifications to any of the Base* or map.* objects, you will be fine. The only thing that torque will not do is delete OM objects when you remove the table definitions. That part you will have to do manually.
-------------------------------------------- Quinton McCombs NequalsOne - HealthCare marketing tools mailto:[EMAIL PROTECTED] http://www.NequalsOne.com > -----Original Message----- > From: Tim Clotworthy [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 25, 2003 2:49 PM > To: [EMAIL PROTECTED] > Subject: How does Torque framework adjust to evolving DB schema? > > > Perhaps I am missing something in the documentation, but I > only see how to install and setup Torque, not how to keep the > various objects in synch with an evolving DB schema. For > instance, as tables are added and removed, fields are added > to existing tables, etc. How does Torque adapt? > > > > A DB schema can't realistically be maintained in XML > (*-schema.xml, or whatever the Torque schema file is). A DB > is maintained by DBAs through sql scripts or through tools > like Erwin, not with XML. > > > > Is there some cache of documentation I am overlooking here, > or is Torque not intended for real databases that must scale? > I would greatly appreciate it if anyone can direct me to how > Torque addresses an evolving database. Thanks very much. > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
