> From: "Marc Lustig" <[EMAIL PROTECTED]> > > After sorting things out a bit I decided to stay with the old security > service implementation, as using the fulcrum-based sercurity service is > still in an experimental state. I'd like to try this out, but I really don't > have the time for this. > So if the following won't work, I will forget about the foreign-key and > handle the links manually in the code: > > <table name="BASE_ROLE" javaName="BaseRole" alias="TurbineRole"> > <column name="ROLE_ID" primaryKey="true" required="true" type="INTEGER"/> > </table> > <table name="RESELLER_ROLE"> > <column name="RESELLER_ROLE_ID" required="true" primaryKey="true" > type="INTEGER"/> > <column name="NAME" type="VARCHAR" size="255"/> > <column name="USER_ID" type="INTEGER"/> > <column name="ROLE_ID" type="INTEGER"/> > <foreign-key foreignTable="AUDIOTEX_USER"> > <reference local="USER_ID" foreign="USER_ID"/> > </foreign-key> > <foreign-key foreignTable="BASE_ROLE"> > <reference local="ROLE_ID" foreign="ROLE_ID"/> > </foreign-key> > </table> > > Marc I'd be surprised if it did work. Extending turbine-user under 2.1 was a pain, but achievable. Not sure about 2.2bx or fulcrum, but I am pretty sure that Henning's proposal does cater for it.
Cheers, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
