Hi list !
I'm trying to cleanup the code handling versioning and publication workflow
in zena and thought that the best solution might be to write a custom
association that would take care of creating new versions when needed.

It seems the way associations work as proxy between objects could be a good
pattern to use for versioning.

Has anyone tried this before ?

Is the code around associations going to change a lot in rails 3 ?

Is it just a bad idea to create "has_one_versioned :version" ?

Gaspard

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to