#26777: Cannot add foreign key constraint when migrating manytomany field
----------------------------+--------------------------------------
     Reporter:  Uninen      |                    Owner:  nobody
         Type:  Bug         |                   Status:  new
    Component:  Migrations  |                  Version:  1.9
     Severity:  Normal      |               Resolution:
     Keywords:              |             Triage Stage:  Unreviewed
    Has patch:  0           |      Needs documentation:  0
  Needs tests:  0           |  Patch needs improvement:  0
Easy pickings:  0           |                    UI/UX:  0
----------------------------+--------------------------------------
Changes (by Uninen):

 * status:  closed => new
 * resolution:  needsinfo =>


Comment:

 1. Yes, both tables are using InnoDB engine.
 2. No, I'm not using a custom user model

--
Ticket URL: <https://code.djangoproject.com/ticket/26777#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 [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/064.c15e28b4023a512043a78b8c6eea76de%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to