Autoupgrading is dumb right now. Where there's any possible confusion DataMapper.auto_update! doesn't do anything (so as to protect your data), so far as i know. DataMapper.auto_migrate! should blank your db and rebuild the thing from scratch, so that should work. If it doesn't, that's definitely a a bug.
-knowtheory On Sat, May 9, 2009 at 5:46 PM, MilesTogoe <[email protected]> wrote: > > running datamapper with ruby 1.9.1 and sqlite3 in a "model.rb" with > automigrate turned on. If I change the name of a class field in my > model.rb, save it, then in irb if I type require 'model.rb' get a true > response, then I enter sqlite3, the field name has not changed. Is > there a bug with this ? Am I missing some update command ? Is the old > value being cached somehow ? > thks for any help. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" 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/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
