Migrations doesn't works properly
Reported by Botanicus | June 23rd, 2008 @ 08:24 AM
The migrations doesn't run properly. I'm using merb_datamapper and his dm:db:migrate:up, but it doesn't work. Sometimes it just don't run anything and sometimes it starts from random(?) migration number: http://pastie.org/220292 My migrations are there: http://pastie.org/220331 There are using my merb-fixtures plugin http://github.com/botanicus/merb..., so it's the fixtures method there, but it's not important.
It were it case when it just run bad migration number. Time to time it just run no migration - it execute the task, but nothings happen.
Comments and changes to this ticket
-
Aaron Spiegel October 28th, 2008 @ 07:30 AM
- Tag set to “bug”
You need to add a Symbol #to_proc method to do your migrations the way you have them:
class Symbol def to_proc
proc { |obj, *args| obj.send(self, *args) }end end
That's the error I see in your trace anyways. Although I haven't gotten your fixtures working for me yet either.
-
-
Jonathan Stott (namelessjon) November 30th, 2008 @ 07:38 AM
- State changed from “new” to “hold”
- Assigned user cleared.
I'm pretty certain this is an issue with the code in the migrations, not migrations themselves.
Placing it on hold until it can be confirmed either way.
-
Dan Kubb (dkubb) December 3rd, 2008 @ 12:18 AM
- State changed from “hold” to “invalid”
Followed up with Botanicus on IRC about this a moment ago.
He can't recall what this problem was, but based on the stack trace and Aaron's work, it appears this as caused by using Symbo#to_proc, which isn't available in DM or Merb.
Marking this as invalid.
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 new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Dan Kubb (dkubb)
Rick