Why this matters
Defends against accidentally pulling the entire table over the wire. Best applied to ad-hoc query files; report-style queries that intentionally aggregate everything will fight the rule and should disable it locally.
Examples
Incorrect
SELECT * FROM users;SELECT name, email FROM users WHERE active = true;Correct
SELECT * FROM users LIMIT 100;SELECT name, email FROM users WHERE active = true LIMIT 50;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/require-limit": "warn",
},
},
]; Options
Edit the SQL — only require-limit 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
require-limit — plus no-syntax-error as a safety net.