Re: BIT/BIT VARYING status

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Adriaan Joubert <a(dot)joubert(at)albourne(dot)com>
Cc: Postgresql <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: BIT/BIT VARYING status
Date: 2001-01-21 13:57:51
Message-ID: 200101211357.IAA10073@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Jerusalem 2001-01-21 16:01:34 Re: postgres memory management
Previous Message Alexander Jerusalem 2001-01-21 12:18:54 postgres memory management