Christopher Kings-Lynne wrote:
>
> > Some SQL92 functionality is missing from the BIT and VARBIT types.
> >
> > It should be possible to enter hexadecimal values as:
> >
> > B'[...]'[{...'[ > X'[...]'[{...'[ >
> > (Cannan and Otten: SQL - The Standard Handbook, p.38)
> >
> > but the hexadexim
"Christopher Kings-Lynne" wrote:
>I have been using the BIT and VARBIT types in Postgres 7.0.3 (undocumented I
>believe), and I note that the _input_ format is as follows:
>
>update blah set flags='b101001'; -- Binary
That is still accepted.
>update blah set flags='xff45'; -- Hex
> Some SQL92 functionality is missing from the BIT and VARBIT types.
>
> It should be possible to enter hexadecimal values as:
>
> B'[...]'[{...'[ X'[...]'[{...'[
> (Cannan and Otten: SQL - The Standard Handbook, p.38)
>
> but the hexadeximal form is not accepted.
I have been using the BIT a
Peter Eisentraut wrote:
>Oliver Elphick writes:
>
>> Some SQL92 functionality is missing from the BIT and VARBIT types.
>>
>> It should be possible to enter hexadecimal values as:
...
>This was omitted because in SQL99 the X'1001' notation also serves as a
>binary large object value
Oliver Elphick writes:
> Some SQL92 functionality is missing from the BIT and VARBIT types.
>
> It should be possible to enter hexadecimal values as:
>
> B'[...]'[{...'[ X'[...]'[{...'[
> (Cannan and Otten: SQL - The Standard Handbook, p.38)
>
> but the hexadeximal form is not accepted.
This
Some SQL92 functionality is missing from the BIT and VARBIT types.
It should be possible to enter hexadecimal values as:
B'[...]'[{...'[...]'[{...'[http://www.lfix.co.uk/oliver
PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47 6B 7E 39 CC 56 E4 C1 47
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839
