I have encountered an annoying issue whereby if I commit more than two transactions one after another, the third will throw a PhalconException with the error message "There is no active transaction"
I have written a really simple gist to illustrate the issue. It can be seen here: https://gist.github.com/clowestab/b94e4c1c48db42bf4b91
The first two transactions are committed successfully and the data is saved in the database. The third crashes with an uncaught exception.
I am using Phalcon 1.3.2 and mySQL.
Does anyone have any insight as to whether this is a bug, or is this a ridiculously obvious oversight (somewhere) on my part?
Edit: To clarify 'transactionManager' is a shared service.