| |||||||||||||
Accounting systems: a rant and a questAccounting systems: a rant and a questPosted May 20, 2012 19:31 UTC (Sun) by renszarv (guest, #84721)In reply to: Accounting systems: a rant and a quest by fest3er Parent article: Accounting systems: a rant and a quest
btw, your requirements are contradicting. If no UPDATE-s are allowed, how/when the 'record retirement date` is modified in that record ? :)
(Log in to post comments)
Accounting systems: a rant and a quest Posted May 20, 2012 21:12 UTC (Sun) by Cyberax (✭ supporter ✭, #52523) [Link]
You don't.
Instead you create a _new_ record pointing to the old record as the predecessor. So that all new documents from that point on would use the retiree's record, not the old ones.
Accounting systems: a rant and a quest Posted May 21, 2012 5:32 UTC (Mon) by jackb (subscriber, #41909) [Link] A bitemporal data model works like that. Information is only added to the database, never deleted or changed.
|
|||||||||||||