From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
Cc: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: bit strings - anyone working on them? |
Date: | 2003-04-23 16:02:33 |
Message-ID: | 27021.1051113753@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
> At 11:51 AM 23/04/2003 -0400, Tom Lane wrote:
>> The only way to get the same answer both ways would be to legislate that
>> int-to-bitstring conversion puts the integer's LSB at the left
> That's what I think we need to do. Alternatively, we put the LSB on the
> right, change the way substring works on varbit, and pad them on the left.
> I suspect this will also break existing apps.
I doubt that we can change the padding rule without violating spec.
How about leaving the cast alone (okay, we can add the cast-directly-to-
a-different-width cases), so as not to break existing apps, and instead
add a separate function that maps an integer to an LSB-first bitstring?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Saito | 2003-04-23 16:37:28 | Re: linking problem with gcc-mingw |
Previous Message | Dave Page | 2003-04-23 15:37:05 | Re: Are we losing momentum? |