postgresql/no-rule

Why this matters

`CREATE RULE` rewrites the query tree at planning time, which interacts poorly with prepared statements, COPY, and partitioning. The PostgreSQL community considers the rule system effectively deprecated; use a trigger or an updatable view instead.

Examples

CREATE RULE noop AS ON UPDATE TO t DO INSTEAD NOTHING;

CREATE TRIGGER t_trg BEFORE UPDATE ON t FOR EACH ROW EXECUTE FUNCTION t_trg_fn();

CREATE VIEW v AS SELECT * FROM t;

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-rule": "warn",
    },
  },
];

Options

This rule has no options.