Hi, It is implemented at the document level.
When a temporal document is updated, the original version of the document is preserved and a copy of the document with the updated data is inserted as a new document. So even if the change Is minimal there will be two documents in the database. Thanks Subhadra From: <[email protected]> on behalf of Grant McKenzie <[email protected]> Reply-To: MarkLogic Developer Discussion <[email protected]> Date: Saturday, October 28, 2017 at 6:34 PM To: "[email protected]" <[email protected]> Subject: [MarkLogic Dev General] Temporal data implementation Hi, I have a question regarding your bi-temporal data feature documented here: http://www.marklogic.com/what-is-marklogic/whats-new/bitemporal/<mailto:[email protected]> Lets say my data is represented as documents with about 1000 unique JSON paths (ie paths to leaf values). The typical change is a single leaf value for one path i.e. 999 values stay the same, one changes. Is the Marklogic temporal data feature implemented at the document level or the individual path/value level? If the former, it would seem like a lot of redundant storage of copies of data that does not change. Thanks.
_______________________________________________ General mailing list [email protected] Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
