On Thu, Mar 4, 2010 at 9:14 AM, Michael Pavling <[email protected]> wrote:
> Migrations are a "point in time" reference about the structure of a database. > > If they alter *data* then they are binding tightly to the models - and > you can no longer have a later migration that adds/removes/renames > columns, because those columns will be set in the data in an earlier > migration. Huh? I can't even parse that last part - "columns set in the data in an earlier migration"?? What does that mean? I can't see how a db column being populated with data is going to keep you from using a migration to update/change it, structure- or content-wise. > Similarly, you can now no longer alter your models, because some > migrations rely on the operation of the model at that "point in time" Likewise, sorry, that makes zero sense to me. I can't alter a model because it was altered before? What?? Maybe an example would help... -- Hassan Schroeder ------------------------ [email protected] twitter: @hassan -- 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.
