Sequel migrations creates new db connection
Reported by mis | April 24th, 2008 @ 02:00 AM
Migration code:
def up
SomeModel.create_table!
raise "foo"
end
isn't atomic, i.e table will be crated regardless migraion failure (sequel migrations are atomic).
That's because merb_sequel creates another connection while Sequel models use Merb's one.
Patch attached.
Comments and changes to this ticket
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 »
