dBeaver fails to produce error messages when running a SQL script with errors.

[coleman-rik]

Description

When running SQL and or plpgsql and there's an error in the script, dBeaver often won't display the error messages that PostgreSQL returns.
I often find myself having to copy/paste/run the same script in pgAdmin4 to find out what the database believes the error to be.

In these cases, dBeaver just shows the entire script that was attempted to run in the Statistics panel.
If you are extremely lucky, it might list something important in the bottom right of the main window pane.

DBeaver Version

Community Edition 23.0.2

Operating System

Windows 10

Database and driver

PostgreSQL 15, 14, 11

Steps to reproduce

1. write SQL/plpgsql script containing one or more errors in query window
2. try to run it
3. watch a Statistics window pop up with a copy of the script you were trying to run, perhaps with an arrow pointing at some seemingly random line.
4. rerun the script in a different product to see what the error messages that the database sent in response actually are.

Additional context

No response

[LonwoLonwo]

Hello @coleman-rik

Please provide an example of the falling script for testing.

[LonwoLonwo]

Some footage of the issue also will be helpful.

[coleman-rik]

Sure,
Here's the most trivial examples I can come up with. As the SQL gets more complicated, so does the PostgreSQL error messages, as does the importance of actually knowing what they might be.

On a server there there is no database public run this statement:
grant all on database public to postgres, minion, bob, stow, ditto, nagios;

the result on dBeaver is:

the same command run against the same server in pgAdmin4 returns this:

On a server where there is a database idp, but the role bob doesn't exit run this statement:
grant all on database idp to bob;

the result on dBeaver is:

the same command run against the same server in pgAdmin4 returns this:

there is nothing in the Output tab in dBeaver, there is nothing in the lower right corner of the application window in dBeaver. What you see in those screenshots is all that dBeaver will tell you when there's an error in your SQL statement.

I hope that helps.

[E1izabeth]

Maybe you acidentialy hide the left part of the error view, so it looks like on the following screenshot.

Could you try clicking on the small blue arrow there to restore the view. Usually it looks like on the following screenshot for me

Please let me know if it helps.

[coleman-rik]

dBeaver 23.0.4 now shows a message at the very bottom, that wasn't there in 23.0.2.

Hitting the blue arrow, I had no Idea it was supposed to be a button, reveals this:

dragging it to the right revealed this:

So all in all, it seems that in 23.0.4 at least there's an error message in the window frame, and now that I know that the symbol pointing to the SQL (which is just a waste of space, as the exact same SQL is right above it) can be dragged open to reveal the error message, I won't have to rerun my code in pgAdmin4 as often.

Why doesn't that error panel open by default when there's an error? Simply reiterating the same SQL that is in the query pane doesn't help the end user and only serves to hide the error message.

thanks.

[E1izabeth]

By default, the result panel with error is extended like on your second picture.
The right-side area with the query text might be useful while running long scripts with multiple queries.

I assume the issue is solved, so I close it.

[coleman-rik]

thanks.
unfortunately, the result panel is not extended by default. by default it only shows a copy of the SQL query from above and a little blue arrow on the left apparently pointing to the copy of the SQL code.

[E1izabeth]

It shouldn't be so. Probably something went wrong for you. Could you try resetting UI settings (https://github.com/dbeaver/dbeaver/wiki/Reset-UI-settings) and check, if it helps?

[coleman-rik]

that seems to have corrected that default behavior,
thanks.