[ssfthurber]

instead of update in place my application requires versioning. so in the event of an update i need to end up with the old version of the record marked as expired and a new version inserted.  my thought was to use update callback to both insert the new record and update the old version marking it as expired.

all the callback examples show return with a single db call. is this a limitation or is there a way to code two db calls, as required by my use case?

[davidoster]

I would use http://www.grocerycrud.com/documentation/options_functions/callback_before_update

and within this function I would do two things,

1. change the versioning field to mark this record as an older one and

2. with the same(previous) data insert a new record

 

The return is used when some (or all of the data) need to be altered before they are sent to the db, as it is in your case.

But at the same time you can do as many db calls within this callback. There is no limitation what you can do.

[ssfthurber]

yes, this is the way to go. thanks.