| Table of Contents |
|---|
...
When using AWS Aurora, a nullable column can be added to existing large (100k rows+?) tables without causing downtime. However, the migration may still timeout in GoCD - so please coordinate the release with DevOps.
- Make a new field addition in model with null=True.
- Generate the model-change migrations locally.
- Create a pull request containing the model change and newly-generated migrations.
- Merge the migration pull request.
- The release process will run the migration and add the nullable column to table.
...
On AWS Aurora, indexes can be build on large tables without causing downtime, but this requires devops coordination as the migration may timeout in GoCD.
- Add the new index on model fields.
- Generate the model-change migrations locally.
- Make pull request containing the model change and newly-generated migrations.
- Merge the migration pull request.
- Release will run the migration and add the index to table.
...
Make sure you are pointing to the correct environment file.
Checking SQL for a migration
After creating your migration file, if you are running Open edX via the DevStack configuration, it is sometimes useful to review the SQL for your new migration:
| Code Block |
|---|
./manage.py [lms|cms] --settings=devstack_docker sqlmigrate name_of_app number |
Performing a migration
After creating your migration file, if you are running Open edX via the DevStack configuration, you can perform the migration using the following command:
...