Why this matters
Comparing with `NULL` using `=`, `<>`, or `!=` always returns NULL (not true), so the predicate silently filters every row. Use the three-valued-logic-aware `IS NULL` / `IS NOT NULL` instead.
Examples
Incorrect
SELECT * FROM t WHERE x = NULL;SELECT * FROM t WHERE x <> NULL;SELECT * FROM t WHERE NULL = x;Correct
SELECT * FROM t WHERE x IS NULL;SELECT * FROM t WHERE x IS NOT NULL;Configure it
// eslint.config.js
import postgresql from "eslint-plugin-postgresql";
export default [
{
files: ["**/*.sql"],
languageOptions: {
parser: postgresql.configs.recommended.languageOptions.parser,
},
plugins: { postgresql },
rules: {
"postgresql/no-equality-with-null": "error",
},
},
]; Options
Edit the SQL — only no-equality-with-null is enabled.
Pre-filled with the first incorrect example. Toggle off in the rule shelf to see how the diagnostic disappears.
Diagnostics
No issues found.
2 rules enabled.
Rule under test
no-equality-with-null — plus no-syntax-error as a safety net.