51369b610e
When an include is not surrounded by empty lines, its content is inlined on the same line as the adjacent content. That can lead to broken tags and other display issues. This PR fixes all such includes and introduces a validation step that forbids introducing the same problem again.
29 lines
898 B
Plaintext
29 lines
898 B
Plaintext
== Why is this an issue?
|
||
|
||
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.
|
||
|
||
|
||
This rule raises an issue when ``++NOT IN++`` is used with a subquery. This rule doesn't check if the selected column is a nullable column because the rules engine has no information about the table definition. It's up to the developer to review manually if the column is nullable.
|
||
|
||
include::../noncompliant.adoc[]
|
||
|
||
include::../compliant.adoc[]
|
||
|
||
ifdef::env-github,rspecator-view[]
|
||
|
||
'''
|
||
== Implementation Specification
|
||
(visible only on this page)
|
||
|
||
include::../message.adoc[]
|
||
|
||
include::../highlighting.adoc[]
|
||
|
||
'''
|
||
== Comments And Links
|
||
(visible only on this page)
|
||
|
||
include::../comments-and-links.adoc[]
|
||
|
||
endif::env-github,rspecator-view[]
|