Re: EOModeling
Re: EOModeling
- Subject: Re: EOModeling
- From: Karl Gretton <email@hidden>
- Date: Sat, 10 Jan 2004 13:35:02 -0500
Hi James,
I always take the latter approach since this is just time stamp
information. You can have this updated or set automatically by
including methods in your EO classes. We use awakeFromInsertion to
initialize such audit fields on our tables.
Karl
On Jan 10, 2004, at 11:56 AM, 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>) |