Hello, recently I've run into strange issue. I've got unit tests which is after every test method rolled back - BUT because of wrong setting of datasource there was commit after rollback of transaction. Here is relevant part of trace of H2:
2016-11-26 23:56:14 jdbc[6]: /*SQL */ROLLBACK; 2016-11-26 23:56:14 jdbc[6]: /*SQL */COMMIT; and data previously rolled back data was visible in new transaction. I don't know what does SQL spec says about that(because its non-public) but think that COMMIT after ROLLBACK and vice versa should not have any effect. Should I investigate it more? Or create test case? (If my assumption that this should not work is correct) Sincerely Petr Holik -- You received this message because you are subscribed to the Google Groups "H2 Database" 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/h2-database. For more options, visit https://groups.google.com/d/optout.
