> On Wednesday 31 December 2008 18:57:29 Karsten Hilbert wrote: > > The solution is to find the right layer to take control of the encoding > but > > this is eventually only possible if the encoding is *known*. Thus the > plea > > for "7-bit-ascii English by default until the encoding *can* be known". > > Going to "7-bit-ascii filter of the original by default until the > encoding > > can be known" only tries to preserve a bit more of the original > language. I > > may be wrong in feasibility. > > The proper fix is probably to include the client encoding in the > connection startup message.
Absolutely, either the desired client encoding being sent to the server or the current server encoding being sent to the client. It would, however, take way longer to trickle down into being supported by client interfaces such as psycopg2 <evil grin> A fixed startup encoding would not need support from those parts of the equation. Karsten -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
