See testcase here: https://gist.github.com/dleavitt/0f413129f9fbefe681f9d49e8b86bad6#file-testcase-rb
When a Sequel transaction fails due to a deferred constraint violation, it calls "COMMIT" anyway, which leads to a PG warning: "WARNING: there is no transaction in progress" Seems like a bug but not sure if it's readily fixable? Is Sequel able to check if the transaction was already rolled back? It also got me wondering why Sequel defaults to wrapping "save" and friends in explicit transactions - I know most ORMs do this but wasn't sure why. What would I be losing if I set "use_transactions" to false on Sequel::Model? Thanks! Daniel -- You received this message because you are subscribed to the Google Groups "sequel-talk" 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/sequel-talk. For more options, visit https://groups.google.com/d/optout.
