| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Tim Smith <randomdev4+postgres(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 00:02:52 |
| Message-ID: | 54D404AC.2090204@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 02/05/2015 03:41 PM, Tim Smith wrote:
>> So either PostgreSQL is seeing a different view (in a different schema) or the function is confused in ways difficult to predict.
>
> Seriously ? You still want to continue calling it user-error ? There
> is no other view, there is no other schema , I am not hiding anything
> from you !
>
No, what we are trying to do is work the solution, not the problem. The
problem being you are getting a error, the solution being tracking down
where the error is coming from. If you start a problem report with
little or no information, you have to expect people are going to have to
ask a spectrum of questions to get at the information necessary to solve
the problem.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Uckun | 2015-02-06 02:13:18 | Partioning with overlapping and non overlapping constraints |
| Previous Message | Adrian Klaver | 2015-02-05 23:58:22 | Re: Using row_to_json with %ROWTYPE ? |