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 changed from “” 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
-
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
Repository is at http://github.com/rails/rails
Check out the development master (Edge Rails):
git clone git://github.com/rails/rails.git
Creating or reviewing a patch
See the contributor guide.
Creating a feature request
Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too"..
RSL