Dan Bachelder wrote:
>
> The compile problem... Maybe what needs to happen is to add the key to your new
>user... do the init to create the auto generated classes... Implement the getUserId
>method, THEN add the FK to your other tables... and reinit.... just a thought....
>
> As to how to implement other functionality.. I had trouble using other column in
>TURBINE_USER so what I did was the following..
>
> public void setSomeAttribute(Object obj)
> {
> setPerm("someAttribute", obj);
> }
>
> public Object getSomeAttribute()
> {
> return (Object)getPerm("someAttribute");
> }
>
> what get/set perm does is serialize data to the OBJECTDATA column of the
>TURBINE_USER...
>
> Can someone who knows confim or deny these facts?
>
> I would also like to see what using the actual columns looks like in code...
>
> I thought I saw somewhere that turbine user was using set/get perm for several
>fields (i.e. email, confirm_status) even though there are columns for these
>attributes... I might be making that up though...
>
> thanks...
the approach above is valid for use whether a column exists to store the
data or not. If a column exists with the name used as the key, then the
data is stored in that column. If not, the data goes into the
ObjectData column.
john mcnally
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
