#27147: Add support for defining bounds in postgres range fields
-------------------------------------+-------------------------------------
Reporter: Kirill Stepanov | Owner: (none)
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 Matthew Schinckel):
Okay, that would not quite meet the requirements of this ticket (which
suggest any range type should be selectable). That makes it a bit more
complicated, but I think maybe defining a target bounds in the field
definition is still the best approach.
We'd want to be applying a fixed bounds to the incoming data (unless the
widget had some way to represent the bounds types, but that's probably
less useful for real humans to interact with), and the data fetched from
the db should be denormalised (?) to match those bounds.
--
Ticket URL: <https://code.djangoproject.com/ticket/27147#comment:7>
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.d43e9a792d9122d582a9b1c6fdd0eb41%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
