Re: pg_atoi() behavior change? Intentional? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_atoi() behavior change? Intentional?
Date
Msg-id 15287.983051896@sss.pgh.pa.us
Whole thread Raw
In response to pg_atoi() behavior change? Intentional?  (Adam Haberlach <adam@newsnipple.com>)
List 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


pgsql-hackers by date:

Previous
From: "Timothy H. Keitt"
Date:
Subject: Re: offset and limit in update and subselect
Next
From: Tom Lane
Date:
Subject: Re: offset and limit in update and subselect