#31872: Postgres DecimalRangeField ignores bounds
----------------------------------+--------------------------------------
Reporter: Jack Delany | Owner: (none)
Type: New feature | Status: closed
Component: contrib.postgres | Version: 3.1
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Changes (by felixxm):
* status: new => closed
* type: Uncategorized => New feature
* resolution: => wontfix
Comment:
> x = OneModel(val=(1.0, 2.0, "[]"))
Thanks for this ticket, however this syntax has never been documented,
tested or supported. Moreover I don't think we should support it because
it's not readable. If you want to specify bounds you can use range types
from `psycopg2.extras`.
> I'd presume the intention is that the behavior matches the underlying
psycopg2 semantics.
We added it for simplicity not to match the psycopg2 semantic.
--
Ticket URL: <https://code.djangoproject.com/ticket/31872#comment:1>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.965ffe1a12e82e9f4eb2939573b68e1f%40djangoproject.com.
