postgresql/consistent-between-over-and

Why this matters

`BETWEEN` is the SQL-standard inclusive-range form and is shorter to read. The rule only flags inclusive comparisons (`>=` / `<=`) where both bounds reference the same expression — strict inequalities are not equivalent to `BETWEEN` and are out of scope. Flip with the `style` option for projects that prefer explicit comparisons.

Examples

SELECT * FROM t WHERE x >= 1 AND x <= 10;

SELECT * FROM t WHERE x BETWEEN 1 AND 10;

SELECT * FROM t WHERE x > 1 AND x < 10; -- strict bounds: out of scope

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/consistent-between-over-and": [
        "warn",
        {
          style: "always",
        },
      ],
    },
  },
];

Options

style "always" | "never" default: "always"

`always` (default) rewrites `>=` + `<=` pairs to `BETWEEN`. `never` rewrites `BETWEEN` back to explicit `>=` and `<=` comparisons.