Re: [PhillyOnRails] Looking for help overriding clear_old_version in acts_as_versioned

["Mark Chadwick" <mark.chadwick@gmail.com>]

Mike,

I could be mistaken, but I believe acts_as_paranoid will just set the deleted column to true for a "deleted" row.  You could just emulate the AAP behavior, and instead of deleting, just do:

my_model_instance.deleted = true
my_model_instance.save

Then, AAR won't really care what happened (unless you're revisioning the deleted column), and it should stay out of your way, as AAP is going to filter it out of queries.

-Mark

On 2/14/07, Mike Zornek <mikezornek@mikezornek.com> wrote:

For a new rails app I'd like to utilize a combination of acts_as_versioned
and acts_as_paranoid to allow me to track the lifespan of objects (a real
client need).

So far it's working fairly well except that when I destroy an Active Record
object the acts_as_versioned plugin is deleting all of the old versions.
It's using a method called clear_old_version and in the docs it says:

http://ar-versioned.rubyforge.org/

> Clears old revisions if a limit is set with the :limit option in
> acts_as_versioned. Override this method to set your own criteria for clearing
> old versions.

My question is: How do I override it. I added a method to my Active Record
model but I don't think it's getting called. Perhaps it's because this
clear_old_version is buried in a stack of Modules.

Any help is appreciated. Thanks.

~ Mike
--
Work: http://ClickableBliss.com
Play: http://MikeZornek.com

_______________________________________________
To unsubscribe or change your settings, visit:
http://lists.phillyonrails.org/mailman/listinfo/talk

_______________________________________________
To unsubscribe or change your settings, visit:
http://lists.phillyonrails.org/mailman/listinfo/talk