From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | yclu(at)ecompliance(dot)net, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Bug #625: bytea data type problem/bug |
Date: | 2002-03-27 21:27:56 |
Message-ID: | 3CA2395C.7080403@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
pgsql-bugs(at)postgresql(dot)org wrote:
> Eric Lu (yclu(at)ecompliance(dot)net) reports a bug with a severity of 4
> The lower the number the more severe it is.
>
> Short Description
> bytea data type problem/bug
>
> Long Description
> Hi,
>
> It happens when I was trying to test the avalaibility of the new binary data type <bytea> comes with ver 7.2.
> As I read from the document, <bytea> will take data from '\\000' (0d)to '\\377' (255d). Although it saves data more than one byte, it looks odd to me that the first digit of the binary data could never be greater than '3'.
> Is it the way it should be?
> Thanks!
>
> Eric Lu
>
The escaped values must be three-digits, octal (i.e. base 8) numbers,
and in the range of 0 - 255 in decimal (base 10). Only the digits 0 - 7
are defined, and 377 octal == 255 decimal is the maximum allowable
value. Anything starting with 4 - 7 (e.g. 400 octal == 256 decimal) is
too big.
Joe
From | Date | Subject | |
---|---|---|---|
Next Message | pgsql-bugs | 2002-03-28 00:17:20 | Bug #626: Query with View not returning proper results |
Previous Message | pgsql-bugs | 2002-03-27 20:25:56 | Bug #625: bytea data type problem/bug |