Getting Started
Configuration
Troubleshooting
Schema migrations allow you to track changes to your database structure over time and apply those changes to your live database. This is a critical process for keeping your database definition in sync with your application requirements.
There are two primary ways to manage these changes: Generating Migration Files (for version control) and Pushing Changes (for direct, immediate updates).
Generating migration files creates a historical record of your schema changes. These files contain the SQL statements required to transition your database from one state to another.
Tip
Use this method if you are working in a team or want to maintain a history of your database changes in your version control system.
If you prefer not to manage individual migration files, you can use the "push" feature to synchronize your database directly.
Warning
Pushing changes directly can be destructive. If the system detects operations that might cause data loss (like removing a table or a column), it will pause and prompt for explicit confirmation. Always review these warnings carefully.
Important
Always keep backups of your database. While the system identifies potential data-loss operations, it is impossible to predict all scenarios, especially in complex environments.
Note
If you are using platforms like Expo or React Native, look for the bundle option, which helps package your migration files into a single file for easier deployment.
Caution
Avoid performing manual changes directly on your database if you are using migrations. Changes made outside the system will conflict with the tool's records, potentially causing errors during future migrations.