Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

This project is archived and is in readonly mode.

assume_migrated_upto_version doesn't work with non-standard migrations path

#343

/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.

Reported by Lukas Biewald · June 5th, 2008 @ 08:32 PM

State: invalid
Milestone: none
Assigned to: nobody
Importance: none

Activity

  1. nikz
    nikz
    • 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

    August 5th, 2008 @ 12:02 PM

  2. Pratik
    Pratik
    • State changed from new to invalid

    What Nik said.

    August 5th, 2008 @ 12:58 PM