#26345: RangeFields always return canonical form of ranges
----------------------------------+--------------------------------------
Reporter: dbinetti | Owner:
Type: Bug | Status: new
Component: contrib.postgres | Version: 1.9
Severity: Normal | Resolution:
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 timgraham):
* needs_better_patch: => 0
* needs_docs: => 0
* needs_tests: => 0
Comment:
From [http://www.postgresql.org/docs/9.2/static/rangetypes.html the
PostgreSQL documentation]:
The built-in range types `int4range`, `int8range`, and `daterange` all
use a canonical form that includes the lower bound and excludes the upper
bound; that is, `[)`. User-defined range types can use other conventions,
however.
Do we need to duplicate this information in Django's docs? Actually
[https://docs.djangoproject.com/en/stable/ref/contrib/postgres/fields
/#range-fields they do say], "The default is lower bound included, upper
bound excluded." Maybe the implications of that statement are unclear?
--
Ticket URL: <https://code.djangoproject.com/ticket/26345#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.889a0ba81219deae408df24ad88ff582%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
