#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):
Sorry for editing my reply (4) during your reply (5).
I think the difference are not that extreme with the exception of the size
of the binary field.
I'm looking into writing a custom field. However, my preference would be
to write it in a way that it can be used to include in the Django master,
so that Django is again fully compatible with Oracle.
I am now using this documentation:
[https://docs.djangoproject.com/en/dev/howto/custom-model-fields/]. If you
have any other documentation, code directives or other modules that I will
need to make changes to, please advice me.
thanks for your patience.
--
Ticket URL: <https://code.djangoproject.com/ticket/24012#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 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.5306d0644c423ea22c5868124e20fc49%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
