On Thu, Jun 14, 2001 at 02:15:50AM -0700, Guido Sohne wrote:
>
> Mike Haberman wrote:
>
> > I can think three ways to handle the blob/setPerm issue in User.
>
> 4. Instead of a blob make a foreign key into a User table in the OM that has
> to
> contain the actual data the application will require on its users. That way
> the
> table can be extended in project-schema.xml by simply adding new Fields.
> That would mean that the OM for that will be automatically be created too.
>
> mike
Sorry for the delay (out of town last week)....
That's fine, but the sql for the User Table could not be provided
statically, unless we know the name of the new table. Users would have
to modify the turbine-schema.xml file for the foreign key stuff.
I think extending the User, in this case, makes more sense. Also, it
will be easier for the programmer to deliver a User object to the
template writer if all the data is contained in a single object.
I think you can configure torque to generate an Object that extends
off any base class not just the standard BaseObject/BasePeer. So
users can still use project-schema.xml file approach for generating
the class. Is that not true?
We could provide an default ApplicationUser template that extends
TurbineUser for people to use.
mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
