At 02:48 PM 9/5/01 -0700, you wrote:
> >
> > I went thro' org.apache.turbine.om.peer.BasePeer.java class which is
> > supposed to be the super class for all the peer classes generated by
> > Torque. Method "doDelete" in BasePeer class does support Cascading
>deletes,
> > if Criteria for delete is set like that. So Turbine code has to set the
> > delete as Cascade in Criteria object and then it will work fine (so may be
> > then we have to touch Turbine code as well). I am saying this by looking
>at
> > the BasePeer.java code. **Some one has to confirm this.***
> >
> > My question is:
> > Once we decide to use TURBINE tables as foreign key tables for respective
> > tables in JETSPEED PSML, then,
> > do we have to chnage the XML Database schema file for TURBINE to include
> > all the Jetspeed Psml related Tables?
> > Basically, point is do we have to regenerate Torque/Peer classes for
> > Turbine? Or will TurbineMapBuilder figure that out, at run time, if all
>the
> > tables exist in same database?
>
>I don't think that is necessary. Here is a Torque foreign key definition
>taken from the Turbine site:
>
>...
> <foreign-key foreignTable="SCARAB_ATTRIBUTE">
> <reference local="ATTRIBUTE_ID" foreign="ATTRIBUTE_ID"/>
> </foreign-key>
>
Yes, but this syntax will be valid only if you have the entire schema
defined in one single file. So we need to modify, turbine-schema.xml file,
with all the Jetspeed tables added, right?.
-Atul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
