On Sat, Mar 8, 2014 at 12:36 AM, Susan Cassidy
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 ot
Bingo, this COPY file did not have the datetimeval, so I added a few lines
of code to convert it from the ctime-type entry that exists in the record.
You would think that postgres could have output a more helpful error
message, though.
Thanks a lot for the assist.
Susan
On Fri, Mar 7, 2014 at 3
On 03/07/2014 04:06 PM, Adrian Klaver wrote:
On 03/07/2014 02:48 PM, Susan Cassidy wrote:
I have another problem with a slightly different trigger. It's very
weird, because it is exactly the same as the first trigger, that now
works, except for the table name.
The error is:
ERROR: query stri
On 03/07/2014 02:48 PM, Susan Cassidy wrote:
I have another problem with a slightly different trigger. It's very
weird, because it is exactly the same as the first trigger, that now
works, except for the table name.
The error is:
ERROR: query string argument of EXECUTE is null
CONTEXT: PL/pg
I have another problem with a slightly different trigger. It's very weird,
because it is exactly the same as the first trigger, that now works, except
for the table name.
The error is:
ERROR: query string argument of EXECUTE is null
CONTEXT: PL/pgSQL function metric_int_insert_func() line 5 at
