Hi Ignacio, I originally hesitated between lifecycles and enum_strings.
After reading the articles on the blog, I settled for lifecycles as being a more elegant solution and then unsuccessfully tried Single Table Inheritance to address the 'no more than one lifecycle per model premise'. The has_one | belongs_to approach works well but uses an extra table....I am a little apprehensive to go back to enum_strings as I feel it will significantly complicate the program logic associated with change of states/transitions most of which are called programatically in different places in my application. Thank you for your help Bernard -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/hobousers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
