So I installed Cubrid and as far as I can tell, it simply doesn't support schemas (at least not the way the SQL standard defines them or the JDBC API expects them).
The driver does not return any schema information for the tables
(the screenshot is from the demodb)
This means there is a table named "public.athlete" that does not
have a schema.
The "schema support" seems to be just a text replacement feature in the parsed name as far as I can tell.
The JDBC driver also confirmst that cubrid does not support
schemas at all.
FEATURE | VALUE
supportsCatalogsInDataManipulation | false
supportsCatalogsInIndexDefinitions | false
supportsCatalogsInProcedureCalls | false
supportsCatalogsInTableDefinitions | false
supportsSchemasInDataManipulation | false
supportsSchemasInIndexDefinitions | false
supportsSchemasInProcedureCalls | false
supportsSchemasInTableDefinitions | false
There are some situations where SQL Workbench gets things wrong,
if the table name contains a dot. Generating the queries for the
FK dependencies seems to be one of them. If Cubrid had chosen to
delimit the prefix using a different character, e.g. the $ sign
("public$athlete") then this wouldn't happen.
I will see if I can fix that.
To view this discussion on the web visit https://groups.google.com/d/msgid/sql-workbench/5b00424e-a87a-b5ca-78b9-c35bcdadd4e3%40sql-workbench.net.