#35734: Tests fail with Postgres 16 and server side bindings
-------------------------------------+-------------------------------------
Reporter: john-parton | Owner: john-
| parton
Type: Bug | Status: assigned
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Natalia Bidart):
Replying to [comment:4 john-parton]:
> Thanks. I assume Nick can take a crack at it? Otherwise I can take a
look. A little busy at the moment, so not sure when I could get to it.
Thank you John for your PR and work on this. We'll review soon!
> Do we need to add Postgres 16/15 to CI? I know there's already a ton of
different configs tested, but it would have caught this if it were in the
CI pipeline.
This is a very valid point and I would like us to pursue a more
sustainable solution for this testing other than "each one does it on
their own laptop".
John, would you be willing to raise this issue in the Django Forum to see
if we could get some traction to setup this? I think we could have **at
least** a new entry in the scheduled tests to test all supported version,
or at least the oldest (current setup) and the newest.
--
Ticket URL: <https://code.djangoproject.com/ticket/35734#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/01070191d850ca23-ad502284-64a6-46e2-a0d9-70339dc6888e-000000%40eu-central-1.amazonses.com.
