halfer/Meshing — Issue #38: Implement a save strategy provider
Author: halfer
Created: 2011-11-27 17:35:55+00:00
State: open

I [recently outlined](http://blog.jondh.me.uk/2011/11/relational-database-versioning-strategies/) some different strategies to save versioned data to the database. In the language of that article, Meshing is heading towards a *Version Previous* implementation; that is fine, but it would also be nice to try *Version Current* which offers a slightly better performance in return for an slightly larger space overhead.

To this end, I think a Save Strategy Provider would be a good idea, so for any node we can specify which of these approaches are to be used. This approach would be very useful in testing, so immersion testing can be used on both models, to see which offers better performance across a range of operations (new record, record update, retrieve latest record, retrieve record of specified version, etc).