[eluser]Nameless One[/eluser]
I wrote a piece of code that uses transactions to delete rows from a table using the delete() method and insert new rows into the same table using the query() method. I started the transaction with trans_start() and ended it with trans_complete(). After the transaction, I use trans_status() to check if there was an error and log an error message.
The code worked perfectly until today when I updated to the latest CI 2.0 from bitbucket. Now, the transaction fails, trans_status() returns FALSE, but _error_number() returns 0 and _error_message returns nothing (either NULL or an empty string). Both queries work if I take them out of the transaction, but when they are in the transaction the transaction fails and is rolled back.
Did they change the way transactions work or is this a new bug?
