#27147: Add support for defining bounds in postgres range fields
-------------------------------------+-------------------------------------
Reporter: Kirill Stepanov | Owner: Guilherme
| Martins Crocetti
Type: New feature | Status: closed
Component: contrib.postgres | Version: dev
Severity: Normal | Resolution: fixed
Keywords: postgres range | Triage Stage: Ready for
bounds | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jared Ahern):
Hi Guilherme (and others)!
I'm trying to follow this issue, and I'm slightly confused. The changes
for continuous fields look great and are much appreciated! But I thought
the original intent of the ticket was to enable a "default_bounds"
argument for all range fields. Since Jacob and Jon's PR didn't get merged,
I don't believe there presently any logic for handling the "+/- step" for
discrete range fields.
My specific use case is to have things like DateRangeField and
IntegerRangeField be editable in the admin by users that expect a "[]"
format. Am I correct in thinking that if I wanted to have a "[]" bounded
DateRangeField, I would still need to modify the field and/or form field
appropriately? If so, would a further patch be accepted that would
facilitate this at the model or form field level?
Apologies if I'm missing something, or if I should be raising this outside
of this ticket!
--
Ticket URL: <https://code.djangoproject.com/ticket/27147#comment:23>
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/01070181970a22ae-39c75e63-c1ad-492b-ba9d-9e1c6ceb3dda-000000%40eu-central-1.amazonses.com.