#34470: client_encoding is no longer enforce on PostgreSQL.
-------------------------------------+-------------------------------------
Reporter: Mariusz Felisiak | Owner: Mariusz
| Felisiak
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"b0d7753d07231fad780de61cd8bfddc5bbd1aa1c" b0d7753d]:
{{{
#!CommitTicketReference repository=""
revision="b0d7753d07231fad780de61cd8bfddc5bbd1aa1c"
[4.2.x] Fixed #34470 -- Enforced UTF-8 encoding on PostgreSQL.
Regression in 6a2165816394ab4bb259f6171e82417e098e97a6.
Backport of 5b8a043bf51ab8bcf4a758d0b4646f30a84be183 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34470#comment:6>
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/010701875ac66dbc-4617feec-5ed9-4082-acc2-367516bffcf7-000000%40eu-central-1.amazonses.com.
