support for migrations wrapped in transactions [postgresql] about sql-migrate

[rubenv]

Migrations are executed in a transaction automatically. No need for manual begin/commit.

On 27 Sep 2014, at 21:00, Raphael Randschau [email protected] wrote:

Hey,

I'm currently migrating my migrations from theory/sqitch to sql-migrate, mostly because I want to ship the migrations /w my binary together.

I ran into problems because all my migrations look like this:

BEGIN;

SET client_min_messages = 'warning';

CREATE TYPE xxx AS ENUM ('a','b');
CREATE TABLE public.xxx ();

COMMIT;
Migration failed: pq: unexpected transaction status idle
Is this any issue with sql-migrate or the postgresql library in use? If you could point me into the right direction I could start working on a pull request so migrations are properly supported.

thanks!

—
Reply to this email directly or view it on GitHub.

[nicolai86]

thanks for the quick answer!