#24912: prefetch_related fails with sqlite3 database and UUIDField primary keys
-------------------------------------+-------------------------------------
     Reporter:  brki                 |                    Owner:  brki
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  master
  (models, ORM)                      |
     Severity:  Release blocker      |               Resolution:  fixed
     Keywords:  UUIDField            |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Tim Graham <timograham@…>):

 In [changeset:"c58755d8757d6d6ad1ab2c52a631aff1b9bae2da" c58755d8]:
 {{{
 #!CommitTicketReference repository=""
 revision="c58755d8757d6d6ad1ab2c52a631aff1b9bae2da"
 [1.8.x] Fixed #24912 -- Fixed prefetch_related failure for UUIDField
 primary keys

 This resolves a problem on databases besides PostgreSQL when using
 prefetch_related with a source model that uses a UUID primary key.

 Backport of bfb5b7150ff52571a7a3cf10e0dd0d1dbd45c4b5 from master
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/24912#comment:16>
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/062.51cfab68fefbad9534082e6554886bdd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to