Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integration with Django's migration system. #66

Merged
merged 2 commits into from
Aug 5, 2022
Merged

Conversation

wesleykendall
Copy link
Collaborator

Triggers are fully integrated with Django's migration system, and they are no longer
installed at the end of migrations by default. Users instead need to run
python manage.py makemigrations to make trigger migrations for their applications.

Triggers for models in third-party apps must be migrated with the
python manage.py pgtrigger makemigrations command.

For instructions on upgrading or preserving legacy behavior, see the frequently
asked questions of the docs.

Type: api-break

Addresses #25

@wesleykendall wesleykendall force-pushed the migrations branch 5 times, most recently from 462ee67 to b433423 Compare August 5, 2022 05:32
Triggers are fully integrated with Django's migration system, and they are no longer
installed at the end of migrations by default. Users instead need to run
``python manage.py makemigrations`` to make trigger migrations for their applications.

Triggers for models in third-party apps must be migrated with the
``python manage.py pgtrigger makemigrations`` command.

For instructions on upgrading or preserving legacy behavior, see the frequently
asked questions of the docs.

Type: api-break
Users no longer have to wrap ``settings.DATABASES`` with
``django-pgconnection`` in order to use the ``pgtrigger.ignore``
function.

Type: feature
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant