Skip site navigation (1) Skip section navigation (2)

Re: encoding names

From: Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>
To: Barry Lind <barry(at)xythos(dot)com>
Cc: pgsql-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: encoding names
Date: 2001-08-19 12:58:44
Message-ID: 20010819145844.B26874@zf.jcu.cz (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
On Fri, Aug 17, 2001 at 10:37:18AM -0700, Barry Lind wrote:
> This patch will break the JDBC driver.  The jdbc driver relies on the 
> value returned by getdatabaseencoding() to determine the server encoding 
> so that it can convert to unicode.  This patch changes the return values 
> for getdatabaseencoding() such that the driver will no longer work.  For 
> example "LATIN1" which used to be returned will now come back as 
> "iso88591".  This change in behaviour impacts the JDBC driver and any 
> other application that is depending on the output of the 
> getdatabaseencoding() function.

 Hmm.. but I agree with Peter that correct solution is rewrite it to
standard names.
 
> I would recommend that getdatabaseencoding() return the old names for 
> backword compatibility and then deprecate this function to be removed in 
  ^^^^^^^^^^^^^^^^^^^^^
 We can finish as great Microsoft systems... nice face but terrible old stuff
in kernel.

-- 
 Karel Zak  <zakkr(at)zf(dot)jcu(dot)cz>
 http://home.zf.jcu.cz/~zakkr/
 
 C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz

In response to

pgsql-hackers by date

Next:From: Karel ZakDate: 2001-08-19 13:03:03
Subject: Re: encoding names
Previous:From: Karel ZakDate: 2001-08-19 12:46:58
Subject: Re: encoding names

pgsql-patches by date

Next:From: Karel ZakDate: 2001-08-19 13:03:03
Subject: Re: encoding names
Previous:From: Karel ZakDate: 2001-08-19 12:46:58
Subject: Re: encoding names

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group