#34470 closed Bug (fixed)
client_encoding is no longer enforce on PostgreSQL.
| Reported by: | Mariusz Felisiak | Owned by: | Mariusz Felisiak |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 4.2 |
| Severity: | Release blocker | Keywords: | |
| Cc: | Florian Apolloner, Anders Kaseorg | Triage Stage: | Accepted |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
client_encoding defined in get_connection_params() is always overridden in the following code.
Regression in 6a2165816394ab4bb259f6171e82417e098e97a6.
Change History (6)
comment:1 by , 3 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 3 years ago
| Summary: | client_encoding is no longer set on PostgreSQL. → client_encoding is no longer enforce on PostgreSQL. |
|---|
comment:4 by , 3 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
I "accepted" based on the Florian's approval on PR.
Note:
See TracTickets
for help on using tickets.
By default, client encoding is the encoding defined by the database but we should still enforce
utf-8.