A little note for those who did not follow the commit messages last
friday:
I added empty classes for the torque generated om/peer classes. So for
example, if you have a FOO table in your schema, you will get: Foo,
BaseFoo, FooPeer, BaseFooPeer. All the torque generated code will go
into the BaseXXX classes. Foo and FooPeer will be empty and are meant
to be filled with application specific code.
A somewhat flimsy scheme is used to make sure Foo and FooPeer are not
overwritten. A file "firstbuild" must be present in the torque main
directory (where torque.xml is located.) This file should be copied when
torque is first built. Torque then deletes the file during its first
run. So if for some reason you want to regenerate the extension classes
you need to put this empty file back into the directory. It would
certainly be better if an extention file was only written if it did not
already exist, hopefully this is already in Texen or easy to add.
Please note that BaseFoo contains casts to Foo, so other classes should
not extend BaseFoo, If you find it necessary to extend these classes
further you should extend from Foo, but then you will have the problem
that the FooPeer is not going to be returning the object you want, so
you will be back in the position prior to the current changes, so add
your code to Foo.
John McNally
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
