> I'm just looking for the correct workaround.
While adding a new collation is the "correct" solution it's a lot of work.
Even then pg can't use different collations anyway unless you reinit
the datadir using initdb.
One workaround is to cast the text value into a bytea value, and then it
will be
> would postgres convert data on the fly from UTF-8(storage) to ASCII for
> sorting
That ain't possible, it seems, or else we wouldn't need UTF-8.
Karsten
--
GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail
-
Cody Pisto wrote:
> I'm just looking for the correct workaround.
The canonically correct workaround it to define your own locale.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 9: In versions below 8.0, t
> Cody Pisto <[EMAIL PROTECTED]> writes:
> > If initdb was done with a C locale, and thus lc_collate and friends
> > where all C, but the database and client encoding was set to UTF-8,
> > would postgres convert data on the fly from UTF-8(storage) to ASCII for
> > sorting or would things just bl
Cody Pisto <[EMAIL PROTECTED]> writes:
> If initdb was done with a C locale, and thus lc_collate and friends
> where all C, but the database and client encoding was set to UTF-8,
> would postgres convert data on the fly from UTF-8(storage) to ASCII for
> sorting or would things just blow up when
Hi Tom,
I did understand what you said, I apologize that it came out otherwise.
I'm just looking for the correct workaround.
If initdb was done with a C locale, and thus lc_collate and friends
where all C, but the database and client encoding was set to UTF-8,
would postgres convert data on t
Cody Pisto <[EMAIL PROTECTED]> writes:
> If this is potentially a problem in postgres somewhere, point me in the
> general direction and I'm more than willing to fix it myself..
You seem not to have absorbed what I said. This *is* the correct result
according to that locale's definition of sorti
Hi Tom,
Thanks for answering,
I pretty much assumed that was the case (whatever library postgres is
using for encoding is causing the "issue")
The[my] problem is, it just seems like completely incorrect behavior..
The quickest and dirtiest examples I can do are that both python and
mysql s
Cody Pisto <[EMAIL PROTECTED]> writes:
> I'm looking for any kind of a reason (and potential workarounds), be it
> bug or otherwise, why the following two queries produce different
> results under a database encoding of UTF8 and lc_collate of en_US.UTF-8:
That's just how it is in most non-C loca
Hi All,
I'm looking for any kind of a reason (and potential workarounds), be it
bug or otherwise, why the following two queries produce different
results under a database encoding of UTF8 and lc_collate of en_US.UTF-8:
SELECT x FROM (SELECT 'Something else' AS x UNION SELECT '-SOMETHING
ELSE
10 matches
Mail list logo
