Why this matters
PostgreSQL's null-ordering defaults (NULLS LAST for ASC, NULLS FIRST for DESC) match the SQL spec but contradict every other major engine. Adding explicit `NULLS FIRST/LAST` removes the surprise and survives copy-paste into other databases.
Examples
Incorrect
SELECT id FROM users ORDER BY created_at DESC;Correct
SELECT id FROM users ORDER BY created_at DESC NULLS LAST;SELECT id FROM users ORDER BY created_at;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/prefer-explicit-null-ordering": "warn",
},
},
]; Options
Edit the SQL — only prefer-explicit-null-ordering 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
prefer-explicit-null-ordering — plus no-syntax-error as a safety net.