#27147: Add support for defining bounds in postgres range fields
-------------------------------------+-------------------------------------
Reporter: Kirill Stepanov | Owner: Guilherme
| Martins Crocetti
Type: New feature | Status: assigned
Component: contrib.postgres | Version: dev
Severity: Normal | Resolution:
Keywords: postgres range | Triage Stage: Accepted
bounds |
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Guilherme Martins Crocetti):
Replying to [comment:13 Carlton Gibson]:
> Hi Guilherme, welcome!
>
> It still looks like a reasonable suggestion yes.
>
> I'd review Matthew's comments and the patch from Jakub and Jon, and then
see what the remaining issue are.
> From the PR, I'd guess that making sure you have a good range of test
cases will be key.
Hey Carlton, I've asked help for contributors in both Github and Django's
mailing group without success. The PR has been opened for two months and
I'm starting to loose context of what I had done. Is there any chance of
you giving it a shot (I'm mentioning you cause you gave the starting tip)
? IMO the overall solution looks solid but need a green light before
spending energy writing documentation.
The PR is quite short :). Looking forward for a review.
--
Ticket URL: <https://code.djangoproject.com/ticket/27147#comment:17>
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.431f7d7363c7fcd8bb4a7ec7dbd5be4f%40djangoproject.com.
