Re: Passing server_encoding to the client is not future-proof

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Carlos Guzman Alvarez <carlosga(at)telefonica(dot)net>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Passing server_encoding to the client is not future-proof
Date: 2003-08-31 19:06:17
Message-ID: Pine.LNX.4.44.0308312105420.1119-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

Carlos Guzman Alvarez writes:

> > The JDBC guys wanted to know it. Why is not clear to me, but I figured
> > it was easy enough to make them happy.
>
> I'm using it too in my .NET Data Provider for allow atomatic encoding of
> strings before send it to the server.

Why would you want to do that? The server can do the encoding conversion.
You're bound to get into trouble using this approach.

--
Peter Eisentraut peter_e(at)gmx(dot)net

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2003-08-31 19:09:16 Re: Passing server_encoding to the client is not future-proof
Previous Message Peter Eisentraut 2003-08-31 19:03:58 Re: "is_superuser" parameter creates inconsistencies

Browse pgsql-jdbc by date

  From Date Subject
Next Message Peter Eisentraut 2003-08-31 19:09:58 Re: Passing server_encoding to the client is not future-proof
Previous Message Paul Thomas 2003-08-30 09:12:31 Re: java_objects and create table