| From: | Luca Ferrari <fluca1978(at)infinito(dot)it> |
|---|---|
| To: | Susan Cassidy <susan(dot)cassidy(at)decisionsciencescorp(dot)com> |
| Cc: | Rob Sargent <robjsargent(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: another trigger problem |
| Date: | 2014-03-08 10:34:54 |
| Message-ID: | CAKoxK+4iHmCROAi3LODbU6ka-Supq1KzQak9hJQS-6QVc_6dFg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Mar 8, 2014 at 12:36 AM, Susan Cassidy
<susan(dot)cassidy(at)decisionsciencescorp(dot)com> wrote:
> You would think that postgres could have output a more helpful error
> message, though.
I believe that is the correct message: you were concatenating a null
string to something, and so nullifying the string you were using for
execute. In other words, it is not a wrong error message, or it could
not have been better since the instruction before the execute was
doing what you asked for. I believe in such cases it is better to
check against the query string and execute it only if valid.
Luca
| From | Date | Subject | |
|---|---|---|---|
| Next Message | matshyeq | 2014-03-09 13:43:35 | libpq - lack of support to set the fetch size |
| Previous Message | Susan Cassidy | 2014-03-07 23:36:43 | Re: another trigger problem |