PowerSync home pagelight logodark logo
  • Dashboard
  • Get Started
  • Get Started
Documentation
Client SDKs
Self-Hosting
Tutorials
Resources
  • GitHub
  • Community Discord
  • PowerSync Dashboard
  • PowerSync Website
  • Introduction
    • PowerSync Overview
    • PowerSync Philosophy
    Installation
    • Quickstart / Overview
    • Source Database Setup
    • Database Connection
    • Client-Side Setup
    • App Backend Setup
    • Authentication Setup
    Usage
    • Sync Rules
    • Lifecycle / Maintenance
      • Overview
      • Implementing Schema Changes
      • Deploying Schema Changes
        • Overview
        • Additive Changes
        • Renaming a Table on the Server
        • Renaming a Table on the Client
        • Renaming a Table on Both Server and Client
        • Renaming a Column on the Server
        • Renaming a Column on the Client
        • Changing a Column Type
      • Handling Update Conflicts
      • Handling Write / Validation Errors
      • Upgrading the Client SDK
      • Postgres Maintenance
      • Compacting Buckets
    • Use Case Examples
    • Tools
    Integration Guides
    • Integrations Overview
    • Supabase + PowerSync
    • FlutterFlow + PowerSync
    • Railway + PowerSync
    • Coolify + PowerSync
    Migration Guides
    • MongoDB Atlas Device Sync Migration Guide
    • WatermelonDB Migration Guide
    Architecture
    • Architecture Overview
    • PowerSync Service
    • Client Architecture
    • PowerSync Protocol
    • Consistency
    Deploying Schema Changes

    Renaming a Table on Both Server and Client

    Treat this as two separate steps and follow the process for both server and client.

    Suggest editsRaise issue
    Renaming a Table on the ClientRenaming a Column on the Server
    githubdiscordblueskyxyoutubelinkedin
    Powered by Mintlify