for Windows and Linux
This page lets you specify the SQL dialects (DBMS-specific versions of SQL) used in various scopes.
|Global SQL Dialect|| The SQL dialect for all the |
.ddl files on your computer; may be redefined in narrower scopes - at the project level, and/or for individual files and directories.
|Project SQL Dialect|| The SQL dialect for all the |
.ddl files in your current project. If <None> is specified, the global SQL dialect is inherited.
|Path / SQL Dialect|| The SQL dialects for individual files and directories - if different from the global or project dialect. |
If nothing is specified in this section, all the
.ddl in your project inherit the project dialect, and all the files that are outside the project - the global dialect.
To specify a dialect for a file or directory, click and select the file or directory in the dialog that opens. Then click or the SQL Dialect cell, and select the dialect.
The dialects specified explicitly are shown in black. The inherited dialects (unless you close the dialog) are shown in gray italic.
When specifying a dialect, in addition to particular dialects, you can select:
- <None> or <Clear>. As a result, a dialect from a higher level is inherited.
- <Generic SQL>. This means that no particular dialect is specified. As a result, basic SQL92-based coding assistance is provided including completion and highlighting for SQL keywords, and table and column names. Syntax error highlighting is not available. So the file contents are always shown as syntactically correct. Also, automatic code reformatting isn't possible.
Say, most of the SQL script files on your computer are for PostgreSQL. In the current project, you are developing the scripts for Oracle but in one of the directories in your project there are the scripts for MySQL. In such a situation, you'd specify:
- Global SQL dialect: PostgreSQL
- Project SQL dialect: Oracle
Last modified: 26 October 2017
Language and Framework-Specific Guidelines: