2023-05-03 11:06:20 +02:00
== Why is this an issue?
2020-06-30 12:48:39 +02:00
A WHERE clause condition that uses NOT IN with a subquery will have unexpected results if that subquery returns NULL. On the other hand NOT EXISTS subqueries work reliably under the same conditions.
2021-02-02 15:02:10 +01:00
2021-02-08 19:11:39 +01:00
This rule raises an issue when NOT IN is used with a subquery where the selected column is nullable.
2020-06-30 12:48:39 +02:00
2021-02-02 15:02:10 +01:00
2022-04-13 11:17:01 +02:00
*Noteworthy*
2021-02-02 15:02:10 +01:00
2022-04-13 11:17:01 +02:00
This rule raises issues only when a *Data Dictionary* is provided during the analysis. See https://docs.sonarqube.org/latest/analysis/languages/plsql/
2020-06-30 12:48:39 +02:00
include::../noncompliant.adoc[]
include::../compliant.adoc[]
2021-06-02 20:44:38 +02:00
2021-06-03 09:05:38 +02:00
ifdef::env-github,rspecator-view[]
2021-09-20 15:38:42 +02:00
'''
== Implementation Specification
(visible only on this page)
include::../message.adoc[]
include::../highlighting.adoc[]
2021-06-08 15:52:13 +02:00
'''
2021-06-02 20:44:38 +02:00
== Comments And Links
(visible only on this page)
include::../comments-and-links.adoc[]
2021-06-03 09:05:38 +02:00
endif::env-github,rspecator-view[]