#27213: ArrayField with null throws ProgrammingError but not ValidationError on
Psycopg < 2.6.1
-------------------------------------+-------------------------------------
Reporter: Mark Mikofski | Owner: nobody
Type: Bug | Status: closed
Component: contrib.postgres | Version: 1.9
Severity: Normal | Resolution: wontfix
Keywords: postgres, | Triage Stage:
arrayfield, programmingerror | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* resolution: worksforme => wontfix
Comment:
I could reproduce the exception with older versions of Psycopg. It seems
that Psycopg 2.6.1 fixes it. I don't think it's worth trying to fix this
in Django for older versions of Psycopg.
--
Ticket URL: <https://code.djangoproject.com/ticket/27213#comment:3>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.d56230e97497388a0b9681bae540d377%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
