Re: BIT/BIT VARYING status

From: Adriaan Joubert <a(dot)joubert(at)albourne(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Postgresql <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: BIT/BIT VARYING status
Date: 2001-01-21 06:43:36
Message-ID: 3A6A8518.3C18B2F2@albourne.com
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.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Denis Perchine 2001-01-21 06:48:17 Re: Re: [PATCHES] Patch to support transactions with BLOBs for current CVS
Previous Message Steve Howe 2001-01-21 05:04:41 This script will crash the connection