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

From Bruce Momjian
Subject Re: BIT/BIT VARYING status
Date
Msg-id 200101211357.IAA10073@candle.pha.pa.us
Whole thread Raw
In response to Re: BIT/BIT VARYING status  (Adriaan Joubert <a.joubert@albourne.com>)
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.

Should I add this to the TODO list?

> 
> 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
> 


--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Denis Perchine
Date:
Subject: Re: Re: [PATCHES] Patch to support transactions with BLOBs for current CVS
Next
From: Frank Joerdens
Date:
Subject: Re: beta3 vacuum crash