I noticed that the jsonb field indexing in postgres which is so handy in
filtering does not seem to extend to calls to values(). After digging around a
bit, it seems that sql.query.get_transform() is only called when building a
filter, but not when adding fields for a values call.
Using transforms in both places was mentioned as part of the now closed feature
request, #21863, which states that the "values() call will use always
get_transform() so .values('hstorefield__exact') will work correctly”. This
was a little confusing because values does not use “lookup”, which seems to
refer only to the comparison type extension in the filter string, but I am
still relatively new to django so maybe I’m missing something.
I don’t see evidence of any further discussion of the effect on values calls.
Anyone know if this was on purpose, or just an oversight?
Thanks,
-Rishi.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/5C557351-59AF-450A-A69A-56821E215EB6%40soe.ucsc.edu.
For more options, visit https://groups.google.com/d/optout.
