Hi Guillaume.
The trouble with the way it used to work is that we are essentially looking
at tables from all catalogs/schemas. That is the difference between "" and
null in those DBMD params. This causes problems in a few different
situations. First is the case of simply having more than one ta
FWIW, if I change the return ""; to return null;, I get my application to
start \o/.
I'll start testing the application more in depth.
FWIW, I don't know if it's something normal but
AvailableSettings.DEFAULT_SCHEMA is not used in the constructor of
JdbcEnvironmentImpl used when JDBC is available
