Re: BIT/BIT VARYING status - Mailing list pgsql-hackers

From Adriaan Joubert
Subject Re: BIT/BIT VARYING status
Date
Msg-id 3A6A8518.3C18B2F2@albourne.com
Whole thread Raw
In response to Re: Re: BIT/BIT VARYING status  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: BIT/BIT VARYING status
List pgsql-hackers
Main open item is the handling of hex strings: they are still converted
to integers by default. They could be BLOBs or bit strings, and the SQL
standard gives no hint, so it is not clear what the solution should be.

The only other complaint has been on the output of bit strings. I
believe the current policy is that they are always output in binary, but
I have had a request for output in hex. We may have to add a function
that allows the user to use the hex output routine (a SET variable or
some type of conversion function). I agree with leaving the default
binary as most people seem to want to use it for bit masks anyway.

Adriaan


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: [PATCHES] Patch to support transactions with BLOBs for current CVS
Next
From: Denis Perchine
Date:
Subject: Re: Re: [PATCHES] Patch to support transactions with BLOBs for current CVS