#28880: The QuerySet.query sql representation of an ORM call on a PostgreSQL
ArrayField is missing a key bit of syntax.
-------------------------------------+-------------------------------------
Reporter: Alexander Kavanaugh | Owner: (none)
Type: Bug | Status: new
Component: contrib.postgres | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage:
postgres,arrayfield,syntaxerror,.query,as_sql,ARRAY| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Curtis Maloney):
It's important to remember that calling str(queryset.query) has not yet
passed the query to the DB-API driver for proper escaping and type
coercion, so it's not always _exactly_ what's sent to the DBMS.
Although ArrayField is postgres only currently, should some other DBMS
support it, and Django add support for their syntax, forcing the repr to
use Postgres's syntax would only result in someone raising a similar
ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/28880#comment:1>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.bbe5904115fb833a7f84b82ba84ffa3d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
