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
26345	Clarify that RangeFields always return canonical form of ranges	David Binetti	nobody	"Asked on #django to no response, so filing here.

When saving a postgres DateRange object to a DateRangeField, the `bounds` are always changed to the default, even if a different bounds is requested.  The date payload (upper or lower), is also changed according to the new bounds.  This may be as designed, but it unexpected from my perspective. 

For instance, my users may enter data in a form to express a two day event as Jan 1 2016 - Jan 2 2106, '[]' (inclusive lower and inclusive upper.)  However, this is translated in the database as Jan 1 2016 - Jan 3 2016 '[)' (inclusive lower *exclusive* upper with changed date) so if I then try to render the upper date directly, it will do so as Jan 3, confusing the user (and the developer :-)  !)  

Yes, I could accommodate this with some display logic, but that strikes me as the wrong approach.  I've included a repo with a test demonstrating what I was expecting to see.

https://github.com/dbinetti/djangodaterange"	Cleanup/optimization	closed	Documentation	1.9	Normal	fixed			Accepted	1	0	0	0	0	0