When an explicit transaction (started with a BEGIN from the client) ends, it should be rolled back. This is not currently the case when an error occurs, for example.
We should fix this at some point. IIRC it caused some issues when I tested it in development, but in general the way it works makes more sense than before. Must've introduced a bug.
When an explicit transaction (started with a
BEGIN
from the client) ends, it should be rolled back. This is not currently the case when an error occurs, for example.