#24319: UUIDField do not properly clean (validate) value in get_db_prep_value
-------------------------------------+-------------------------------------
Reporter: davidfischer-ch | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.8alpha1
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: clean,uuid | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by charettes):
I agree with Josh that we should provide early validation when we can
easily do it.
The simplicity of the patch convince me we should go forward with fixing
this.
On a side note I think that if the
[https://docs.python.org/3.3/library/ipaddress.html ipaddress] module had
been part of the all the supported Python version stdlib when the
`GenericIpAddressField` was added it would have raised a `ValueError`
instead of a database one.
Since the `uuid` module is part of the stdlib I think it would be more
fair to compare the `UUIDField`'s behavior to the temporal ones backed by
the `datetime` module.
--
Ticket URL: <https://code.djangoproject.com/ticket/24319#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/073.83c782efb81c784fcb9173e154c1fe42%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
