Hi Thomas, Thanks for the quick reply and clarification.
I indeed thought that I had found a bug. However, when I returned, after a lot of changes, from file-based to in-memory tests all went well. I have played around a bit with the code in order to be able to reproduce the problem, but no "success" until now. So I assume it must have been a bug in my code. Sorry! Kaspar On Sunday, 16 December 2012 14:56:08 UTC+1, Thomas Mueller wrote: > > Hi, > > > Is this a known limitation of in-memory databases? > > No. > > Could you provide a simple, standalone test case? > > Regards, > Thomas > > > > On Sun, Dec 16, 2012 at 2:22 PM, Kaspar Fischer > <[email protected]<javascript:> > > wrote: > >> Dear everybody, >> >> My code relies on the database reporting referential integrity >> violations. When using H2 (version 1.3.170) file-based databases >> jdbc:h2:~/test, the integrity violation is reported, however, switching >> to jdbc:h2:mem:test causes the violation to pass without errors. >> >> Is this a known limitation of in-memory databases? >> >> Thanks, >> Kaspar >> >> -- >> You received this message because you are subscribed to the Google Groups >> "H2 Database" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/h2-database/-/aK6O8QmpJmEJ. >> To post to this group, send email to [email protected]<javascript:> >> . >> To unsubscribe from this group, send email to >> [email protected] <javascript:>. >> For more options, visit this group at >> http://groups.google.com/group/h2-database?hl=en. >> > > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/lJ5YrGE2MOQJ. 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.
