#27147: Add support for defining bounds in postgres range fields
-------------------------------------+-------------------------------------
Reporter: Kirill Stepanov | Owner: (none)
Type: New feature | Status: new
Component: contrib.postgres | Version: dev
Severity: Normal | Resolution:
Keywords: postgres range | Triage Stage: Accepted
bounds |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Guilherme Martins Crocetti):
Hi, I'm a long time Django's user but first time commenting here.
I'm currently facing a problem related to this ticket: I have a
`DateTimeRangeField` field and there's no easy way, other than writing a
custom `ModelForm` and subclassing `forms.DateTimeRangeField`, to
customize a bound other than the default "[)". These values are
represented by `tstzrange`, one of the types that does not "suffer" of the
aforementioned canonical representation
https://www.postgresql.org/docs/current/rangetypes.html#RANGETYPES-
DISCRETE.
Is this issue still relevant for the current state of Django ? IMO it's a
good feature to add...
Looking forward for opinions.
--
Ticket URL: <https://code.djangoproject.com/ticket/27147#comment:12>
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/065.317d4072066935109a836b6e16cddc42%40djangoproject.com.
