All rules
Safety
postgresql/
Disallow `HAVING` without `GROUP BY`; the predicate belongs in `WHERE`.
Why this matters
PostgreSQL accepts `HAVING` without `GROUP BY` and collapses the query to a single aggregate row over the whole table — almost never what the author meant. If the predicate is row-level, put it in `WHERE`. If it's aggregate-level, add a `GROUP BY`.
Examples
Incorrect
SELECT count(*) FROM users HAVING count(*) > 1;Correct
SELECT category, count(*) FROM items GROUP BY category HAVING count(*) > 1;SELECT count(*) FROM users WHERE active;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-having-without-group-by": "error",
},
},
]; Options
Edit the SQL — only no-having-without-group-by 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-having-without-group-by — plus no-syntax-error as a safety net.