From: | elein <elein(at)sbcglobal(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David U(dot)" <davidu(at)everydns(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: String functions like split() and join() in plpgsql |
Date: | 2003-01-16 01:31:00 |
Message-ID: | 200301160131.h0G1VfUa163094@pimout2-ext.prodigy.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Or try plpython. You can write triggers in plpython directly.
--elein
On Monday 13 January 2003 18:39, Tom Lane wrote:
> "David U." <davidu(at)everydns(dot)net> writes:
> > I'm writing a trigger to change the third field in a varchar record.
> > (it's an SOA field from DNS) and I can do it in plperl but since it needs
> > to be a trigger I have to do it in plpgsql (or other right?).
>
> There's nothing to stop you from calling a plperl function from a
> plpgsql trigger function. If you've got complicated string-mashing
> requirements, I'd certainly recommend coding them in plperl (or pltcl).
>
> Someday someone should get around to implementing trigger support for
> plperl, but in the meantime a two-layer approach seems like your answer.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
--
----------------------------------------------------------------------------------------
elein(at)varlena(dot)com Database Consulting www.varlena.com
I have always depended on the [QA] of strangers.
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Clift | 2003-01-16 01:47:47 | PostgreSQL and Data warehousing question |
Previous Message | Tom Lane | 2003-01-16 00:40:22 | Re: [GENERAL] gmake check error on HPUX |