Do not rename tables
When renaming tables, use a multi-step approach instead of direct renaming to prevent downtime.1. Create a new table2. Write to both tables3. Backfill data from the old table to the new table4. Move reads from the old table to the new table5. Stop writing to the old table6. Drop the old tableInstall 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 tables, use a multi-step approach instead of direct renaming to prevent downtime. 1. Create a new table 2. Write to both tables 3. Backfill data from the old table to the new table 4. Move reads from the old table to the new table 5. Stop writing to the old table 6. Drop the old table Bad: ```sql ALTER TABLE users RENAME TO customers; ``` 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 tables, use a multi-step approach instead of direct renaming to prevent downtime.1. Create a new table2. Write to both tables3. Backfill data from the old table to the new table4. Move reads from the old table to the new table5. Stop writing to the old table6. Drop the old tableBad:```sqlALTER TABLE users RENAME TO customers;```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 tables, use a multi-step approach instead of direct renaming to prevent downtime.1. Create a new table2. Write to both tables3. Backfill data from the old table to the new table4. Move reads from the old table to the new table5. Stop writing to the old table6. Drop the old tableBad:```sqlALTER TABLE users RENAME TO customers;```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 tables, use a multi-step approach instead of direct renaming to prevent downtime.1. Create a new table2. Write to both tables3. Backfill data from the old table to the new table4. Move reads from the old table to the new table5. Stop writing to the old table6. Drop the old tableBad:```sqlALTER TABLE users RENAME TO customers;```File Path Patterns:
Use with Cline
Copy the rule below and ask Cline to review your code using this rule
When renaming tables, use a multi-step approach instead of direct renaming to prevent downtime.1. Create a new table2. Write to both tables3. Backfill data from the old table to the new table4. Move reads from the old table to the new table5. Stop writing to the old table6. Drop the old tableBad:```sqlALTER TABLE users RENAME TO customers;```Use with OpenAI Codex
Copy the rule below and ask OpenAI Codex to review your code using this rule
When renaming tables, use a multi-step approach instead of direct renaming to prevent downtime.1. Create a new table2. Write to both tables3. Backfill data from the old table to the new table4. Move reads from the old table to the new table5. Stop writing to the old table6. Drop the old tableBad:```sqlALTER TABLE users RENAME TO customers;```Use with Cursor
Copy the rule below and ask Cursor to review your code using this rule
When renaming tables, use a multi-step approach instead of direct renaming to prevent downtime.1. Create a new table2. Write to both tables3. Backfill data from the old table to the new table4. Move reads from the old table to the new table5. Stop writing to the old table6. Drop the old tableBad:```sqlALTER TABLE users RENAME TO customers;```Use with Claude Code
Copy the rule below and ask Claude Code to review your code using this rule
When renaming tables, use a multi-step approach instead of direct renaming to prevent downtime.1. Create a new table2. Write to both tables3. Backfill data from the old table to the new table4. Move reads from the old table to the new table5. Stop writing to the old table6. Drop the old tableBad:```sqlALTER TABLE users RENAME TO customers;```Install this rule for Windsurf
To set up rules for Windsurf Reviews, please see this documentation
When renaming tables, use a multi-step approach instead of direct renaming to prevent downtime.1. Create a new table2. Write to both tables3. Backfill data from the old table to the new table4. Move reads from the old table to the new table5. Stop writing to the old table6. Drop the old tableBad:```sqlALTER TABLE users RENAME TO customers;```