Of course the OP's request is also very naive, as (s)he assumes that all changes will be atomic on a single record.I am not sure I understand your point...
To clarify:
What I want is a way to save an object (representing a row) BEFORE I call any updating methods on it into another table (adding a few extra attibutes e.g user-information).
This will be done in the same transaction that will eventually commit the updates to the original row.
After that I have a "before-image" (the row at transaction start) and an "after-image" (the row after commit) in the database.
Which of my assumption here is naive?
In reply to Re^3: data historization with DBIx::Class
by morgon
in thread data historization with DBIx::Class
by morgon
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |