-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
Sorry for the late response, but I'm quite busy and I wanted
to test this before replying...
Bruce Momjian schrieb:
> Tom Lane wrote:
>> Andreas Haumer <[EMAIL PROTECTED]> writes:
>>> How can I get the functionality
nt interactive command. This makes a difference when
the triggering query occurred within a function: the trigger is
invoked before the function proceeds to its next operation."
So, the change seemingly is intentional, but it leads to the
problem I described above.
Now, what can I do t
at this is of course very platform specific. On Oracle
you could use rownum, for example.
I don't have a more portable solution on hand right now.
HTH
- - andreas
- --
Andreas Haumer | mailto:[EMAIL PROTECTED]
*x Software + Systeme | http://www.xss.co.at/
Karm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
I have solved the problem!
Tom Lane wrote:
> Andreas Haumer <[EMAIL PROTECTED]> writes:
>
>>I just can't figure out where and how many quotation marks
>>I have to place in my function.
>
>
> It's messy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
Many thanks for your reply!
Tom Lane wrote:
> Andreas Haumer <[EMAIL PROTECTED]> writes:
>
>>It seems I would have to use EXECUTE on dynamically constructed
>>PL/PGSQL statements in order to have my trigger function re
llions of quotation marks in my dynamically
generated EXECUTE statement but I can't seem to get the statements
right :-(
So, IMHO all this can be reduced to the following question:
how can I use trigger function arguments inside of PL/PGSQL
trigger functions to write generalized SELECT state