|more useful options|
ORM with version control?by moritz (Cardinal)
|on Feb 06, 2008 at 14:13 UTC||Need Help??|
moritz has asked for the wisdom of the Perl Monks concerning the following question:
The other day I thought about writing a web application that manages material data. It seems straight forward: set up a database, store material name and a bit of meta data, properties + values + units, set up a CRUD interface, and be done.
As always, reality is a poor approximation to my mental model, and things are more complicated: the properties of the materials need to be versioned.
Ideally the object that represents a versioned object (or an object with versioned properties) should ...
Most search queries against the database would only query the current revision, but some would also query all available revisions.
The more I think about the proble, the more I'm sure that such a version aware db wrapper is desirable in many situations, but I haven't found anything useful on cpan and freshmeat.
Now I seek my fellow monk's wisdom and ideas:
(For a while I thought about building it the other way round - storing the data with git, and build a database engine on top of that, but I discarded it as being to much work).
At the moment speed isn't all that important, but it should still be scalable - no O(nē) lookups if possible ;)