Re: BUG #1578: ::bit(n) behaves "differently" if applied to bit

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Celia McInnis <celia(at)drmath(dot)ca>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1578: ::bit(n) behaves "differently" if applied to bit
Date: 2005-05-11 05:36:51
Message-ID: 563.1115789811@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> ... Though this is slightly inconsistent in how it works with a
> bit string, it does seem the most useful approach.

Also, this is a behavior that we changed in 8.0 in response to previous
complaints. Before changing it again, I'd want to see a pretty detailed
analysis of either (1) why the previous complainers were idiots, or
(2) why this change is still compatible with what they asked for ;-)

Where relevant, comments on SQL spec compliance would help the argument
too. I don't think the spec defines any bit<->integer conversions,
but it definitely addresses the issue of converting from bit(m) to bit(n).

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message brahim 2005-05-11 12:36:00 BUG #1659: primary key accepts null value
Previous Message Bruce Momjian 2005-05-11 03:25:33 Re: BUG #1578: ::bit(n) behaves "differently" if applied to bit