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
- [HACKERS] Re: BIT/BIT VARYING status Adriaan Joubert
- Re: [HACKERS] Re: BIT/BIT VARYING status Peter Eisentraut
- Re: [HACKERS] Re: BIT/BIT VARYING status Adriaan Joubert
- Re: [HACKERS] Re: BIT/BIT VARYING status Peter Eisentraut
- Re: [HACKERS] Re: BIT/BIT VARYING status Adriaan Joubert
- Re: [HACKERS] Re: BIT/BIT VARYING status Adriaan Joubert
- Re: [HACKERS] Re: BIT/BIT VARYING s... Peter Eisentraut
- Re: [HACKERS] Re: BIT/BIT VARYING s... Peter Eisentraut
- Re: [HACKERS] Re: BIT/BIT VARYING status Bruce Momjian
- Re: [HACKERS] Re: BIT/BIT VARYING status Bruce Momjian
- [HACKERS] Re: BIT/BIT VARYING status Adriaan Joubert
- [HACKERS] Re: BIT/BIT VARYING status Bruce Momjian