Re: how to call a TCL function from within a plpgsql trigger?

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Ian Harding <iharding(at)tpchd(dot)org>
Cc: Josué Maldonado <josue(at)lamundial(dot)hn>, pgsql-general(at)postgresql(dot)org
Subject: Re: how to call a TCL function from within a plpgsql trigger?
Date: 2003-09-04 19:24:21
Message-ID: 3F579165.6000106@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ian Harding wrote:

> A tcl function is just like any other, you can call it from within a
> plpgsql trigger function in the same way you would call a built-in, or
> any other function. Having said that, I am not sure what the exact
> plpgsql options are besides "SELECT myfunction(' 'foo' ', ' 'bar' ')
> ...." and don't know syntax for storing the returned value in a
> variable. I'm a one-trick pony.

What about

plpgsql_variable := tcl_or_any_other_function();

You can also pass some arguments, but that doesn't count as another
trick, it's just a modification to an already seen one.

Jan

>
> Josué Maldonado wrote:
>
>> Hi list,
>>
>> That's the question, anyone knows a way to do that?
>>
>> Thanks in advance,
>>
>> Josue Maldonado.
>>
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 9: the planner will ignore your desire to choose an index scan if
>> your
>> joining column's datatypes do not match
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jonathan Bartlett 2003-09-04 19:26:28 Re: Replaceing records
Previous Message Alvaro Herrera Munoz 2003-09-04 19:11:19 Re: [HACKERS] tablelevel and rowlevel locks