Safe Table Renaming in DataGrip: How the Refactoring Engine Protects Your Schema

The problem with manual schema changes

Renaming a table in a production database usually means hunting down every view, trigger, or stored procedure that references it, crafting the right ALTER statements, and hoping nothing breaks. In multi-connection projects, the risk multiplies.

How DataGrip's refactoring engine works

DataGrip's refactoring engine parses DDL and updates all dependent objects - views, stored procedures, triggers - in a single operation. Before any changes are applied, a preview dialog lists every affected statement, letting you review the scope of the rename.

Worked example: renaming a table across dependent objects

Suppose you have a table named orders with two dependent views order_summary and sales_total, and a stored procedure that references orders.order_date. Right-click the table, choose Refactor → Rename, and enter the new name order_headers. DataGrip's preview will list:

-- Table DDL: ALTER TABLE orders RENAME TO order_headers
-- View: CREATE OR REPLACE VIEW order_summary AS SELECT * FROM order_headers
-- Procedure: ALTER PROCEDURE get_order_date() ...

After you confirm the list, applying the refactor updates every object in a transaction per connection. A simple SELECT * FROM order_headers then returns data without manual edits.

Trade-offs and limitations

• Refactoring is destructive - always back up the database before applying changes.
• The preview list may omit objects that are dynamically generated or stored in external scripts; manual review is advised.
• Large schema changes can lock tables or trigger extensive recompilation on the server, potentially impacting availability.
• DataGrip's refactoring may not be fully supported for all database vendors; test in a staging environment first.
• When identifiers are case-sensitive, DataGrip's rename may alter the case unexpectedly, leading to runtime errors.

How to verify the result

1. Open DataGrip 2025.2 or later and connect to a test database (PostgreSQL or MySQL).
2. Select a table, open the context menu, choose Refactor → Rename.
3. In the preview dialog, confirm the list of affected statements matches your intent.
4. Apply the refactoring and run a simple SELECT * FROM renamed_table to verify the table is accessible.
5. Check the version-control integration to confirm the change was recorded as a single patch.