Re: [SQL] dynmic column names inside trigger?

2007-11-23 Thread Michael Glaesemann
On Nov 23, 2007, at 12:06 , Louis-David Mitterrand wrote: On Wed, Nov 21, 2007 at 09:14:14AM +0100, Bart Degryse wrote: LANGUAGE plpgsql VOLATILE RETURNS NULL ON NULL INPUT; Hi, I was curious as to why you created this function with a prototype of func(intext IN text, outtext OUT t

Re: [SQL] dynmic column names inside trigger?

2007-11-23 Thread Louis-David Mitterrand
On Wed, Nov 21, 2007 at 09:14:14AM +0100, Bart Degryse wrote: > I would do something like this (not tested, but conceptually working): > > CREATE or replace FUNCTION sanitize_text(webtext IN text, cleantext OUT text) > AS > $body$ > BEGIN > cleantext = translate(webtext, E'\x92\x96', '''-'); > c

Re: [SQL] Aleatory exception - found cause

2007-11-23 Thread Sabin Coanda
Hi, Finally I found the cause of the problem. I found deeper inside my calls, a function which has to return an integer column from a RECORD rec variable. The rec is assigned with the following statement: EXECUTE 'SELECT pk AS "PK" FROM "my_table" WHERE my_where_clause' INTO rec. When

Re: [SQL] PL argument max size, and doubt

2007-11-23 Thread Martin Marques
Tom Lane escribió: Martin Marques <[EMAIL PROTECTED]> writes: Tom Lane escribió: Martin Marques <[EMAIL PROTECTED]> writes: I have always heard that modification queries should be EXECUTED in PL. AFAICR. Run far away from whatever source gave you that advice... Sorry, it was with DDL comma

Re: [SQL] Aleatory exception

2007-11-23 Thread Sabin Coanda
Sorry for the previous incomplete text. I add the followings: For instance I got that exception for the following statement string: '"my_function"( NULL, ''TEXT1'', NULL::int4, NULL::int4, 5413, , TIMESTAMP WITH TIME ZONE ''2007-11-23 10:08:29.904+02'', 19255, 0 )' What is wrong with this

[SQL] Aleatory exception

2007-11-23 Thread Sabin Coanda
Hi there, I have a custom function where I execute a dynamic statement. I trap the exceptions, and sometimes I got the following error data: SQLSTATE = 22P02, SQLERRM = invalid input syntax for integer: "NULL::int4" For instance I got this for the following statement string: Please