#31735: Migration crash when adding inline foreign key to different schema on
PostgreSQL.
-------------------------------------+-------------------------------------
     Reporter:  Rodrigo Estevao      |                    Owner:  Simon
                                     |  Charette
         Type:  Bug                  |                   Status:  closed
    Component:  Migrations           |                  Version:  3.0
     Severity:  Release blocker      |               Resolution:  fixed
     Keywords:  many-to-             |             Triage Stage:  Ready for
  many;relationship;intermediate;table;through|  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Mariusz Felisiak <felisiak.mariusz@…>):

 In [changeset:"453a5bf3024ed385f95f2f9a5378d8fc03baffc2" 453a5bf3]:
 {{{
 #!CommitTicketReference repository=""
 revision="453a5bf3024ed385f95f2f9a5378d8fc03baffc2"
 [3.0.x] Fixed #31735 -- Fixed migrations crash on namespaced inline FK
 addition on PostgreSQL.

 The namespace of the constraint must be included when making the
 constraint immediate.

 Regression in 22ce5d0031bd795ade081394043833e82046016c.

 Thanks Rodrigo Estevao for the report.

 Backport of 2e8941b6f90e65ffad3f07083b8de59e8ed29767 from master
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/31735#comment:8>
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.a1764b0104b3acd24c8eb696fa8664f4%40djangoproject.com.

Reply via email to