plsql-and-sql-coding-guidelines
plsql-and-sql-coding-guidelines copied to clipboard
Trivadis
Trivadis PL/SQL & SQL Coding Guidelines
As mentioned in #184, the guideline might be too strict. However, introducing a `threshold` parameter similar to the case mentioned in #180 does not make sense IMO. Data types can...
There are 16 violations of G-2130 in [SonarCloud](https://sonarcloud.io/project/issues?resolved=false&rules=external_db*+CODECOP%3AG-2130&id=Trivadis-plsql-and-sql-coding-guidelines). This shows two things: a) We do not follow our own rules b) The rule might be too strict. This ticket deals...
There are 46 violations of G-7460 in [SonarCloud](https://sonarcloud.io/project/issues?resolved=false&rules=external_db*+CODECOP%3AG-7460&id=Trivadis-plsql-and-sql-coding-guidelines). Some of them are valid and some are false positives. The problem with this guideline is that there is no `non-deterministic` clause....
As mentioned in #181 the guideline is too strict IMO. There are some cases where a violation can be considered a false positive. For example for the following data types...
There are 75 violations of G-8310 in [SonarCloud](https://sonarcloud.io/project/issues?resolved=false&rules=external_db*+CODECOP%3AG-8310&id=Trivadis-plsql-and-sql-coding-guidelines). This shows two things: a) We do not follow our own rules b) The rule might be too strict. This ticket deals...
As mentioned in #179, the guideline is too strict IMO. SonarSource defines a similar rule [plsql:S1192 - String literals should not be duplicated](https://sonarcloud.io/organizations/tvd/rules?open=plsql%3AS1192&rule_key=plsql%3AS1192). For this rule a `threshold` can be...
There are 77 violations of G-1050 in [SonarCloud](https://sonarcloud.io/project/issues?resolved=false&rules=external_db*+CODECOP%3AG-1050&id=Trivadis-plsql-and-sql-coding-guidelines). This shows two things: a) We do not follow our own rules b) The rule might be too strict. This ticket deals...
This rule was suggested by @dmcghan via [X (Twitter)](https://twitter.com/dmcghan/status/1743008854873718841). Here's an example of a bad SQL: ```sql create or replace function emp_name(in_empno in integer) return varchar2 is l_ename emp.ename%type; begin...
In v4.3. the code snippets in the bad and good examples became more extensive and it is not easy to spot the line that violates the guideline. [Material for Mkdocs...
G-1050 should not apply to check constraints. Check constraints only accept literals, sql-functions (not PL/SQL) and references to columns in same row. see [section "Restrictions on Check Constraints"](https://docs.oracle.com/en/database/oracle/oracle-database/19/sqlrf/constraint.html#GUID-1055EA97-BA6F-4764-A15F-1024FD5B6DFE) ```sql create...
