I just made a lot of changes to torque.
1. Your schema.xml file can contain more than one database, so that
your application can use more than one database. Some work still needs
to be done so that the tdk will build the TR.props for
such an app, but I still have to catch up on the tdk.
For your schemas that are already built just add
<app-data>
</app-data>
around your single <database></database> tags
There could still be bugs in the code for multiple databases, but it at
least should work the same
as it did for one db.
2. I added several methods to turn foreign key references into
associations between the objects. To check this out modify your
torque.props as stated in the comments. This will generate a lot of
code that I have not tested at all, other than it compiles for me on the
scarab (scarab.tigris.org) schema which tests a couple complicating
factors. I still have not (explicitely) added support for
self-referencing foreign keys, so I am not sure what might happen with
those.
3. The save() method should work better now that I added an is_new
attribute to BaseObject to keep track of whether an object had ever been
saved. I also added a save(DBConnection) method, so that the objects
can be saved as part of a transaction.
Left to do:
As Fedor suggested I think I would still like to implement the object id
as an inner class.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
