#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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"fc565cb539e4c1e5fba70d9ebb19bac0ca251d37" fc565cb]:
{{{
#!CommitTicketReference repository=""
revision="fc565cb539e4c1e5fba70d9ebb19bac0ca251d37"
Fixed #27147 -- Allowed specifying bounds of tuple inputs for non-discrete
range fields.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27147#comment:22>
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.381f8ee90e5116d2e8729ec2186fd92c%40djangoproject.com.
