postgresql/no-on-delete-cascade

Why this matters

`ON DELETE CASCADE` makes a single `DELETE` quietly recurse through dependent tables. Prefer `RESTRICT` / `NO ACTION` / `SET NULL` and explicit deletion code paths so deletions are visible at the call site.

Examples

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

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

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 NO ACTION;

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-on-delete-cascade": "warn",
    },
  },
];

Options

This rule has no options.