Yeah: Thanks for this great 1.4.200 H2 release: We had bugs in our tests, which weren't found because of bugs in H2. Now these bugs in H2 are fixed :)
Background: It seems that it could happen in 1.4.199, that being in a schema a select from a table which doesn't exist (being on the wrong schema) could receive a table with the desired name from another schema. Thanks you very much -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/cb50b993-ffab-4447-bb4d-e5cca2d54c8d%40googlegroups.com.
