I have a couple of dm models that remix a module declared as remixable. In both cases remix has a :for option to create an m2m association with another model.
On my development platform everything works fine. Tables for the remixed models are created in mysql when I run rake db:automigrate (or autoupgrade). When I try to deploy the app to slicehost, one of the remixed models is created fine, just like on the development machine. However the second is created with only the attributes of the remixable module. The foreign keys for the parent model and the :for model are missing. Does this ring any bells with anyone?? The only obvious difference between the two models that remix the mixable is that one declares 'remix n' and the other 'remix 1'. It is the latter that is exhibiting problems. However as I say, in both cases the models are created as required on the development machine. On the development machine I run rake db:autoupgrade manually. For deployment it is executed under the control of capistrano. I guess I can create the missing columns manually on the production machine using phpmyadmin, but it would be nice to know why the table isn't generated correctly to start with. Any clues/guidance would be appreciated. Mark. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
