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
33642	Can't create objects with Postgres range fields without upper and lower bounds in the admin	Tom Carrick		"There is some funky behaviour when using Postgres range fields in the admin.

I only tested with DateTimeRangeField but I imagine it's the same for the others.

----

Using `period = DateTimeRangeField()`:

Trying to add an item without lower and upper bounds results in an error that the field is required.

Adding an item with a lower bound but no upper bound, or vice versa does work.

----

Using `period = DateTimeRangeField(blank=True, null=True)`:

Adding an item without any bound gives a null for the column, which is not always what I want.

----

Using `period = DateTimeRangeField(blank=True)`:

Tries to do as above but fails on the null constraint.

----

I imagine this needs a bit of UX thought as it should be possible to do either: set the column to null or set the column to a range with null as both bounds."	Bug	closed	contrib.postgres	dev	Normal	needsinfo			Unreviewed	0	0	0	0	0	1