G-3130
🆓Warning
Try to use ANSI SQL-92 join syntax.
Reason
ANSI SQL-92 join syntax supports the full outer join. A further advantage of the ANSI SQL-92 join syntax is the separation of the join condition from the query filters.
Example
Non-Compliant Example
select e.employee_id
,e.last_name
,e.first_name
,d.department_name
from employees e
,departments d
where e.department_id = d.department_id
and extract(month from e.hire_date) = extract(month from sysdate);Issues
| Line | Column | Message |
|---|---|---|
| 5 | 3 | Use ANSI SQL-92 instead of Oracle join syntax. |
Compliant Solution - ★★★★★
select emp.employee_id
,emp.last_name
,emp.first_name
,dept.department_name
from employees emp
join departments dept
on dept.department_id = emp.department_id
where extract(month from emp.hire_date) = extract(month from sysdate);Parameters
Use parameters to customize the rule to your needs.
| Parameter | Description | Default Value |
|---|---|---|
| DisableAllQuickFix | Comma-separated ist of rules for which a quick fix should not be applied to all the problems in a file. | Core G-3130 |
| DisableIncompleteQuickFix | Comma-separated list of rules for which an incomplete quick fix should be suppressed. | Core G-3130 |
References
- same as plsql:UseAnsiJoinsCheck
- similar to SQLFluff ambiguous.join_condition
The scope of ambiguous.join_condition is CROSS joins with Oracle join syntax.
- same as Trivadis G-3130