Re: Looking for general ideas on keeping transaction history in a database

"sdenney" <sdenney_at_healthetech.com> wrote in message <news:6CC69F9B57AB0A7C.F069E97D678E2745.13F59057E89CBEDC_at_lp.airnews.net>...

> I am curious how people keep transaction histories so that every transaction
> that is made to a database is archived so that it can be rolled back. Sort
> of a fool-proof way of keeping data in shape and recoverable. Does anyone
> do this? So that a certain record or set of records could be rolled back to
> where the bad transaction happened?

If I keep such logs, I write them to plain old human-readable text files that can be copied to, say, a CD-R at the drop of a hat... any hat. I might also keep a history within the database, but it's the text file and/or the DBMS' transaction log I'll use to recover from gremlins. What do you mean by a "bad transaction"? The idea of being unable to reverse something without having to also undo all subsequent transactions would make me rather twitchy, but that's what I get for having worked at a bank! =)

--
Joe Foster <mailto:jfoster_at_ricochet.net>  Space Cooties! <http://www.xenu.net/>
WARNING: I cannot be held responsible for the above        They're   coming  to
because  my cats have  apparently  learned to type.        take me away, ha ha!