On Nov 14, 2007, at 7:42 AM, robert wrote:
> I'm not sure if I like "property" (for model/database setup) being > within the model itself. That's mostly because I really like > migrations being extracted from the model. I think migrations are a nice history myself. But I always thought it was a bit of a pain doing something in two places (i.e. add a column in a migration, and a model). And, actually, with associations, in three places. This has always nagged at me a bit. A question about datamapper. One nice thing about migrations is you were in complete control, so you could be careful to preserve your data. For example, maybe you just want to resize a string column from 80 to 128? Or, maybe you need to rename a column? How can Datamapper handle these cases without being destructive? -- Stephen Waits [EMAIL PROTECTED] http://swaits.com/ --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
