For me, leveraging database facilities is the most appropriate. I
worked on a very large EOF system for many years, and the way we
decided to deal with this was with database triggers. In our case,
the audit tables were in the same database, but most database systems
have ways of accessing other databases in triggers so that you can
move the appropriate data over.
On May 11, 2006, at 5:32 AM, David Avendasora wrote:
Pierce,
Can you elaborate on some of the easier ways to do this? I am
facing this requirement for a project I am working on now. The
intent is to add the functionality after the core system is up and
running but I'd feel much more comfortable with at least having a
strategy now.
I need to maintain a history of a subset of the date in my database
for use in forecasting and recall.
Thanks,
Dave
On May 10, 2006, at 11:22 PM, Pierce T. Wetter III wrote:
The original author, Milan, isn't replicating the object, he's
migrating it in that he's copying the record from database1 to
database2, then deleting the copy in database1.
I suspect some kind of audit trail, like he doesn't really want
to "delete" the object, as much as mark it deleted by moving it
into the other database. So if I'm following the code correctly,
the second database ends up being a record of all the objects that
have been deleted.
Which, as I said, there's much easier ways to do...so I was
hoping Milan would talk about the real problem...
Pierce
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/lists%
40anderhome.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
