I considered that, it is a good approach since it would log all
changes to the DB regardless of the application used to access it. But
it falls short since creating an interface to access that old data is
complex (meaning that we'd have to create a separate non-WO (or
heaviliy modified EOF) application to access old data, or relegate all
requests for old data to DBAs, which is not an option). Unless you
know something I don't :-).
What we need is a simple way for (all) users to see modifications logs
for all records; Who changed What When.
Besides, I want to do this in a non-database-dependent fashion. We're
currently using Oracle (which is serious overkill for our application)
and we're bleeding money through our back ends for it.
Cheers,
- Hugi
On 19.12.2008, at 17:05, Dov Rosenberg wrote:
Most of the projects I worked on with this requirement used the
built in audit tracking functions of the database. Most DBA’s didn’t
leave the requirement to the developers to enforce. That way
everything is tracked in a consistent fashion across applications.
Dov Rosenberg
On 12/19/08 11:57 AM, "Hugi Thordarson" <h...@karlmenn.is> wrote:
Well, for each off-topic post, I guess you must send at least one
on-topic post :-).
So, I work on government databases, and a big part of our
requirements revolves around keeping track of changes. We need to
know exactly how our databases looked at some point in time, and we
need to know who made what modifications when.
So I'm curious about how people are implementing transaction
logging. Attached is a (simplified version of a) class that
demonstrates how I do this today - you can plug it into your
application by calling Spy.register(), for example in yor
application constructor (Oh - and you should probably change the
createAndInsertTransactionForEO() method to use something other
than that EO class called "Transaction" ;-).
Does anyone have any transaction logging stories, examples or code
to share? What is the best way to do this?
Cheers,
- Hugi
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/drosenberg%40inquira.com
This email sent to drosenb...@inquira.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
