#36078: Document that Postgres normalizes a range field with no points
normalizes
to empty
--------------------------------------+------------------------------------
Reporter: Mapiarz | Owner: (none)
Type: Cleanup/optimization | Status: new
Component: contrib.postgres | Version: 4.2
Severity: Normal | Resolution:
Keywords: postgres | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Mapiarz):
I agree. There should be an explicit warning about this. It's really easy
to be caught of guard by this and lose data.
I do not understand why psycopg opted out of normalizing the value to
empty, just like postgres does. I have raised this issue here:
https://github.com/psycopg/psycopg/discussions/993
--
Ticket URL: <https://code.djangoproject.com/ticket/36078#comment:5>
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/01070194603403d1-3ce934ec-df11-4ff5-8ae5-bcc5e54202db-000000%40eu-central-1.amazonses.com.
