Skip site navigation (1) Skip section navigation (2)

Re: No support for int8 sized binary/hex literals

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: <9sch1(at)txl(dot)com>, <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: No support for int8 sized binary/hex literals
Date: 2001-02-18 00:24:33
Message-ID: Pine.LNX.4.30.0102180122450.933-100000@peter.localdomain (view raw or flat)
Thread:
Lists: pgsql-bugs
>      The B'111...' and X'1F...' SQL92 literal syntax is limited to
> int4 sized literals.  Any attempt to use an int8 sized literal
> > int4/32-bit word size fails.  This makes it impossible to specify
> many int8 sized bit patterns as column default values.  It makes
> it impossible to even insert > 32bit sized binary/hex values.
> Failure to support SQL92 literals for int8 types dramatically
> limits and/or complicates the use of int8 bit/nibble/byte composed
> values (bit fields, nibble/byte patterns, etc.)

The B'111...' and X'1F...' SQL92 literal syntax is not for integer types
at all.  The upcoming version 7.1 will implement the BIT and BIT VARYING
types, which have virtually unlimited length.

-- 
Peter Eisentraut      peter_e(at)gmx(dot)net       http://yi.org/peter-e/


In response to

pgsql-bugs by date

Next:From: Chowalit TinnagonsuboutDate: 2001-02-19 04:42:57
Subject: Error of dump OID datatype
Previous:From: pgsql-bugsDate: 2001-02-17 23:22:36
Subject: No support for int8 sized binary/hex literals

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group