#35194: Postgres 16.2 with _iexact leads to IndeterminateCollation
-------------------------------------+-------------------------------------
Reporter: Aldalen | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* resolution: => needsinfo
* severity: Release blocker => Normal
* stage: Accepted => Unreviewed
* status: new => closed
Comment:
It is currently not clear whether the bug is on Postgres side or not.
Until this is clear, we can keep the ticket in the "needsinfo" state as it
best represents it's current status.
Reopening the ticket did bring it to the attention of others and has
helped us look into this a little more, but even in a closed state, the
ticket is still "visible"/searchable.
We can reopen once we better understand the root of the problem and it's
clear that Django needs to implement changes.
--
Ticket URL: <https://code.djangoproject.com/ticket/35194#comment:13>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018f3d69e8d2-44c16cd0-6419-42f2-9350-d58444487004-000000%40eu-central-1.amazonses.com.
