historikk med svn (cvs-alternativ)

jf historikk...

Configuration Management Using Subversion: "Relational databases and the relational data modeling concentrate on efficient data storage and retrieval. The history tables do not model naturally with relational databases.
There is no support for versioning from the database. The application has to carefully store the entries into the history tables either through triggers or some other custom techniques.
It's up to the application to determine what changed between versions. The retrieval of historical information from the history tables is also specific to the history table storing the data.
The relational databases should still be the repository for storing and retrieving transactional data. They excel in managing these critical data assets. The shortcomings listed above are confined to storing multiple versions of data entities within the relational data store and tracking such entities over time."

frå opprinneleg artikkel:

"Today's enterprise applications are often required to not just store data, but also keep track of all the changes that are made. This expectation also permeates into an associated set of requirements, such as tracking the reason for each change, the time of the change etc.
....
Applications can use a combination of relational databases and Subversion to satisfy data management and data tracking requirements. .... Subversion would be the primary data source for use-cases for tracking"