#33642: Can't create objects with Postgres range fields without upper and lower
bounds in the admin
--------------------------------------------+------------------------
Reporter: Tom Carrick | Owner: (none)
Type: Bug | Status: new
Component: contrib.postgres | Version: dev
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 1 |
--------------------------------------------+------------------------
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/33642>
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/0107018022bde271-87d6a268-893f-472c-8299-610871f250ab-000000%40eu-central-1.amazonses.com.
