#29345: Migrations that recreate constraints can fail on PostgreSQL if table is 
not
in public schema
-----------------------------+------------------------------------
     Reporter:  Olav Morken  |                    Owner:  nobody
         Type:  Bug          |                   Status:  new
    Component:  Migrations   |                  Version:  2.0
     Severity:  Normal       |               Resolution:
     Keywords:               |             Triage Stage:  Accepted
    Has patch:  0            |      Needs documentation:  0
  Needs tests:  0            |  Patch needs improvement:  0
Easy pickings:  0            |                    UI/UX:  0
-----------------------------+------------------------------------

Comment (by Emre Kartoglu):

 I was trying to reproduce this issue. Although I failed to reproduce it
 using the files attached by Olav, I did notice another potential issue in
 the process: Django migration created 2 foreign key constraints both
 pointing from the same table&column to the same table&column. The attached
 file `2_fk_constraints.png​` shows what I mean. Should we create a ticket
 for this? I wonder if solving 29345 would solve this too, or vice versa.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/29345#comment:2>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.311f37d6da2bdbc8a5b49470599931b7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to