On Wed, Aug 29, 2007 at 09:49:03PM -0600, Charlie Savage wrote:
Hmm. Its postgresql 8.2.4 + tsearch2 + tree + postgis. postgis in
turn loads proj4 and geos. I grepped through those 3 libraries source
code and did not find any calls to setlocale. So I don't think so.
So now I'm
Hope this is the right place for this post...
I'm been trying out the msvc++ build scripts for postgresql 8.2.4 on my
development laptop (using window xp pro).
I noticed the sort orders of queries changed. Investigating more,
encodings don't seem to be working as expected.
Using a MSVC++
Using a MSYS build:
CREATE DATABASE test1 WITH ENCODING = 'utf8';
show all
lc_collate;en_US.UTF-8
lc_ctype;en_US.UTF-8
lc_messages;C
lc_monetary;C
lc_numeric;C
lc_time;C
Sorry, the above output is for Linux (Fedora Core 6). With an MSYS
build on my XP laptop its:
lc_collate;C
Charlie Savage wrote:
Hope this is the right place for this post...
I'm been trying out the msvc++ build scripts for postgresql 8.2.4 on
my development laptop (using window xp pro).
I noticed the sort orders of queries changed. Investigating more,
encodings don't seem to be working as
Hi Andrew,
Thank for the reply.
In both cases, the database clusters were created like this:
initdb ---locale=c --encoding=utf8;
That seems most unlikely - without the superfluous dash it should set
both lc_collate and lc_ctype to C.
Ah, sorry, that was a typo. If you actually try it:
