All rules
Safety
postgresql/
Error on `ADD COLUMN ... NOT NULL` without a `DEFAULT` — fails on non-empty tables.
Why this matters
On any table that already has rows, `ALTER TABLE ADD COLUMN ... NOT NULL` aborts because existing rows have no value for the new column. Supply a `DEFAULT`, or add the column nullable, backfill, then `SET NOT NULL`.
Examples
Incorrect
ALTER TABLE users ADD COLUMN status text NOT NULL;Correct
ALTER TABLE users ADD COLUMN status text NOT NULL DEFAULT 'active';ALTER TABLE users ADD COLUMN status text;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-add-column-not-null-without-default": "error",
},
},
]; Options
Edit the SQL — only no-add-column-not-null-without-default 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-add-column-not-null-without-default — plus no-syntax-error as a safety net.