Re: EOModeling
Re: EOModeling
- Subject: Re: EOModeling
- From: Ricardo Strausz <email@hidden>
- Date: Mon, 12 Jan 2004 13:30:09 -0600
I usually include this atributes in the object itself and use them as
part of the "optimistic locking" mechanism, but its up to you.
On Jan 10, 2004, at 10:56, james cicenia wrote:
First I want to thank everyone who has replied to my "newbie" thread.
I have now refactored my design to break up my "Project" table to
actually
be three ala Chuck's advice.
My new question is... I like to have audit fields in my databases so
that
every row is stamped with a creation date/user and last mod date/user.
Should I start a separate base object that includes these "audit"
attributes
and then create a corresponding "audit" table in the database? Or,
should
I just leave them as attributes in my classes and just store the
attributes as
columns in the database?
thanks again.
-James
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
| References: | |
| | >EOModeling (From: james cicenia <email@hidden>) |