#36078: Postgres date and time range fields change after saving object
----------------------------------+--------------------------------------
Reporter: Mapiarz | Owner: (none)
Type: Bug | Status: closed
Component: contrib.postgres | Version: 4.2
Severity: Normal | Resolution: invalid
Keywords: postgres | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Changes (by Sarah Boyce):
* resolution: => invalid
* status: new => closed
Comment:
Thank you for the careful report I was able to replicate and had a look
into this
From what I can tell, this is Postgres behavior and so I don't think this
is a bug in Django
See https://www.postgresql.org/docs/current/rangetypes.html#RANGETYPES-IO
> {{{
> -- includes no points (and will be normalized to 'empty')
> SELECT '[4,4)'::int4range;
> }}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36078#comment:2>
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 visit
https://groups.google.com/d/msgid/django-updates/010701944fbf1d43-15e84f05-a013-426f-af50-dc52e92d6a1b-000000%40eu-central-1.amazonses.com.
