is there no stacktrace ?
and are you sure you have both a schema and catalog named testdb in your mysql setup ?
It's not executing and there's nothing in the Eclipse logs so there's no stack trace. This error just shows up during validation in Eclipse. (The properties of the error in the Markers view gives no extra information.)
If I run the query: select * from information_schema.tables where table_schema="testdb" it tells me that TABLE_CATALOG='def'.
No matter what value I set hibernate.default_schema to it simply updates the error message and complains about that schema not being found, even if I set it to 'def'. Also, if I remove the hibernate.default_schema line from my properties it reverts back to 'testdb' as the catalog it is looking for. The same occurs if I alter the code and explicitly name the catalog in the @Test parameters.
I think you are bumping into Eclipse Dali validation bug when it comes to mysql and catalog handling.
Can you show the full validation marker ? just right click and copy it and then paste content here.
Is this what you mean?
Description Resource Path Location Type Catalog "testdb" cannot be resolved for table "test_table" TestTable.java /testdb/src/main/java/com/company/model line 14 JPA Problem
Edited for spelling.
So you do not have the catalog listed in your java class ?
if you do not, go into JPA Facet properties and define the connection to use and in here you can customize/override the default catalog/schema. See if that works?
The catalog isn't listed in the class but if I add one it just updates the error message.
In the JPA settings, if I select to override the catalog, nothing is in the dropdown. If I select to override the schema the expected value _is_ in the dropdown so it seems it's not getting any catalog names from the connection?