Do changes on 'temporary' record - save back to table when finished


I am doing an app, where the user can edit a ‘Story’. Each story
contains a number of Sections (that in return contains a number of
Routes each, whatsoever). Using AJAX the user can can choose to edit a
Story, and within the same page edit, add and remove Sections. That is
no problem at all, except: None of the changes the user does, should
actually be saved into the database before he chooses to, by clicking
a link or whatsoever. So even though the given Story is being added
and Sections being added/removed/etc, the database should still hold
the old values.

Any ideas how I could do this?

Regards, Harry

On Nov 28, 2007 4:27 PM, harryv [email protected] wrote:

Any ideas how I could do this?
You might try acts_as_versioned.

Greg D.