Ok, thanks Thomas for your help. I actually have an old version of H2: 1.1.114 (2009-06-01), so it may explain the behavior, but it's a legacy system, and I prefer to avoid the change of version for the moment.
But at the same time I run your test case with my environnement and .. it works correctly ! The data are correctly persisted as long as I let him some time to flush (Thread.Sleep(1000)) or when I explicitly ask for the flush via "checkpoint". So maybe the problem is rather in the JPA/Hibernate/H2 dialect layer... I'll try do dig that out, but if anybody as some idea to share, I'll be glad to here them. Thanks again Thomas for your contribution, it is still a step forward for me. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
