August 17, 2003 at 5:57 pm
Hi,
I am new to this, but do any of you know of decent articles that deal with the above...
eg,
1)a user submits a sproc "spUpdateEntity" via the UI, this sproc updates an existing record in a database.
2) the user changes his or her mind and re-submits the "spUpdateEntity" sproc, with different params( the ID of the exisiting record, remaining constant, of course 🙂 ).
How do you folk store all this info?
Do you use a timestamped column and discard all but the latest entry?
If I wanted to keep a record of all the "spUpdateEntity" sprocs that were executed on the database, would I:
1) store the info from the LATEST sproc execution in the respective table.
2) store the info from previous sproc execution in a separate table.
I'd love to get hold of an article that'd explain these issues, from the bottom up, so far, no joy.
any thoughts appreciated.
cheers,
yogiberr
August 17, 2003 at 6:37 pm
If I wanted to keep a record of all the "spUpdateEntity" sprocs that were executed on the database I would have spUpdateEntity log all the parms to a separate table (also with CURRENT_USER and CURRENT_TIMESTAMP columns).
If I wanted to keep an audit trail on the entity, regardless of whether it done by spUpdateEntity, I'd use a trigger to also log to a separate table.
Cheers,
- Mark
Cheers,
- Mark
August 18, 2003 at 3:00 am
Hi Mark,
Magic,Thanks for that.
yogi
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply