This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Temporal aspects of RIMBAA databases"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) (New page: category:RIMBAA Issue ==Summary== How, in RIMBAA applications, does one deal with 'versions of an object'. *If you receive an update of an object, should the old object be simply ove...) |
Rene spronk (talk | contribs) |
||
| Line 10: | Line 10: | ||
==Discussion== | ==Discussion== | ||
| − | * | + | *Davide Magni: we are taking in to account the new "framework" from jboss to manage the history.. will be relaese with hibernate 3.4 |
Revision as of 09:56, 19 January 2009
Summary
How, in RIMBAA applications, does one deal with 'versions of an object'.
- If you receive an update of an object, should the old object be simply overridden and the new one persisted? Or should the history of the object be maintained? Other objects may reference a specific (old) version of the object.
- This is related to the (potential) requirement to archive ControlActs - to keep a record of who has caused certain changes to happen.
- See also the Core Principles document on 'Accountability'
Analysis
Discussion
- Davide Magni: we are taking in to account the new "framework" from jboss to manage the history.. will be relaese with hibernate 3.4
