#27147: Add support for defining bounds in postgres range fields
-------------------------------------+-------------------------------------
Reporter: impala2 | Owner:
Type: New feature | Status: new
Component: contrib.postgres | Version: master
Severity: Normal | Resolution:
Keywords: postgres range | Triage Stage: Accepted
bounds |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by impala2):
Replying to [comment:3 timgraham]:
> Is this about form fields and/or model fields? How does it interact with
the fact that for some types, "PostgreSQL always returns a range in a
canonical form that includes the lower bound and excludes the upper bound;
that is `[)`." as the documentation ticket says. Accepting because the
idea seems sensible, however, I would like to see a patch to make a final
evaluation of the idea.
Ah, I saw that but misunderstood as "no matter how it was originally
inserted, django will always interpret incoming data as `[)` because it
doesn't know any better. I now see that postgres canonicalizes discrete
ranges but I'll see what I can do about it. The proposal still at least
makes sense for non-discrete ranges.
--
Ticket URL: <https://code.djangoproject.com/ticket/27147#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/065.4221f76f8934a28ed0ef17396495eff2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
