Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: UTF8 should be accepted as UNICODE
- From: Kris Jurka <books(at)ejurka(dot)com>
- To: Dave Cramer <pg(at)fastcrypt(dot)com>
- Cc: Ivo Danihelka <ivo(dot)danihelka(at)itonis(dot)tv>, pgsql-jdbc(at)postgresql(dot)org
- Subject: Re: UTF8 should be accepted as UNICODE
- Date: Fri, 22 Feb 2008 11:35:22 -0500 (EST)
On Fri, 22 Feb 2008, Dave Cramer wrote:
But it should probably ignore your attempt, since it has no effect.
The problem is that there are a lot of potential aliases to check, "SET client_encoding = 'UTF -- 8'". We could try to normalize it and then check it, but I don't think it's worth it.
Kris Jurka
- References:
- UTF8 should be accepted as UNICODE
- From: Ivo Danihelka
- Re: UTF8 should be accepted as UNICODE
- From: Dave Cramer
- UTF8 should be accepted as UNICODE
- Prev by Date: JVM crash when select count(*) on large table through JDBC
- Next by Date: Re: JVM crash when select count(*) on large table through JDBC
- Previous by thread: Re: UTF8 should be accepted as UNICODE
- Next by thread: JVM crash when select count(*) on large table through JDBC
- Indexes: