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
UPDATE users SET id = 5 WHERE id = 1;Correct
UPDATE users SET name = 'foo' WHERE id = 1;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
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.
Diagnostics
No issues found.
2 rules enabled.
Rule under test
no-update-primary-key — plus no-syntax-error as a safety net.