Re: UTF8 conversion differences from v8.1.3 to v8.1.4 - Mailing list pgsql-general

From Eric Faulhaber
Subject Re: UTF8 conversion differences from v8.1.3 to v8.1.4
Date
Msg-id 44BEACD0.50207@goldencode.com
Whole thread Raw
In response to Re: UTF8 conversion differences from v8.1.3 to v8.1.4  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: UTF8 conversion differences from v8.1.3 to v8.1.4  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-general
Martijn van Oosterhout wrote:
> On Wed, Jul 19, 2006 at 05:24:53PM -0400, Eric Faulhaber wrote:
>> OK, but now that this "feature" has been removed in 8.1.4, how is this
>> supposed to be handled, given that we don't control what string data
>> we're handed?  How does psql deal with it?
>
> Well, bytea handles null like it always has. There must be a way to you
> to store strings into bytea columns... But I only have a vague
> understanding of why bytea won't work for you...

Collation, for one.  Our runtime is extremely sensitive to the order in
which records are read, to the point where I've created a custom locale
just for the PostgreSQL cluster.

Then there's case sensitivity, being able to use string functions in
SQL, etc., etc.  Bottom line, these are valid strings, so we need to
treat them as such.

Thanks,
Eric

pgsql-general by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: UTF8 conversion differences from v8.1.3 to v8.1.4
Next
From: MargaretGillon@chromalloy.com
Date:
Subject: Re: Constraint for two fields unique any order