Replies: 1 comment
-
It would make sense only if you can execute a script as a whole but not an individual statements. Which is not true, and so the analysis works with respect to individual statements. Also consider huge scripts like dumps of databases, which can be of gygabytes. You really wouln't want DBeaver to overwhelm your CPU while analysing such an amount of SQL statements, most of which woulndn't even be ever observed even if some edited. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When creating an SQL script that includes both DDL and DML, the DML statements (i.e. INSERTS) show errors for 'unknown table' when the previous DDL statement (i.e. CREATE TABLE) actually creates the table in question. The syntax checker should be adjusted to use the existing script, in its entirety from top to bottom, when considering whether or not a table exists.
Beta Was this translation helpful? Give feedback.
All reactions