Re: Fatal error when not numeric value - PostgreSQL 9.2 - Mailing list pgsql-general

From David G. Johnston
Subject Re: Fatal error when not numeric value - PostgreSQL 9.2
Date
Msg-id CAKFQuwYyXaOE+17CuQRRCcAoKpaZJQzZm2ZFKLYAZcxix4GGSQ@mail.gmail.com
Whole thread Raw
In response to Re: Fatal error when not numeric value - PostgreSQL 9.2  ("drum.lucas@gmail.com" <drum.lucas@gmail.com>)
List pgsql-general
On Wed, Feb 3, 2016 at 4:09 PM, drum.lucas@gmail.com <drum.lucas@gmail.com> wrote:


On 4 February 2016 at 12:03, David G. Johnston <david.g.johnston@gmail.com> wrote:
On Wed, Feb 3, 2016 at 3:48 PM, drum.lucas@gmail.com <drum.lucas@gmail.com> wrote:

Hi all,

Below is an example of the auto-generated update query, with client-supplied keys (_iid). There's a fatal error when _iid is not numeric. However; this should accept any value.

​The supplied query is not an update query and as far as I can tell nothing in it compels the system to try and convert your text _iid from the CTE to an integer.  So, you are still not showing us the whole picture.​  But, if whatever target relation you are trying to insert/update this record against defines _iid as integer then you need to change it to be defined as text.

David J.


pgsql-general by date:

Previous
From: Andreas Joseph Krogh
Date:
Subject: Re: Fatal error when not numeric value - PostgreSQL 9.2
Next
From: John R Pierce
Date:
Subject: Re: Fatal error when not numeric value - PostgreSQL 9.2