> All migrations are wrapped within transactions. But some schema changes, > such as enum type modifications can not be run inside transactions. > > And code falls with message > > DBD::Pg::st execute failed: ERROR: ALTER TYPE ... ADD cannot run inside a > transaction block at /path/to/project/local/lib/perl5/Mojo/Pg/Migrations.pm > line 66 > > As I can see, for now there is no way to disable transaction for some > migrations. > > So, what do you think, is it a good feature?
Most likely not worth it, since it would require huge code changes. And for enum there are workarounds that work in transactions (rename type, create type, add column, remove column). -- Sebastian Riedel http://mojolicio.us http://github.com/kraih http://twitter.com/kraih -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
