[Please quote when replying -- otherwise, it's hard to figure out what you're replying to.]
Chris Habgood wrote: > Well sort of. Basically you have a ton of states that are defined in > the model, is there away to take those stares and define them in the > db and have a fk pointing back to the main model. Normalized db. > Repeated data extrapolated into another table. That's easy enough to do in general. You were asking about AASM, though, and I'm not sure how to get that working without patching AASM. A patch shouldn't be difficult, and I've also been bothered enough by AASM's lack of normalization that I might write one at some point... ...but for now, I've kind of accepted the lack of normalization as the price to pay for easy AASM management. Perhaps an enumerated type would be a good compromise, if your DB supports it (there are plugins to get enumerated types working with Rails). Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en.
