Re: UTF8 conversion differences from v8.1.3 to v8.1.4

From: Eric Faulhaber <ecf(at)goldencode(dot)com>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org
Subject: Re: UTF8 conversion differences from v8.1.3 to v8.1.4
Date: 2006-07-19 22:06:08
Message-ID: 44BEACD0.50207@goldencode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message MargaretGillon 2006-07-19 23:26:42 Re: Constraint for two fields unique any order
Previous Message Martijn van Oosterhout 2006-07-19 21:45:00 Re: UTF8 conversion differences from v8.1.3 to v8.1.4