Migrations not actually run in a transaction?

[Preetam]

Reading the code for migration, it looks like a transaction is started here:

tern/migrate/migrate.go

Line 339 in ebefbe4

 tx, err = m.conn.Begin(ctx) 

but tx is not actually used to execute the SQL, so the migration is not actually run within a transaction.

tern/migrate/migrate.go

Line 352 in ebefbe4

 _, err = m.conn.Exec(ctx, sql) 

@jackc: Am I reading that wrong or is there a bug here?

[Preetam]

Oh, is it because there is no connection pooling so everything's happening in the same connection?

[Jack Christensen]

Yes. Since it is a single connection it will be correctly executed even though the code does look suspicious. That code could be made clearer. But I'm also hoping to eliminate explicit transaction handling altogether. See #43.

[Preetam]

Thanks!