#36092: Composite primary key wrongly allows non-local fields to be referenced
-------------------------------------+-------------------------------------
     Reporter:  Jacob Walls          |                    Owner:  Csirmaz
                                     |  Bendegúz
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  dev
  (models, ORM)                      |
     Severity:  Release blocker      |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Ready for
                                     |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce <42296566+sarahboyce@…>):

 * resolution:   => fixed
 * status:  assigned => closed

Comment:

 In [changeset:"d83fb782d33aa7aaa1b2c995c648a59eddb46047" d83fb78]:
 {{{#!CommitTicketReference repository=""
 revision="d83fb782d33aa7aaa1b2c995c648a59eddb46047"
 Fixed #36092 -- Disallowed non-local fields in composite primary keys.
 }}}
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36092#comment:6>
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 visit 
https://groups.google.com/d/msgid/django-updates/010701945fd3d6df-e84c901a-f3c2-4777-b2bb-2d0e5d131f97-000000%40eu-central-1.amazonses.com.

Reply via email to