All rules

Safety

postgresql/no-update-primary-key

Disallow `UPDATE` on primary-key columns (heuristic).

  • Type problem
  • Recommended error
  • Fixable no

Why this matters

Primary keys are intended to be immutable: foreign-key references and external systems may hold the old value. By default the rule treats `id` and `<table>_id` as primary-key columns; override with `pkColumnNames` for non-conventional schemas.

Examples

Incorrect

Incorrect
UPDATE users SET id = 5 WHERE id = 1;

Correct

Correct
UPDATE users SET name = 'foo' WHERE id = 1;
Correct
UPDATE orders SET total = 100, status = 'paid' WHERE id = 2;

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-update-primary-key": [
        "error",
        {
          pkColumnNames: ["id"],
        },
      ],
    },
  },
];

Options

pkColumnNames string[] default: ["id"]
Explicit list of primary-key column names. Replaces the default. The `<table>_id` heuristic still applies in addition.
Try this rule

Edit the SQL — only no-update-primary-key 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-update-primary-key — 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