Re: Referential integrity checks for in-memory databases

52 views
Skip to first unread message

Thomas Mueller

unread,
Dec 16, 2012, 8:56:08 AM12/16/12
to H2 Google Group
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 <kaspar....@dreizak.com> 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 h2-da...@googlegroups.com.
To unsubscribe from this group, send email to h2-database...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.

Kaspar Fischer

unread,
Dec 17, 2012, 8:32:55 AM12/17/12
to h2-da...@googlegroups.com
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
Reply all
Reply to author
Forward
0 new messages