From e863951a59cc04df370bc6dd06b42bff9b211965 Mon Sep 17 00:00:00 2001 From: Alvaro Herrera Date: Thu, 10 Apr 2008 15:16:46 +0000 Subject: [PATCH] Remove mention of DBD::PgSPI, which is unmaintained and generally unnecessary. --- doc/src/sgml/plperl.sgml | 18 +++--------------- 1 file changed, 3 insertions(+), 15 deletions(-) diff --git a/doc/src/sgml/plperl.sgml b/doc/src/sgml/plperl.sgml index ce217dfa33..dfb15b3bd1 100644 --- a/doc/src/sgml/plperl.sgml +++ b/doc/src/sgml/plperl.sgml @@ -1,4 +1,4 @@ - + PL/Perl - Perl Procedural Language @@ -309,20 +309,7 @@ BEGIN { strict->import(); } Access to the database itself from your Perl function can be done - via the function spi_exec_query described - below, or via an experimental module - - DBD::PgSPI - (also available at - CPAN mirror sites). This module makes available a - DBI-compliant database-handle named - $pg_dbh that can be used to perform queries with - normal DBI - syntax.DBI - - - - PL/Perl provides additional Perl commands: + via the following functions: @@ -412,6 +399,7 @@ $$ LANGUAGE plperl; SELECT * FROM test_munge(); + spi_query and spi_fetchrow work together as a pair for row sets which might be large, or for cases -- 2.40.0