#31735: Migration crash when adding inline foreign key to different schema on
PostgreSQL.
-------------------------------------+-------------------------------------
Reporter: Rodrigo Estevao | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 3.0
Severity: Release blocker | Resolution:
Keywords: many-to- | Triage Stage: Accepted
many;relationship;intermediate;table;through|
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
This should be solveable by making sure the schema name is included in the
`SET CONSTRAINT` as well.
That would result in `SET CONSTRAINTS
"loader"."data_load_valuation_id_9af1ae91_fk_valuation_id" IMMEDIATE`.
--
Ticket URL: <https://code.djangoproject.com/ticket/31735#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/072.3d20cdaedcc08f1f92e439a20e44b73c%40djangoproject.com.
