Hi Noel, I've created repo which contains this isolated problem. But I can't reproduce it without Spring and Hikari Connection pool. So therefore I think it should not be bug in H2 but in Hikari or Spring or I have some missconfiguration.
I am unsure if this numbers in log does corelate with session number? 2016-11-27 20:35:34 database: connecting session #4 to C:/Users/User/test/strangeTransaction <- This '4' 2016-11-27 20:35:34 jdbc[4]: <- This number '4' /*SQL */ROLLBACK; Does it corelate? If yes, then Spring or Hikari is propably rolling back another connection that it should :( PS: repo is available here: https://github.com/petrholik/strangeTransactionBehavior Sincerely Petr Holik Dne neděle 27. listopadu 2016 7:55:49 UTC+1 Noel Grandin napsal(a): > > that does sound dodgy, a commit directly after a rollback should have no > effect > > yes, a test case would be very useful > > -- 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.
