Opened 17 years ago

Closed 17 years ago

#4340 closed (fixed)

[unicode] Missing mapping in postgresql encodings

Reported by: tim@… Owned by: Malcolm Tredinnick
Component: Database layer (models, ORM) Version: other branch
Severity: Keywords: unicode postgresql
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

The mapping between postgresql and python encoding in unicode branch is missing some entries to be able to work with older version of postgresql : source:django/branches/unicode/django/db/backends/postgresql/encodings.py

Postgresql only return 'UTF8' value for client_encoding since version 8.1, older version return 'UNICODE'.

For reference, see:

Change History (4)

comment:1 by Malcolm Tredinnick, 17 years ago

Owner: changed from Adrian Holovaty to Malcolm Tredinnick
Summary: Missing mapping in postgresql encodings → [unicode] Missing mapping in postgresql encodings
Triage Stage: Unreviewed → Accepted

comment:2 by Malcolm Tredinnick, 17 years ago

You say the mapping is missing "some entries", but only point out the UNICODE entry. Which other ones are missing?

comment:3 by tim@…, 17 years ago

Sorry, I was too lazy to make a diff between old postgresql version and new ones ...

It seems that those entries are missing (based on difference between 7.4 and 8.2 table) :

  • UNICODE (utf-8)
  • WIN (Windows CP1251)
  • ALT (Windows CP866)
  • TCVN (TCVN-5712/Windows CP1258 (Vietnamese))

comment:4 by Malcolm Tredinnick, 17 years ago

Resolution: → fixed
Status: new → closed

(In [5286]) unicode: Fixed #4340 -- added a few character set encodings that PostgreSQL 7.x
can return. Pointed out by tim@….

Note: See TracTickets for help on using tickets.
Back to Top