#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
-------------------------------------+-------------------------------------
Changes (by felixxm):

 * cc: Simon Charette (added)
 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 Tentatively accepted, but I'm not sure if this is a supported use case,
 see #6148.

 Regression in 22ce5d0031bd795ade081394043833e82046016c.

 Crashing SQL:
 {{{
 ALTER TABLE "loader"."data_load" ADD COLUMN "valuation_id" integer NOT
 NULL CONSTRAINT "data_load_valuation_id_9af1ae91_fk_valuation_id"
 REFERENCES "core"."valuation"("id") DEFERRABLE INITIALLY DEFERRED; SET
 CONSTRAINTS "data_load_valuation_id_9af1ae91_fk_valuation_id" IMMEDIATE
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/31735#comment:1>
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.43971519b19951f1e3343aed256ddb50%40djangoproject.com.

Reply via email to