#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
----------------------------------+--------------------------------------
Comment (by felixxm):
> First, is that the syntax is exactly the syntax that
psycopg2.extras.NumericRange supports, so it's not
undocumented/unsupported.
I don't see in Django docs or tests any example of using 3-tuples with
bounds.
> The only thing that works correctly right now is to actually instantiate
and pass in a psycopg2 object as the Django value.
This ticket is about adding support for 3-tuples with bounds. If you can
describe any behavior that is documented, tested and supported but doesn't
work properly, please do.
--
Ticket URL: <https://code.djangoproject.com/ticket/31872#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.45ce5494fbd3b82ac2293fe80bc7aecf%40djangoproject.com.
