From: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com> |
Cc: | PostgreSQL Hackers List <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: bit type external representation |
Date: | 2002-07-16 06:21:12 |
Message-ID: | 3D33BB58.893BA2F9@fourpalms.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > 1) the SQL standard says what hex values should be translated to in
> > binary, which implies that all values may be *output* in binary format.
> So the standard says both represent a fixed-length bit string data type.
> ISTM that we should not try to preserve any information on the units
> used for input, and that both should be output in the same way.
OK, that's how I read it too. I'll work on making it behave with hex
input and not worry about the output, which takes care of itself.
I also notice that the following has trouble:
thomas=# select bit '1010';
ERROR: bit string length does not match type bit(1)
which is similar to the very recent problem with fixed-length character
strings. I've got patches to fix this one too.
- Thomas
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-07-16 06:25:27 | Re: BlockNumber fixes |
Previous Message | Christopher Kings-Lynne | 2002-07-16 06:18:10 | Re: Unused system table columns |