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

Re: pgsql 7.1: int4out() brokeness?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: James Troup <james(at)nocrew(dot)org>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: pgsql 7.1: int4out() brokeness?
Date: 2001-01-11 15:17:28
Message-ID: 11354.979226248@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
James Troup <james(at)nocrew(dot)org> writes:
>  | template1=# create table x (y int4); insert into x values (31); select y, int4out(y) from x;
>  | CREATE
>  | INSERT 34029 1
>  |  y  |  int4out
>  | ----+-----------
>  |  31 | 136420312
>  | (1 row)

The bug here is that the system allows you to invoke int4out at all.
It should not, because int4out doesn't return a value that can be
used for computation...

> int4out() seems to be broken which in turn breaks ODBC.

ODBC is broken for having ever used it in the first place.  This error
is repaired in the 7.0.3 and 7.1 releases of ODBC, btw.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: pgsql-bugsDate: 2001-01-11 16:39:10
Subject: JDBC PreparedStatement.setMaxRows() affects other objects intantiated from this class and it's parent class
Previous:From: Stanislas PinteDate: 2001-01-11 13:24:56
Subject: Bad Integer N

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