Here are the commit messages describing a few additions/changes I have made recently. Added an interface, Persistent, that can be used in place of BaseObject. So the OM classes no longer have to extend from BaseObject. BaseObject now serves as a default implementation of the Persistent interface. In the schema, two new attributes were added. "baseClass" defines the class the OM classes will extend. The default is BaseObject and if no parent class is desired baseClass="" should work. the "package" attribute can be used to override the target package defined in torque.props. This is primarily to allow multiple database applications to avoid name conflicts. Allow choice of extending an alternate class for the BaseXXXPeer's. Similar to the recent change in OM classes, but this alternate class should extend BasePeer. Fixed bug where the order of the tables in Criteria.addJoin affected which table would get placed into the FROM clause. Both tables will now be added correctly. I moved the joins to there own storage attributes as some of the torque generated objects add join clauses to Criteria, so they could end up overwriting values placed there by users. Added a couple methods to Object.vm to allow low level access to the attributes, which might be more appropriate for general reporting screens. getByPeerName which expects a static attribute for the column from the Peer classes. getByPosition which gives the attributes in the order specified in the xml schema. ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/> Problems?: [EMAIL PROTECTED]
