#24012: models.UUIDfield fails on Oracle backend
-------------------------------------+-------------------------------------
Reporter: JorisBenschop | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: oracle, | Unreviewed
models.UUIDfield | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by JorisBenschop):
If you look here:
[https://github.com/django/django/blob/108b8bf852c76855ed98f5abe55db1da845598e7/django/db/models/fields/__init__.py#L2261
here] you see that `models.UUIDfield` forces data to fit into uuid.UUID
even when the DB allows other formats also. This check, and the
requirement to store the content of the UUIDfield in a uuid.UUID object is
the main issue.
the `value` is a 4096bit binary . I cannot print it (thats the whole point
of this ticket). I can convert to hex but then the foreign keys (of
course) no longer work.
--
Ticket URL: <https://code.djangoproject.com/ticket/24012#comment:4>
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/071.18a06fd7c4a2180cf992b19b8ef473ae%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
