Date: Thu, 10 Apr 2008 09:16:02 -0400
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Martin Edlman <edlman@fortech.cz>
Cc: pgsql-sql@postgresql.org, Pg Hackers <pgsql-hackers@postgresql.org>,
	Pg Docs <pgsql-docs@postgresql.org>, andrew@dunslane.net
Subject: Re: [SQL] pl/PgSQL, variable names in NEW
Message-ID: <20080410131602.GF4697@alvh.no-ip.org>
References: <47FA034B.7090201@fortech.cz>
	<162867790804070511y7266c911w370db97a78c3c519@mail.gmail.com>
	<47FB51C7.6090509@fortech.cz>
	<20080408132157.GF5290@alvh.no-ip.org>
	<47FDFB2E.3060503@fortech.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <47FDFB2E.3060503@fortech.cz>
User-Agent: Mutt/1.5.17+20080114 (2008-01-14)

Martin Edlman wrote:

> |> I don't want to rewrite whole trigger to plPerl as I would have to use
> |> DBD-PgSPI.
> |
> | Huh?  Certainly not -- there are functions in PL/Perl for this.  See
> | spi_exec_query in
> | http://www.postgresql.org/docs/8.3/static/plperl-database.html
>
> Oh, I see. I have read the doc "...can be done via the function
> spi_exec_query described below, or via an experimental module
> DBD::PgSPI...", but missed the "OR" and thought that DBD::PgSPI is
> mandatory.

Yeah, that's a bit confusing.  I don't know why we have a mention of
DBD::PgSPI on the plperl manual at all.  Is there anything it can do
that can't be done with PL/Perl native calls?

Question for plperl hackers:  Should we remove the mention of DBD::PgSPI
from the PL/Perl manual?

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support