postgresql/require-on-delete-action

Why this matters

Without `ON DELETE`, the default is `NO ACTION` — but it is rarely the deliberate choice. Forcing the author to write the action makes intent visible at the call site. Covers both inline `REFERENCES` and `ALTER TABLE ADD CONSTRAINT FOREIGN KEY`. With the `allowed` option, the rule additionally fails when the action is not in an opt-in list.

Examples

CREATE TABLE t (
  fid integer REFERENCES other(id)
);

ALTER TABLE t ADD CONSTRAINT fk FOREIGN KEY (fid) REFERENCES other(id);

CREATE TABLE t (
  fid integer REFERENCES other(id) ON DELETE RESTRICT
);

ALTER TABLE t ADD CONSTRAINT fk FOREIGN KEY (fid) REFERENCES other(id) ON DELETE SET 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/require-on-delete-action": [
        "warn",
        {
          allowed: [],
        },
      ],
    },
  },
];

Options

allowed ("CASCADE" | "RESTRICT" | "NO ACTION" | "SET NULL" | "SET DEFAULT")[]

When set, the rule additionally flags any `ON DELETE` whose action is not in this list. Use it to bake project-wide policy into the rule (e.g. `["RESTRICT", "NO ACTION"]` to forbid cascading deletes).