Re: Using row_to_json with %ROWTYPE ?
| От | Adrian Klaver |
|---|---|
| Тема | Re: Using row_to_json with %ROWTYPE ? |
| Дата | |
| Msg-id | 54D50A4F.10104@aklaver.com обсуждение исходный текст |
| Ответ на | Re: Using row_to_json with %ROWTYPE ? (Tim Smith <randomdev4+postgres@gmail.com>) |
| Ответы |
Re: Using row_to_json with %ROWTYPE ?
|
| Список | 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.klaver@aklaver.com
В списке pgsql-general по дате отправления: