Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>We developped such a possibility in our database by keeping track of all transactions applied to the data (not really all, just the ones that are less than 3 months old). The basic idea was to be able to see who did what and when. Each database record, uniquely identified by its GUID, can then be considered as the result of one INSERT, multiple UPDATEs statements, and finally one DELETE statement. As we keep tracks of all these SQL statements, and as INSERTs are global INSERTS (a track of all fields value is kept in the INSERT statement), it is then possible to:</p> <ul> <li>Know who modified which field and when: Paul inserted a new line in the proforma invoice, Bill renegociated the unit price of the item, Pat modified the final ordered quantity, etc)</li> <li><p>'undo' all previous transactions with the following rules:</p> <p>an 'INSERT' undo is a 'DELETE' based on the unique identifier</p> <p>an 'UPDATE' undo is equivalent to the previous 'UPDATE'</p> <p>a 'DELETE' undo is equilavent to the first INSERT followed by all updates</p></li> <li><p>As we do not keep tracks of transactions older than 3 months, UNDO's are not allways available.</p></li> </ul> <p>Access to these functionalities are strictly limited to database managers only, as other users are not allowed to do any data update outside of the business rules (example: what would be the meaning of an 'undo' on a Purchase Order line once the Purchase Order has been agreed by the supplier?). To tell you the truth, we use this option very rarely (a few times a year?)</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload