#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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => needsinfo
Comment:
Thanks for this ticket, however it's not clear for me what do you want to
achieve. Bounds cannot be specify for discrete range types because they
are not natively supported on PostgreSQL. I don't think we should add
implicit logic in our fields to give the impression that they are, this
looks error-prone and it's probably not worth the complexity.
--
Ticket URL: <https://code.djangoproject.com/ticket/33344#comment:3>
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.321d8e3bcbe958dab5bd30046a257a05%40djangoproject.com.
