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 CAKFQuwbOGc3QAbd8bGRfMK9q77oXAwf9k0O3W48G91=QaAyDcQ@mail.gmail.com
Whole thread Raw
In response to Fatal error when not numeric value - PostgreSQL 9.2  ("drum.lucas@gmail.com" <drum.lucas@gmail.com>)
Responses 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 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.

Question: How could I do something that would allow _iid to be more than just an INT?

WITH
    in_rows AS (
      SELECT
        CAST(customer_id AS BIGINT),
        csv_data,
        freshbooks_id,
        myob_id,
        ppy_id,
        qb_id,
        xero_id,
        _iid
      FROM
        (
          VALUES
('3905', E'\x1A', E'\x1A', 'c59894c-142b6', E'\x1A', E'\x1A', E'\x1A', '44'),
('39107', E'\x1A', E'\x1A', '6260-2ba1', E'\x1A', E'\x1A', E'\x1A', '65e-0f0d-49b4-9ac1-a8752ba1'),
Thank you
Lucas

​You have a fatal error because the query you provided is malformed.  Send something that works, and provokes the relevant error, and we might be able to help.

David J.

pgsql-general by date:

Previous
From: "drum.lucas@gmail.com"
Date:
Subject: Fatal error when not numeric value - PostgreSQL 9.2
Next
From: "drum.lucas@gmail.com"
Date:
Subject: Re: Fatal error when not numeric value - PostgreSQL 9.2