#33344: Define bounds transform for discrete postgres range fields
-------------------------------------+-------------------------------------
Reporter: Vidir Valberg | Owner: (none)
Gudmundsson |
Type: New feature | Status: closed
Component: contrib.postgres | Version: dev
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Vidir Valberg Gudmundsson):
Replying to [comment:4 Mariusz Felisiak]:
> Moreover this can be confusing for users who will assume that values are
stored with different bounds.
Yeah, that I can agree on. That's also why I want to somehow name the
feature along the lines of "transform", "cast" og maybe "output". Also the
default would be "[)" thus only something one would set if one wanted to
change the output behaviour.
--
Ticket URL: <https://code.djangoproject.com/ticket/33344#comment:6>
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.82af67751c8ea63669c472f9db6b7e6f%40djangoproject.com.
