Opened 10 years ago

Last modified 10 years ago

#24169 closed Bug

ArrayField can't use __contained_by or __overlap queries for CharField — at Version 1

Reported by: Joel Burton Owned by:
Component: contrib.postgres Version: 1.8alpha1
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Joel Burton)

ArrayField's lookup.py uses the @> operator for __contains, the <@ operator for __contained_by, and the && operator for __overlap.

When the field uses CharField (Postgres' varchar()), __contains works, but __contained_by and __overlap do not, as Postgres does not define <@ and && operators for an array of varchar[] (it does for text[]).

__contains works because, in array.py, there is a custom lookup, "ArrayOverlap", the outputs a cast to cast the array query value to, say, "::varchar(10)[]"

If there are similar custom lookups for __contained_by and __overlap, these then work.

Change History (2)

comment:1 by Joel Burton, 10 years ago

Description: modified (diff)

by Joel Burton, 10 years ago

Attachment: array.py-patch​ added

Patch, along with tests

Note: See TracTickets for help on using tickets.
Back to Top