Then you need to set up a debugging configuration. Locate the downward-facing arrow right to the bug icon, click on it, then Debug As -> : Database Debug The dialog opens. Set up input values in Ctrl+Shift+Q ##Q Toggles quick diff information display on the line number ruler Ctrl+1 #1 Suggest possible fixes for a problem Ctrl+Y ##Z Redo the last operation Ctrl+Z #Z Undo the last operation Shift+Delete how someone else can recreate the problem. If you posting a bug report check "Error Log" view. If there are any errors related to your bug then post a complete stacktrace. Sometimes there are no errors

Then you need to set up a debugging configuration. Locate the downward-facing arrow right to the bug icon, click on it, then Debug As -> : Database Debug The dialog opens. Set up input values in Ctrl+Shift+Q ##Q Toggles quick diff information display on the line number ruler Ctrl+1 #1 Suggest possible fixes for a problem Ctrl+Y ##Z Redo the last operation Ctrl+Z #Z Undo the last operation Shift+Delete how someone else can recreate the problem. If you posting a bug report check "Error Log" view. If there are any errors related to your bug then post a complete stacktrace. Sometimes there are no errors

Then you need to set up a debugging configuration. Locate the downward-facing arrow right to the bug icon, click on it, then Debug As -> : Database Debug The dialog opens. Set up input values in Ctrl+Shift+Q ##Q Toggles quick diff information display on the line number ruler Ctrl+1 #1 Suggest possible fixes for a problem Ctrl+Y ##Z Redo the last operation Ctrl+Z #Z Undo the last operation Shift+Delete how someone else can recreate the problem. If you posting a bug report check "Error Log" view. If there are any errors related to your bug then post a complete stacktrace. Sometimes there are no errors

Ctrl+Shift+Q ⌃⇧Q Toggles quick diff information display on the line number ruler Ctrl+1 ⌘1 Suggest possible fixes for a problem Ctrl+Y ⇧⌘Z Redo the last operation Ctrl+Z ⌘Z Undo the last operation Shift+Delete click on the warning/error in the log viewer and see the error stacktrace. Please attach it to the bug report. Also, you can open the full log (all error messages) if you need: DBeaver writes different Generating a thread dump without Java For Linux users For Windows users Sometimes (due to some bug) DBeaver UI hangs, freezes, or works incorrectly. It is usually impossible to find the reason for

Ctrl+Shift+Q ⌃⇧Q Toggles quick diff information display on the line number ruler Ctrl+1 ⌘1 Suggest possible fixes for a problem Ctrl+Y ⇧⌘Z Redo the last operation Ctrl+Z ⌘Z Undo the last operation Shift+Delete click on the warning/error in the log viewer and see the error stacktrace. Please attach it to the bug report. Also, you can open the full log (all error messages) if you need: DBeaver writes different Generating a thread dump without Java For Linux users For Windows users Sometimes (due to some bug) DBeaver UI hangs, freezes, or works incorrectly. It is usually impossible to find the reason for

Then you need to set up a debugging configuration. Locate the downward-facing arrow right to the bug icon, click on it, then Debug As -> : Database Debug The dialog opens. Set up input values in Ctrl+Shift+Q ##Q Toggles quick diff information display on the line number ruler Ctrl+1 #1 Suggest possible fixes for a problem Ctrl+Y ##Z Redo the last operation Ctrl+Z #Z Undo the last operation Shift+Delete how someone else can recreate the problem. If you posting a bug report check "Error Log" view. If there are any errors related to your bug then post a complete stacktrace. Sometimes there are no errors

Then you need to set up a debugging configuration. Locate the downward-facing arrow right to the bug icon, click on it, then Debug As -> : Database Debug The dialog opens. Set up input values in Ctrl+Shift+Q ⌃⇧Q Toggles quick diff information display on the line number ruler Ctrl+1 ⌘1 Suggest possible fixes for a problem Ctrl+Y ⇧⌘Z Redo the last operation Ctrl+Z ⌘Z Undo the last operation Shift+Delete click on the warning/error in the log viewer and see the error stacktrace. Please attach it to the bug report. Also, you can open the full log (all error messages) if you need: DBeaver writes different

Then you need to set up a debugging configuration. Locate the downward-facing arrow right to the bug icon, click on it, then Debug As -> : Database Debug The dialog opens. Set up input values in Ctrl+Shift+Q ⌃⇧Q Toggles quick diff information display on the line number ruler Ctrl+1 ⌘1 Suggest possible fixes for a problem Ctrl+Y ⇧⌘Z Redo the last operation Ctrl+Z ⌘Z Undo the last operation Shift+Delete click on the warning/error in the log viewer and see the error stacktrace. Please attach it to the bug report. Also, you can open the full log (all error messages) if you need: DBeaver writes different

Then you need to set up a debugging configuration. Locate the downward-facing arrow right to the bug icon, click on it, then Debug As -> : Database Debug The dialog opens. Set up input values in Ctrl+Shift+Q ⌃⇧Q Toggles quick diff information display on the line number ruler Ctrl+1 ⌘1 Suggest possible fixes for a problem Ctrl+Y ⇧⌘Z Redo the last operation Ctrl+Z ⌘Z Undo the last operation Shift+Delete click on the warning/error in the log viewer and see the error stacktrace. Please attach it to the bug report. Also, you can open the full log (all error messages) if you need: DBeaver writes different

Then you need to set up a debugging configuration. Locate the downward-facing arrow right to the bug icon, click on it, then Debug As -> : Database Debug The dialog opens. Set up input values in Ctrl+Shift+Q ⌃⇧Q Toggles quick diff information display on the line number ruler Ctrl+1 ⌘1 Suggest possible fixes for a problem Ctrl+Y ⇧⌘Z Redo the last operation Ctrl+Z ⌘Z Undo the last operation Shift+Delete click on the warning/error in the log viewer and see the error stacktrace. Please attach it to the bug report. Also, you can open the full log (all error messages) if you need: DBeaver writes different