Query script errors not highlighted, only position count provided. #11907
Replies: 5 comments 1 reply
-
Thank you for the report. Highlighting is not implemented yet. We are going to do it. |
Beta Was this translation helpful? Give feedback.
-
Hello, @coleman-rik, |
Beta Was this translation helpful? Give feedback.
-
there is no update for more than a month. |
Beta Was this translation helpful? Give feedback.
-
#11869 Thanks. |
Beta Was this translation helpful? Give feedback.
-
Hello @coleman-rik, We don't parse the statements by ourselves, the errors are sent by the server itself, as mentioned multiple times before. The same thing is for the error message - the code position is the part of it, we don't modify it. |
Beta Was this translation helpful? Give feedback.
-
System information:
Windows 10 x64 Enterprise
Connection specification:
PostgreSQL 11
org.postgresql:postgresql:RELEASE [42.2.18]
No
Describe the problem you're observing:
When running queries in DBeaver, whenever there's an error all DBeaver provides is a general description of the error and a Position: xxx. It doesn't provide a line number nor any indication of which query has an error at Position: xxx.
Unfortunately when running large queries (the one I am working on at the moment is over 1,000 lines comprised of more than 20 individual queries) this doesn't help identify where DBeaver thinks the error may be. This is compounded by the fact that the query editor in DBeaver doesn't have any indication in the status bar (or anywhere else I can find) at least telling you what position the cursor is currently at.
Running the same query against the same database in pgAdmin4 returns the same error message as expected. At least there the error message provides the line number, the character number in the script as a whole and scrolls the query editor to the problematic line. It even highlights it in pink. So I find myself writing and running queries in DBeaver, but having to rerun those same queries in pgAdmin4 whenever there's an error to get any idea where or what the error might be.
Steps to reproduce, if exist:
Create a query with an error.
Try to run that query.
Try and figure out where Position: xxx is that DBeaver thinks the error lies.
For real fun;
Create 10 or 20 or more queries in the same query editor (say 1200 lines) with an error.
User the 'Run Script' functionality to run all of them.
Marvel at how after running for a couple of minutes DBeaver claims that there is an error and gives you some seemingly random position like 'Position: 336'
Beta Was this translation helpful? Give feedback.
All reactions