Re: schema help

From: Rob <rmpsfdbs_at_gmail.com>
Date: Thu, 27 Dec 2007 09:02:04 -0800 (PST)
Message-ID: <d1e1a0e2-e535-4f3b-a7c2-b88385a184ee_at_d21g2000prf.googlegroups.com>


I'm giving you the last word here.

<<<
My comments are a suggestion for how the RDBMS should provide specialised support for a History-DB. This would include the total ordering (or better still use vector times and a partial ordering), efficient sequential writing of new operations to disk, and concurrent
access for readers of the operations. I don't think any commercial RDBMS provides these capabilities.
>>>

The revised question is then , Are EXISTING RDBMSs appropriate for solving
the OP's requirements, and if so, is it better to a.) maintain current state, periodically take a snapshot and measure state change as the difference between snapshots, or, b.) maintain a sequence of states in the database and periodically measure state change from (this sequence in) the database?

(For purposes of this question, a snapshot is the response to a query, stored externally as a file or in a data warehouse.) Received on Thu Dec 27 2007 - 18:02:04 CET

Original text of this message