halfer/Meshing — Issue #28: Consider a code insertion system to capture model load events
Author: halfer
Created: 2011-11-02 09:41:48+00:00
State: open

Presently it looks like the initial prototype will be able to do versioning by capturing preSave and postSave hooks provided by Propel. For existing rows, this will require an extra select to get the initial state of the row - since there is no easy hook to get this in a base class.

This is a tiny bit inefficient, since the initial row state can be captured when the object is first loaded. To do this, I think we will need a code writer to modify model row classes.

Whilst this will save a select, on the other hand it may have more substantial memory requirements, so may not be suitable for large rows. Blob columns would probably need to be lazy-loaded via a save-time select anyway - so perhaps one for performance testing?

This could be a selectable option, rather than a replacement for the existing approach?