i really don't think this is a good idea but someone made the
suggestion so i need to follow up on it.

we maintain a catalogue of music and video releases and someone has
suggested that our new database be capable of being restored to a
point in time, so say someone stuffs up a mass update of data and it's
only discovered days later we can rollback all the transactions done
in the meantime. can this be done?

i realise there's probably not much in the way of the database doing
this itself so i though we might create some history tables and insert
records into them in after insert/update triggers. in a trigger is
there any easy way of finding which field has been changed aside from
comparing each OLD and NEW field?

TIA