Skip to content
This repository has been archived by the owner on Apr 17, 2018. It is now read-only.

auto_migrate/auto_upgrade do not work with subclasses and storage_names changes #21

Open
solnic opened this issue May 17, 2011 · 1 comment
Milestone

Comments

@solnic
Copy link
Contributor

solnic commented May 17, 2011

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 :)


Created by Kabari - 2010-02-14 01:14:47 UTC

Original Lighthouse ticket: http://datamapper.lighthouseapp.com/projects/20609/tickets/1198

@solnic
Copy link
Contributor Author

solnic commented May 17, 2011

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

by Kabari

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant