I'm writing a Rails3 app that collects data as defined by an external source. At periodic intervals, the external source will update their data definitions and require a different schema to be presented to the end-users.
My end users will be at different versions of the external data schema and have legacy data that needs to remain available when they upgrade to the new schema. The external schema changes are thoughtful and can be layered into the database (ie, they are not repurposing a field, but a field might be abandoned in place and future data moved to a new field). I don't think this the problem addressed by model versioning like vestal_versions. My thoughts on this process is to use a flag to indicate which version the user wants to see and then check the flag when creating views to show or hide user elements that are required for the version of the schema that is required. Wondering if someone has a more elegant solution or experience with a similar situation and wants to share. -- 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 rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
