Why this matters
Same fragility as positional `ORDER BY`: reordering the SELECT list silently shifts the grouping to a different column, producing plausible-looking but wrong aggregates. Reference the column by name or by the grouping expression.
Examples
Incorrect
SELECT category, count(*) FROM items GROUP BY 1;SELECT region, category, sum(amount) FROM sales GROUP BY 1, 2;Correct
SELECT category, count(*) FROM items GROUP BY category;SELECT region, category, sum(amount) FROM sales GROUP BY region, category;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-group-by-ordinal": "warn",
},
},
]; Options
Edit the SQL — only no-group-by-ordinal 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-group-by-ordinal — plus no-syntax-error as a safety net.