Closed p-himik closed 9 months ago
It seems that whenever this block gets executed, the transaction has already been started by the wrapping functionality: https://github.com/yogthos/migratus/blob/master/src/migratus/migration/sql.clj#L106-L107
But in the case where the relevant functions below migratus.core/migrate
are considered a public API, just removing that extra transaction would be a breaking change. Perhaps a check for an existing transaction could be introduced? Or a local binding of next.jdbc.transaction/*nested-tx*
to :ignore
(doesn't seem like :allow
should be a preferred choice).
I think using :ignore
here would probably be the way to resolve this. Would you be ok to try it out and do a pr for the fix?
Thanks for the fix, just pushed up 1.5.5
to Clojars with the changes.
Pretty much what the title says. An cleaned up exception data: