Re: pg_atoi() behavior change? Intentional?
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Adam Haberlach <adam@newsnipple.com>
Cc: pgsql-hackers@postgresql.org
Date: 2001-02-24T21:58:16Z
Lists: pgsql-hackers
Adam Haberlach <adam@newsnipple.com> writes:
> ... one of the engineers has been writing some queries that
> cast a text field to an int and take advantage of the
> fact that we used to turn text fields with no digits into 0,
> much as C's atoi function works.
> The new behavior is to throw a parse error, which causes
> all kinds of problem. Is this intentional?
What new behavior?
regression=# select ''::text::int4;
?column?
----------
0
(1 row)
7.0.* behaves the same as far as I can tell. I think this is actually
a bug, and it *should* throw an error ... but it doesn't.
regards, tom lane