id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
27147	Add support for defining bounds in postgres range fields	Kirill Stepanov	Guilherme Martins Crocetti	"Django supports postgres range types in the contrib package, but the bounds are restricted to the default value of ""[)"" (inclusive low value, exclusive high value) in psycopg2. I propose that django add support for all bounds types - ""[]"", ""(]"", ""[)"" and ""()"".

Psycopg2 documentation on the matter: http://initd.org/psycopg/docs/extras.html?highlight=range#range-data-types
Postgres documentation on the syntax: https://www.postgresql.org/docs/9.2/static/rangetypes.html#RANGETYPES-IO

I think this could easily be implemented via another argument to the range field type contructor which could be passed down to the psycogp2 range type whenever it's created. Everything else should be automatic after that. Some validation is probably a good idea too.

If people think this is a useful feature, I'll try to write a patch."	New feature	closed	contrib.postgres	dev	Normal	fixed	postgres range bounds	George Tantiras Paolo Melchiorre	Ready for checkin	1	0	0	0	0	0