From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Tim Smith <randomdev4+postgres(at)gmail(dot)com>, David Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Using row_to_json with %ROWTYPE ? |
Date: | 2015-02-06 18:39:11 |
Message-ID: | 54D50A4F.10104@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 02/06/2015 10:26 AM, Tim Smith wrote:
> Re:So, you have an input parameter named "session_id" and a query with
> a column named "session_id" - this is the problem.
>
> Well, I'll re-try with a revised function, but surely the database
> could have come up with a more meaningful and insightful message than
> the coded incomprehensible error message it did ? I would say its
> not only user error, its developer error too for creating such
> confusing error messages !
Well actually you did yourself a disservice by including the EXCEPT
code. That changed the error message. Taking that code out and running
the failing function you get:
test-> validateSession('441122','10.11.12.13','abc',3600,3600);
ERROR: column reference "session_id" is ambiguous
LINE 2: session_id=session_id and session_ip=client_ip
^
DETAIL: It could refer to either a PL/pgSQL variable or a table column.
QUERY: select * from app_val_session_vw where
session_id=session_id and session_ip=client_ip
CONTEXT: PL/pgSQL function
validatesession(character,inet,character,bigint,bigint) line 7 at SQL
statement
I would say that is fairly specific:)
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | David Johnston | 2015-02-06 19:00:28 | Re: Using row_to_json with %ROWTYPE ? |
Previous Message | Tim Smith | 2015-02-06 18:28:54 | Re: Using row_to_json with %ROWTYPE ? |