- Deploy Sync Rules containing both the old and the new table name, with a mapping (alias) from the new name to the old one (so that both end up with the old name on the client). This will cause validation errors because of a missing table, but PowerSync will still allow the deploy.
- Wait for Sync Rule reprocessing to complete.
- Put the backend in maintenance mode.
- i.e. Backend needs to be made unavailable to avoid breaking things during migrations.
- Apply the source schema changes (i.e. in Postgres database)
- Deploy backend changes and re-activate backend.
- Remove the old table from Sync Rules, then deploy and activate the Sync Rules.
Deploying Schema Changes
Renaming a Table on the Server
The approach here is to have the Sync Rules handle both the old and the new table name during the migration period.
Using maintenance mode on the backend here for simplicity. Other processes may be used to avoid maintenance mode, but that doesn’t affect PowerSync system.