Okay, so I found the workaround myself. However, I'd still like to know if I'm working around a bug or a feature.
class SignupConductor ... def self.auto_migrate_down! repository_name end def self.auto_migrate_up! repository_name end def self.auto_upgrade! repository_name end end On Oct 17, 1:15 pm, aanand <[EMAIL PROTECTED]> wrote: > Hi. I'm getting behaviour that I'm not certain is incorrect, but is > certainly undesired, so if it's not a bug I'd like to know if there's > a workaround. > > The relevant code is here:https://gist.github.com/f6149878465bee298c61 > > As well as a default, database-backed repository, I'm using an in- > memory repository to work with temporary models - i.e. my > SignupConductor class. > > When I perform an auto_migrate! or auto_upgrade!, however, it attempts > to automigrate/upgrade SignupConductor, leading to a > NotImplementedError. > > I tried specifying the :default repository, thinking that this would > restrict migrations to only model classes which use :default, but it > instead tried to migrate SignupConductor as though it were using the > default repository and create a table for it. > > In this particular case I haven't defined any DM-style properties, so > it failed with a syntax error, but in any case I don't want it to try > to create a table in the first place. > > Is this a bug? If not, is there a workaround? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
