#25492: Check deferred foreign key constraints before dropping them
-------------------------------------+-------------------------------------
Reporter: Joey Wilhelm | Owner: nobody
Type: New feature | Status: closed
Component: Core (System | Version: master
checks) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette <charette.s@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"cd7efa20338cb6f3ede4780e00590c0a6dd48ca2" cd7efa20]:
{{{
#!CommitTicketReference repository=""
revision="cd7efa20338cb6f3ede4780e00590c0a6dd48ca2"
Fixed #25492 -- Checked deferred foreign key constraints before dropping
them.
This allows running foreign key data and schema altering operations in the
same migration on PostgreSQL.
Thanks Tim for review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25492#comment:14>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.3a1171c7c8f6a4924de93745ced0ae07%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.