#34255: Annotation/group by with an expression on psycopg3
-------------------------------------+-------------------------------------
Reporter: Guillaume Andreu | Owner: Mariusz
Sabater | Felisiak
Type: Bug | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: orm postgres | Triage Stage: Accepted
psycopg3 annotation groupby |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
I suggest that CI have a build that uses `server_side_binding` so that
regressions aren't introduced for that configuration. For example, in the
current PostgreSQL build that defaults to client-side binding,
`ConcatPair.as_postgresql` can be removed without any test failures.
`test_group_by_nested_expression_with_params` needs to be marked as
expected failure when using `server_side_binding`. Is it appropriate to
create a follow-up ticket if it might be possible to fix that in the
future?
When I read the current "Server-side parameters binding" section in
Django's docs, it left me wondering how to choose between the two. Perhaps
there's not much more to be said than what's in the psycopg documentation.
Though we typically don't document bugs, I wonder if Django's
documentation should note the limitation for queries like the one reported
here.
--
Ticket URL: <https://code.djangoproject.com/ticket/34255#comment:16>
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/01070185f0ba8100-91a1110f-1d97-4e82-b78e-b31a21078faa-000000%40eu-central-1.amazonses.com.
