All rules

Safety

postgresql/no-add-column-not-null-without-default

Error on `ADD COLUMN ... NOT NULL` without a `DEFAULT` — fails on non-empty tables.

  • Type problem
  • Recommended error
  • Fixable no

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

Incorrect
ALTER TABLE users ADD COLUMN status text NOT NULL;

Correct

Correct
ALTER TABLE users ADD COLUMN status text NOT NULL DEFAULT 'active';
Correct
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

This rule has no options.

Try this rule

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.

0 errors 0 warnings parse 0ms · rules 0ms
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.
eslint-plugin-postgresql

An ESLint plugin that lints .sql files with real PostgreSQL grammar and a curated set of best-practice rules.

© 2026 eslint-plugin-postgresql contributors Built on libpg-query · PostgreSQL 17