From: | Alvaro Herrera <alvherre(at)surnet(dot)cl> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Oliver Jowett <oliver(at)opencloud(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SQL_ASCII vs. 7-bit ASCII encodings |
Date: | 2005-05-13 14:17:10 |
Message-ID: | 20050513141709.GC7182@surnet.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, May 13, 2005 at 09:59:27AM -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)surnet(dot)cl> writes:
> > The problem is that a single application coming from a single
> > environment is happy with a 8-bit-unchecked encoding, but as soon as
> > they develop a second application using a different environment, which
> > uses a different encoding, they start seeing invalid data pop up.
>
> [ shrug... ] The evidence at hand says that many people never get to
> that point. For instance, a particular database may never be accessed
> through anything except JDBC, and so all the incoming data will be utf8
> anyway.
One thing that's not clear to me is what encoding does people running on
Windows get? Is it also determined based on locale, and is it something
useful?
In fact I've seen many more people with this problem after 8.0 was
released, at least in pgsql-es-ayuda.
--
Alvaro Herrera (<alvherre[a]surnet.cl>)
"La verdad no siempre es bonita, pero el hambre de ella sí"
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-05-13 14:22:06 | Re: SQL_ASCII vs. 7-bit ASCII encodings |
Previous Message | Tom Lane | 2005-05-13 13:59:27 | Re: SQL_ASCII vs. 7-bit ASCII encodings |