Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Fabien COELHO wrote:
>> I think that the inability to convert nearly binary compatible standard
>> types one to the other is a postgresql issue. Even if it is not often
>> useful, the point is completeness and soundness of the type provided by
>> the core.
> OK, can I get some feedback from others about this patch?
I think Fabien is way overstating his case here. It's not immediately
obvious that there should be a cast between bit(n) and bytea, and it's
even less obvious that it should be done in a way that exposes the
internal representation of bit(n) as this does. There's no principled
reason for one bit ordering over the other, for example, nor any very
clean way to handle coercions where N isn't a multiple of 8.
I think this request has more to do with a lack of adequate operators
for one type or the other. If we're missing, say, bitwise logical
operators for bytea, then let's add those rather than create a bogus
equivalence between the types.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
