David, thanks a lot for your suggestion, but I think I'll take the easy way
and create views from my tables that mimic the original Turbine tables :)

Pierre

> -----Original Message-----
> From: David Sean Taylor [mailto:[EMAIL PROTECTED]]
> Sent: vendredi, 7. f�vrier 2003 06:00
> To: Jetspeed Users List
> Subject: Re: Turbine user management : change database field names
> 
> 
> 
> On Thursday, February 6, 2003, at 09:01  AM, Pierre Henry wrote:
> 
> > Hi,
> > I use Jetspeed CVS head with the turbine user management with an 
> > Oracle db.
> > I want to change the table name as well as field names for the 
> > TURBINE_USER
> > etc tables.
> >
> > Changing the name of the table is not a big problem : I changed the 
> > names
> > int the build/torque/security-schema.xml, with the javaName 
> attributes 
> > so
> > that the classes still have the same name.
> >
> > But changing the field names (for example I want to have 
> > PC_TURBINE_USER_ID
> > instead of USER_ID to conform to our internal standards) 
> causes some 
> > static
> > fields names in the Peer classes, and the Turbine services refer to 
> > these
> > fields. So if the field names change, I can't compile any more !
> >
> The USER_ID is hardcoded in the Turbine*Management services.
> A recommend patching it by getting the primary key instead.
> You could also extend JetspeedUser and override USER_ID, and not make 
> it final
> Anyway thats a start .... Im sure there will be other minor problems 
> but it should be easy enough.
> The USER_ID is the primary key, and if you take the approach of 
> replacing USER_ID with getPrimaryKey, and send us the patch 
> if it works
> You shouldn't have problems with changing the names of the 
> other fields
> 
> --
> David Sean Taylor
> Bluesunrise Software
> [EMAIL PROTECTED]
> +01 707 773-4646
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

Reply via email to