ernst leonhard wrote:
> > You don't need to touch the table. Just use User.setPerm() /
> > User.getPerm()
> > for your additional attributes.
> An example:
> I have a 1:N relation to a "CUTOMER" table. So I need to alter the
> TURBINE_USER table adding a new column "CUST_ID" and then I only have to
> use the User.setPerm("CUST_ID", new Integer(199)) /
> User.getPerm("CUST_ID") ?
> Am I right ? I believe no...
Actually, you re right. TurbineUserPeer is a tricky beast. You can add
this column to TURBINE_USER table, to use it as a FK in join statements,
and to use it in Criteria, but at the same time
TurbineUserPeer/DBUserManager
will pick it up automatically. You can use getPerm/setPerm on your
custom
columns added to TURBINE_USER table without modifying a single line of
Turbine
code. (This cool feature was introduced before I started working on the
security system)
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
