Do not rename columns

postgresqlprismasupabasemysqldrizzlemigrations
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

Install this rule for wispbit

Add this rule to wispbit and it will run when you open a pull request

Install 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 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;
```

File Path Patterns:

*.sql

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 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;
```

File Path Patterns:

*.sql

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 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;
```

File Path Patterns:

*.sql

Use with Cline

Copy the rule below and ask Cline to review your code using this rule

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;
```

Use with OpenAI Codex

Copy the rule below and ask OpenAI Codex to review your code using this rule

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;
```

Use with Cursor

Copy the rule below and ask Cursor to review your code using this rule

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;
```

Use with Claude Code

Copy the rule below and ask Claude Code to review your code using this rule

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 Windsurf

To set up rules for Windsurf Reviews, please see this documentation 

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;
```