An upcoming project I need to maintain a log of all updates to documents. The MarkLogic DB is being used to 'mirror' a dataset with changes occuring daily. About 20,000 documents but expected about 10 change daily. For this were not using the Library API (may at a future point but not now).
I was planning on using document properties to store update history. I still think this is a good idea, but there's the need to produce a global report of "all documents updated since XXX". Would this work well by simply querying the document properties ? Another Idea I had is keeping a directory and adding small 'log files' to it for every update that contain the URI and update date. Much like I'd do in an RDB (add a new record for every activity). I suspect this would be in a directory and could grow large over time (but not that large as the change rate is low). However to do this I need to create unique ID's. Is this any better then using the document properties ? Alternatively I could simply append elements to a single audit XML document ... but I suspect that requires loading, inserting, then storeing the document every time and it would grow unbounded. I'm sure this is a common problem, any suggestions ? ---------------------------------------- David A. Lee Senior Principal Software Engineer Epocrates, Inc. [email protected] <mailto:[email protected]> 812-482-5224
_______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
