Move to new ChangeLogging behaviour

[pwhittlesea]

Ensure that a separate table is used for each loggable item.
Make sure an upgrade route is provided.

[antineutron]

Found a couple of tools that (should?) do this for us:

http://www.webtechnick.com/wtn/blogs/view/248/CakePHP_Icing_Plugin_Versioning
http://bakery.cakephp.org/articles/alkemann/2008/12/18/revision-behavior-revision-control-made-easy

Also found this article on versioned DB migrations:

http://bakery.cakephp.org/articles/sayb/2012/11/24/versioned_dbmigrations

I don't think we're using the migrations stuff yet - maybe we should? :-)

On 28/01/2013 21:49, Phillip Whittlesea wrote:

Ensure that a separate table is used for each loggable item.
Make sure an upgrade route is provided.

—
Reply to this email directly or view it on GitHub
https://github.com/SourceKettle/devtrack/issues/274.

Web Bug from
https://github.com/notifications/beacon/RiD5rqD6Iyy1babGUlCka5pVw9tMn_ezP6l88jrX9wTWGnPDkEE5-zzieh3bhgWn.gif

[pwhittlesea]

My worry with full versioning is that we will be storing the whole object and not just the changes, which is all we need for history