From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | "drum(dot)lucas(at)gmail(dot)com" <drum(dot)lucas(at)gmail(dot)com> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Fatal error when not numeric value - PostgreSQL 9.2 |
Date: | 2016-02-03 23:43:24 |
Message-ID: | CAKFQuwYyXaOE+17CuQRRCcAoKpaZJQzZm2ZFKLYAZcxix4GGSQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Feb 3, 2016 at 4:09 PM, drum(dot)lucas(at)gmail(dot)com <drum(dot)lucas(at)gmail(dot)com>
wrote:
>
>
> On 4 February 2016 at 12:03, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com
> > wrote:
>
>> On Wed, Feb 3, 2016 at 3:48 PM, drum(dot)lucas(at)gmail(dot)com <
>> drum(dot)lucas(at)gmail(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | John R Pierce | 2016-02-03 23:43:49 | Re: Fatal error when not numeric value - PostgreSQL 9.2 |
Previous Message | Andreas Joseph Krogh | 2016-02-03 23:32:58 | Re: Fatal error when not numeric value - PostgreSQL 9.2 |