Hi merbers/merbists, Learning about migrations through doing, I created a migration that adds a name field to the users table. I also added a property to the model class and then I realized that I am violating the good old DRY and in a very bad way. (I use DataMapper for ORM)
One way to prevent repeating myself is not using migrations. However, I suppose migrations have their role in a production env. since the db:automigrate task drops tables first and db:autoupgrade can not alter table columns. I now realize making db:autoupgrade work might be the solution for this problem but I am very interested to hear your thoughts. Is there another way? Maybe there is a way around the update problem in prod. env.-s and so migrations are simply not needed? Thank you, Balint --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
