SQL

Whitespace should be limited to a single space unless while indenting or preceding a comment.

References should be consistent in statements with a single table. You can configure this in the [analyzers.meta] section of the .deepsource.toml vonfiguration file.

Trailing whitespace is any spaces or tabs after the last non-whitespace character on the line until the newline.

A single section of whitespace contains both tabs and spaces.

A single whitespace is expected after AS in WITH clause.

A single whitespace expected after USING in JOIN clause to avoid confusing it for a function.

Each file should end with a trailing newline. Ref: https://unix.stackexchange.com/questions/18743/whats-the-point-in-adding-a-new-line-to-the-end-of-a-file

Inconsistent capitalization found for unquoted identifiers. All keywords should be of same case to maintain consistency.

Line length of the SQL statement exceeds the defined limit. This includes - Maximum line length allowed.

Inconsistent capitalisation of function names.

Operators near newlines should be placed after, not before the newline.

Commas should be followed by a single whitespace unless followed by a comment.

All keywords should be of same case to maintain consistency. The defaults can be configured per your needs with the following parameters.

Implicit aliasing of table not allowed. Use explicit AS clause.

Implicit aliasing of column not allowed. Use explicit AS clause.

WITH clause closing bracket should be aligned with WITH keyword.

This issue is raised for Leading / Trailing comma enforcement. By default the analyzer prefers trailing commas, however it is configurable for leading commas in the .deepsource.toml file. Whichever option you chose it does expect you to be consistent.

A blank line is expected after CTE definition. In queries with many CTEs this hinders readability.