Java requirements

As the tool uses Generics, Java 1.5 runtime is required to be able to create reports sucessfully.

MySQL odbc 3.51 driver limitation

As this version of the odbc driver has a bug during tables names retrieve, the list of existing tables, it won't be possible to report the list of tables. This is mainly due to the fact that thi odbc driver does not conform to the official jdbc api : when a table name prototype is set to null, then all table must be retrieved, and unfortunatelym this is not the case with this driver. Hence, you won't be able to have a complet report on a MySql database if you want to use the MySQL 3.51 odbc driver with the JdbcOdbc bridge.

I have not yet tested it, but it seems like the MySQL Jdbc driver has corrected this bug, hence you should be able to get a full and complete report of a MySQL database.

Oracle 10.02.00.01 odbc driver limitation

As this version of the odbc driver has a bug during tables names retrieve, the list of existing tables, it won't be possible to report the list of tables. This is mainly due to the fact that this odbc driver does not conform to the official jdbc api : when a table name prototype is set to null, then all table must be retrieved, and unfortunatelym this is not the case with this driver. Hence, you won't be able to have a complet report on a MySql database if you want to use the native odbc driver with the JdbcOdbc bridge.

Indeed the Jdbc type 4 (pure Java) Oracle driver (also called thin driver) does implement the spec the right way : so if you want a complete report, you can use Thin driver. Datadirect Wire protocol does implememt it, so you have here still an another way to report your db.

IBM DB2 V8.x ODBC driver limitation

Native IBM odbc drivers for DB2, do not provide (an empty ResultSet) the list of procedures while a call to getMetaData().getProcedures(...). Then the dedicated section will stay empty while using this driver. I have to test that with IBM Type IV jdbc drivers.