In some cases, custom JDBC drivers work incorrectly in DBeaver - they show the wrong metadata like table columns, constraints or foreign keys.
It usually happens because the driver is not compliant with the JDBC API specification and DBeaver cannot correctly interpret the metadata provided by the driver.
To understand what is going on inside the driver, you can enable JDBC tracing:
dbeaver.inifile (it is located in the same folder where DBeaver is installed)
- Add line
-Ddbeaver.jdbc.trace=truein the end of
- Restart DBeaver
- Connect to your database and browse the metadata in the database navigator/object editors.
- In DBeaver Workspace go to
jdbc-api-trace.logcontains all JDBC API invocations and all queries with results.
Analyzing contents of
jdbc-api-trace.log you can understand what is wrong with the metadata. Attach the piece of the trace file in the GitHub ticket if you think that something is wrong on DBeaver's side.
WARNING: disable JDBC tracing in your regular work. Enable it only for debugging. The trace generation decreases application performance and may produce huge log files.