upper to get case insensitive
ordering if I ever need it.
The bottom line seems to be: if you're planning to store data with languages
from across the world, initialise your database cluster with the C locale
and Unicode encoding.
Thanks again to everyone who replied!
Kind regards
Harry Mant
ing with C locale.
Okay, that's great, so I'm going to re-initialise my database cluster with
the C locale this week-end.
I'll report the results, for the record.
Thanks to everyone who replied!
Kind regards
Harry Mantheakis
London, UK
---(end of broa
d words.
I think I'll have to suck it and see, and then post my results - but that
won't be until after this next week-end.
Kind regards
Harry Mantheakis
London, UK
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
European names/words. (I've tried searching for
this topic, but failed to find an answer.)
Would specifying a locale for LC_COLLATE take care of this? Perhaps
something like this:
initdb --locale=C --lc-collate=en_GB.UTF-8 --encoding UNICODE
I'm sorry to drag this out. Perhaps I can
dora Core 3.
Meanwhile, am I correct in assuming that re-initialising my database cluster
with "--locale=C" will solve the problem?
What is more, am I correct in assuming that I can then restore my data with
pg_restore, as prescribed in the documentation?
Kind regards
Harry Manth
I wonder if someone might be kind enough to confirm that this is the right
approach to solving the problem.
Many thanks!
Harry Mantheakis
London, UK
---(end of broadcast)---
TIP 6: explain analyze is your friend
