This project is archived and is in readonly mode.
assume_migrated_upto_version doesn't work with non-standard migrations path
Reported by Lukas Biewald | June 5th, 2008 @ 08:32 PM
/db/migrations is hardcoded as the path for assume_migrated_upto_version, which causes this function to fail silently if this is not the correct path.
Attached is the patch I used to make it work. I'm completely unfamiliar with the codebase, so I don't know if this is useful, but it made things work for me.
Comments and changes to this ticket
-
nikz August 5th, 2008 @ 12:02 PM
- Tag set to “activerecord”
Hey there!
This looks fairly easy to fix but (just out of interest):
- Is there a reason you're using a non-standard migrations path?
- How are you using the non-standard path? For instance, /db/migrate is hard-coded into the db:migrate rake task?
Perhaps if there's good reasoning behind it, you can discuss it on the mailing list and come up with a config setting?
Correct me if there's anything out there - I only looked around the code for 5-10 minutes and googled briefly :)
Nik
-
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
People watching this ticket
Lukas Biewald
nikz
Pratik
RSL
Attachments
Tags
Referenced by
-
189
ActiveRecord::AssociationTypeMismatch with same class name -- added helpful exception message
I'm not sure why it's just showing the class name rather...