--- In firebird-support@yahoogroups.com, Jonathan Neve wrote:
> [...] So I ended up having to
> restore a backup, and pump an old version of the record back to the DB.
> So it went ok, but I can understand the potential usefulness of some
> sort of "Undo-after-commit" feature, or something like that...
>
> Or else, what might be good would be something like a shadow file, in
> which, all obselete record versions are dumped, as and when they become
> obselete.

I can't judge whether your "keep alll old versions around"
idea will fly.

But generally I assume, that the database layer isn't smart enough
to handle wrong doings in the past without disturbing something
that happened thereafter. As, in the general case, all sort of
triggers that should have triggered, didn't (and vice versa) because
of the different situation with or without the accident in the past.

And the RDBMS doesn't know enough to handle.

Isn't this a job for the proverbial middle layer? (Which then of
course has to write it own logs of "Business Transactions", probably
with rich context).

Regards,
Peter Jacobi