prefer-not-equals-operator · eslint-plugin-postgresql

Why this matters

PostgreSQL accepts both spellings. Default target is the SQL-standard `<>`; switch with the `operator` option.

Examples

Incorrect

SELECT id FROM users WHERE status != 'inactive';

Correct

SELECT id FROM users WHERE status <> 'inactive';

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/prefer-not-equals-operator": [
        "warn",
        {
          operator: "<>",
        },
      ],
    },
  },
];

Options

operator "<>" | "!=" default: "<>": Which not-equal spelling to enforce.

Edit the SQL — only prefer-not-equals-operator 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 prefer-not-equals-operator — plus no-syntax-error as a safety net.