no-drop-column · eslint-plugin-postgresql

Why this matters

Every running app instance that still reads the column starts failing the moment the migration runs. The safe pattern is to stop reading/writing the column in the application, deploy, then drop it in a follow-up migration.

Examples

Incorrect

ALTER TABLE users DROP COLUMN legacy_flag;

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-drop-column": "warn",
    },
  },
];

Options

This rule has no options.

Edit the SQL — only no-drop-column 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-drop-column — plus no-syntax-error as a safety net.