Re: catalog versus schema

[Bryan Young]

My experience with MySql so far has been very frustrating. The latest frustration has been trying to get DBUnit to work well with MySql. DBUnit expects to be able to call con.getMetaData().getTables(null, null, "%", null) and get a listing of all the tables in all the schemas -- as it should according to the JDBC javadoc. MySql returns nothing.

Even if I have DBUnit limit the query to tables in the same schema, I have problems. I can set the 'catalog' rather than the schema to get the correct tables returned, but the result set returned has the schema values in the catalog field. DBUnit doesn't expect this of course -- and why would they?

Instead of posting messages in the forums explaining the inner workings and historical baggage of MySQL to those who get strange value from your JDBC driver, maybe you should just change the code to conform to the JDBC spec and the javax.sql documentation?

The whole point of JDBC, after all is to hide your server's historical baggage behind a standardized interface -- so it can be easily plugged into tools like DBUnit!