From: | Gregory Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Gregory Stark <gsstark(at)mit(dot)edu>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org, Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Subject: | Re: Fixed length data types issue |
Date: | 2006-09-08 07:47:59 |
Message-ID: | 87ac5ayf2o.fsf@stark.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Gregory Stark wrote:
> > > But that won't help in the example you posted upthread, because
> > > char(N) is not fixed-length.
> >
> > Sure it is because any sane database--certainly any sane database
> > using char(N)--is in C locale anyways.
>
> This matter is completely independent of the choice of locale and
> therefore any unilateral redefinition of sanity that you might come up
> with.
Except it isn't. If you're dealing with fixed length ascii codes from existing
databases you interoperate with then you will have problems if you initialize
your database in a non-C locale. Interpreting those codes in your locale will
be do incorrect things like treat them as case insensitive or ignore spaces in
collation, etc.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2006-09-08 07:58:47 | Re: Fixed length data types issue |
Previous Message | Peter Eisentraut | 2006-09-08 07:41:47 | Re: Fixed length data types issue |