Alvaro Herrera wrote:
For example, with all LC_* parameters set to "en_US.UTF8", I get the
following incorrect "order:by":
Béarn
Bécancour
Beaupré
Did you initdb with locale en_US.UTF8, and also createdb with encoding
UTF8? While you can certainly choose mismatching values
John Gunther wrote:
> >Pretty much any locale (say, en_US for you) with a matching character
> >set should work. Unless you go out of your way, this should be the
> >default setting.
>
> >>I've tried a half dozen time-consuming configs without
> >>success.
>
> >Like what?
>
> For example, wi
Pretty much any locale (say, en_US for you) with a matching character
set should work. Unless you go out of your way, this should be the
default setting.
I've tried a half dozen time-consuming configs without
success.
Like what?
For example, with all LC_* parameters set to "en_US.UTF8",
John Gunther wrote:
> Can someone tell me what combination of PostgreSQL and Linux settings
> I need for this? Or point me somewhere that it's well explained. It
> seems like a very basic question, but I'm just dense,
> I guess.
Pretty much any locale (say, en_US for you) with a matching character
I've been reading about locales, encodings, sort orders, the to_ascii
function but I'm more confused than enlightened.
What I want is very simple:
1) I want the database to correctly accept, store, and display
alphabetic characters, including European accented characters, entered
and viewed in H
I've
been reading about locales, encodings, sort orders, the to_ascii
function and, embarrasingly, I'm more confused than enlightened.:
What I want is very simple:
1) I want the database to correctly accept, store, and display
alphabetic characters, including European accented characters,
