| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tim Smith <randomdev4+postgres(at)gmail(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>, david(dot)g(dot)johnston(at)gmail(dot)com |
| Subject: | Re: Using row_to_json with %ROWTYPE ? |
| Date: | 2015-02-05 23:50:03 |
| Message-ID: | 1455.1423180203@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tim Smith <randomdev4+postgres(at)gmail(dot)com> writes:
> Yes, well PostgreSQL is being incredibly unhelpful in that respect, it
> says "(SQLSTATE: 42702 - SQLERRM: column reference "session_id" is
> ambiguous)" ... but that is an utter lie. There is only one column
> called session_id in my view (in both the view output and the
> underlying view query, there is only one reference to "session_id")
A reasonably likely bet is that the ambiguity is between a column name
exposed by the query and some variable of the same name declared within
the plpgsql function. But, as has been mentioned repeatedly, you've not
shown us enough detail to permit a positive diagnosis.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2015-02-05 23:58:22 | Re: Using row_to_json with %ROWTYPE ? |
| Previous Message | Tim Smith | 2015-02-05 23:43:03 | Re: Using row_to_json with %ROWTYPE ? |