Do not rename columns
When renaming columns in PostgreSQL, follow a safe migration pattern to avoid breaking changes to applications:1. Create a new column2. Update application code to write to both the old and new columns3. Backfill data from the old column to the new column4. Update application code to read from the new column instead of the old one5. Once all deployments are complete, stop writing to the old column6. Drop the old column in a later migrationInstall this rule for wispbit
Quick Install
Run this one command to automatically install the rule:
Manual install
Copy the rule
---include: *.sql---When renaming columns in PostgreSQL, follow a safe migration pattern to avoid breaking changes to applications:1. Create a new column2. Update application code to write to both the old and new columns3. Backfill data from the old column to the new column4. Update application code to read from the new column instead of the old one5. Once all deployments are complete, stop writing to the old column6. Drop the old column in a later migrationBad:```sqlALTER TABLE users RENAME COLUMN some_column TO new_name;```Add the rule into your project
.wispbit/rules/no-column-renaming.mdInstall this rule for Coderabbit
Copy the configuration below and add it to your repository as .coderabbit.yml in your project root.
reviews: path_instructions: - path: "*.sql" instructions: | When renaming columns in PostgreSQL, follow a safe migration pattern to avoid breaking changes to applications: 1. Create a new column 2. Update application code to write to both the old and new columns 3. Backfill data from the old column to the new column 4. Update application code to read from the new column instead of the old one 5. Once all deployments are complete, stop writing to the old column 6. Drop the old column in a later migration Bad: ```sql ALTER TABLE users RENAME COLUMN some_column TO new_name; ``` Install this rule for Greptile
Greptile rules can be added through the web interface. Please see this documentation for details on how to add custom rules and context.
When renaming columns in PostgreSQL, follow a safe migration pattern to avoid breaking changes to applications:1. Create a new column2. Update application code to write to both the old and new columns3. Backfill data from the old column to the new column4. Update application code to read from the new column instead of the old one5. Once all deployments are complete, stop writing to the old column6. Drop the old column in a later migrationBad:```sqlALTER TABLE users RENAME COLUMN some_column TO new_name;```File Path Patterns:
Install this rule for GitHub Copilot
Copilot instructions can be added through the interface. See the documentation for details on how to create coding guidelines.
When renaming columns in PostgreSQL, follow a safe migration pattern to avoid breaking changes to applications:1. Create a new column2. Update application code to write to both the old and new columns3. Backfill data from the old column to the new column4. Update application code to read from the new column instead of the old one5. Once all deployments are complete, stop writing to the old column6. Drop the old column in a later migrationBad:```sqlALTER TABLE users RENAME COLUMN some_column TO new_name;```File Path Patterns:
Install this rule for Graphite Diamond
Diamond custom rules can be added through the interface. See the documentation for details on how to create custom rules.
When renaming columns in PostgreSQL, follow a safe migration pattern to avoid breaking changes to applications:1. Create a new column2. Update application code to write to both the old and new columns3. Backfill data from the old column to the new column4. Update application code to read from the new column instead of the old one5. Once all deployments are complete, stop writing to the old column6. Drop the old column in a later migrationBad:```sqlALTER TABLE users RENAME COLUMN some_column TO new_name;```File Path Patterns: