#26139: UUIDField value must be declared "binary" to avoid MySQL warning
-------------------------------------+-------------------------------------
     Reporter:  guilhem-bichot       |                    Owner:  nobody
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  1.9
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  invalid
     Keywords:  MySQL                |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by timgraham):

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


Comment:

 Yes, Claude is correct. Django's `UUIDField` uses `char(32)` -- the
 `binary(16)` representation is a third-party implementation. The warnings
 I'm seeing for Django's test suite are for `BinaryField` (created #26140).

--
Ticket URL: <https://code.djangoproject.com/ticket/26139#comment:3>
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/072.99a95618ad2d52aa58703462ddb085c7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to