#34255: Annotation/group by with an expression on psycopg3
-------------------------------------+-------------------------------------
Reporter: Guillaume Andreu | Owner: nobody
Sabater |
Type: Bug | Status: new
Component: Database layer | Version: dev
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: orm postgres | Triage Stage: Accepted
psycopg3 annotation groupby |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Florian Apolloner):
Replying to [comment:2 Simon Charette]:
> Edit, another solution could be to have the psycopg3 query `%s -> $n`
logic de-duplicate equal values and avoid using multiple placeholders for
them.
I would love to see this done for Django in general and not at the
individual backend level. That said it is probably to late for 4.1
If we cannot fix the issue at hand nicely I think we could fall back to
client side cursors and provide a setting (backend option) to switch back
to server side cursors so people can experiment with them. Btw from the
looks of it and issues we ran into developing psycopg3 support, this also
means that the postgresql backend is basically the only backend using
server side bindings or is it just stricter than every other backend?
--
Ticket URL: <https://code.djangoproject.com/ticket/34255#comment:8>
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/01070185a9fd5576-a0970ef3-aa31-41b5-b768-104cbbbf924e-000000%40eu-central-1.amazonses.com.
