Hello @coleman-rik

Please provide an example of the falling script for testing.

Some footage of the issue also will be helpful.

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.

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.