All rules

Safety

postgresql/no-equality-with-null

Disallow `x = NULL` / `x <> NULL`; use `IS NULL` / `IS NOT NULL`.

  • Type problem
  • Recommended error
  • Fixable no

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

Incorrect
SELECT * FROM t WHERE x = NULL;
Incorrect
SELECT * FROM t WHERE x <> NULL;
Incorrect
SELECT * FROM t WHERE NULL = x;

Correct

Correct
SELECT * FROM t WHERE x IS NULL;
Correct
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

This rule has no options.

Try this rule

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.

0 errors 0 warnings parse 0ms · rules 0ms
Diagnostics

No issues found.

2 rules enabled.

Rule under test no-equality-with-null — plus no-syntax-error as a safety net.
eslint-plugin-postgresql

An ESLint plugin that lints .sql files with real PostgreSQL grammar and a curated set of best-practice rules.

© 2026 eslint-plugin-postgresql contributors Built on libpg-query · PostgreSQL 17