#34080: __exact lookup on nested arrays with None values fails on PostgreSQL.
----------------------------------+---------------------------------------
Reporter: Ion Alberdi | Owner: Ion Alberdi
Type: Bug | Status: assigned
Component: contrib.postgres | Version: 4.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+---------------------------------------
Comment (by David Sanders):
ok so further looking into this it appears that the array constructor
doesn't try to infer types in literals at all even if the literal contains
only int; using an array literal within a constructor should always be
cast.
{{{
# SELECT *
FROM "ticket_34080_foo"
WHERE "ticket_34080_foo"."field_nested" = (ARRAY['{1}'])::integer[][]
LIMIT 21;
ERROR: invalid input syntax for type integer: "{1}"
LINE 3: WHERE "ticket_34080_foo"."field_nested" = (ARRAY['{1}'])::i...
^
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34080#comment:10>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070183d10d55cd-0b79bc09-a6cb-42f4-9cb1-ca6a841d85ab-000000%40eu-central-1.amazonses.com.
