
auto_upgrade! doesn't apply indexes
Reported by Drew Neil | October 6th, 2009 @ 01:03 PM
DataMapper.auto_upgrade! does not add indexes to a model, whereas DM.auto_migrate! applies indexes just fine.
I already reported this problem on the mailing list here: http://groups.google.com/group/datamapper/browse_thread/thread/d8d5...
I've attached an example script that illustrates the problem.
Comments and changes to this ticket
-
Dan Kubb (dkubb) October 7th, 2009 @ 01:06 PM
- Milestone set to 0.10.2
- State changed from new to accepted
- Assigned user set to Dan Kubb (dkubb)
-
Dan Kubb (dkubb) February 1st, 2010 @ 04:33 PM
- Milestone changed from 0.10.2 to 1.0.0
-
-
-
Dan Kubb (dkubb) February 2nd, 2010 @ 02:47 AM
- State changed from accepted to confirmed
-
John Ramos January 7th, 2011 @ 07:36 PM
I'm using DM version 1.0.0 and am experiencing the same problem. Is it supposed to be fixed in this version?
-
Xavier Shay January 30th, 2011 @ 11:09 PM
- Assigned user set to Xavier Shay
This bug still exists - it also affects dm-constraints/foreign keys (they are not applied)
I haven't investigated too much yet, but my guess is that the code to do this has only hooked into automigrate and omitted auto_upgrade. -
Dan Kubb (dkubb) February 5th, 2011 @ 06:59 PM
- State changed from confirmed to resolved
(from [8678eb399428d0937bb559bb797353915fec879f]) DataMapper.auto_upgrade! can now add simple indexes when adding columns.
[#1079 state:resolved] https://github.com/datamapper/dm-migrations/commit/8678eb399428d093...
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 your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
People watching this ticket
Attachments
Referenced by
-
1079 auto_upgrade! doesn't apply indexes [#1079 state:resolved] https://github.com/datamapper/dm-...