#34080: __exact lookup on nested arrays with None values fails on PostgreSQL.
----------------------------------+------------------------------------
Reporter: Ion Alberdi | Owner: nobody
Type: Bug | Status: new
Component: contrib.postgres | Version: 4.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by Mariusz Felisiak):
> The rhs variables look correct to me. I'll continue digging, so far I
tend to go towards the psycopg2 bug hypothesis.
As far as I'm aware it's not a `psycopg2` issue but PostgreSQL-behavior.
Regression tests work when we skip wrapping values in `ARRAY()` for
`None`-only arrays, so this should be fixable on Django side.
--
Ticket URL: <https://code.djangoproject.com/ticket/34080#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070183c1b3def6-c5d847d6-f50e-41ae-960d-d19333c02ded-000000%40eu-central-1.amazonses.com.
