finding are available in . dbeaver.ini our article Add line in the end of . -Ddbeaver.jdbc.trace=true dbeaver.ini Restart DBeaver. Connect to your database and browse the metadata in the database queries with results. jdbc-api-trace.log Analyzing contents of you can understand what is wrong with the metadata. Attach the piece jdbc-api-trace.log of the trace file in the GitHub ticket if you 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. JDBC tracing DBeaver

finding are available in . dbeaver.ini our article Add line in the end of . -Ddbeaver.jdbc.trace=true dbeaver.ini Restart DBeaver. Connect to your database and browse the metadata in the database queries with results. jdbc-api-trace.log Analyzing contents of you can understand what is wrong with the metadata. Attach the piece jdbc-api-trace.log of the trace file in the GitHub ticket if you 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. JDBC tracing DBeaver

finding are available in . dbeaver.ini our article Add line in the end of . -Ddbeaver.jdbc.trace=true dbeaver.ini Restart DBeaver. Connect to your database and browse the metadata in the database queries with results. jdbc-api-trace.log Analyzing contents of you can understand what is wrong with the metadata. Attach the piece jdbc-api-trace.log of the trace file in the GitHub ticket if you 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. JDBC tracing DBeaver

exception is shown for the placeholder. If settings.DEBUG == True this message includes the full Django trace. Editors still can edit plugins causing the exception. It can be edited by double- clicking the error