auto_migrate/auto_upgrade do not work with subclasses and storage_names changes
Reported by Kabari | February 13th, 2010 @ 07:14 PM
I'm not sure if things should work this way, but when a model is subclassed and the descendent model changes self.storage_names it will still update the parent model when calling auto_migrate/auto_upgrade.
example: http://gist.github.com/303755
I attached a patch but I'll leave up to you guys if it's something that needs to be changed :)
Comments and changes to this ticket
-
Kabari March 9th, 2010 @ 09:27 AM
- Assigned user set to “Dan Kubb (dkubb)”
-
Dan Kubb (dkubb) May 29th, 2010 @ 01:59 AM
- State changed from “new” to “unconfirmed”
- Assigned user cleared.
-
Kabari December 14th, 2010 @ 12:30 AM
- Milestone order changed from “0” to “0”
This is still an issue. I've updated the failing example gist (http://gist.github.com/303755) and provided a new patch for the current dm-migrations gem: https://gist.github.com/740076
-
Piotr Solnica (solnic) May 17th, 2011 @ 02:22 AM
- Tag changed from “subclassed model, auto_migrate, auto_upgrade” to “dm-migrations”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Dan Kubb (dkubb)
Kabari
Piotr Solnica (solnic)