Re: Shared Objects (Dynamic loading) - Mailing list pgsql-general

From Michael Fuhr
Subject Re: Shared Objects (Dynamic loading)
Date
Msg-id 20060824202830.GA31900@winnie.fuhr.org
Whole thread Raw
In response to Re: Shared Objects (Dynamic loading)  ("Jasbinder Bali" <jsbali@gmail.com>)
Responses Re: Shared Objects (Dynamic loading)  ("Jasbinder Bali" <jsbali@gmail.com>)
List pgsql-general
On Thu, Aug 24, 2006 at 03:46:00PM -0400, Jasbinder Bali wrote:
> The way we use ECPG for the database related activites while working with
> C, what do i need to look up if i'm using perl.

For information about writing server-side Perl functions see the
PL/Perl documentation (adjust the link if you're using a version
other than 8.1):

http://www.postgresql.org/docs/8.1/interactive/plperl.html

If the function needs to execute SQL statements in the same backend
in which it's running then see the "Database Access from PL/Perl"
section.  If it needs to connect to a different database then you
could use the DBI module.

> As alot of people have pointed out that perl is the best language to use
> while dealing with email parsing.

"Best" is a matter of opinion; others might prefer Ruby, Python,
or something else.  Perl is good at text handling, it has a large
number of third-party modules (CPAN), and there's a lot of material
written about it so it's a popular choice.

> We have the perl code ready to parse the email.
> Just wondering what would be the best method to deal with database
> (postgresql) calls from the perl code.

See the aforementioned PL/Perl documentation.  You could also use
PL/Perl just for parsing and use PL/pgSQL for working with the
database.

--
Michael Fuhr

pgsql-general by date:

Previous
From: marcelo Cortez
Date:
Subject: lock table problem
Next
From: Frank Cohen
Date:
Subject: Re: XPath and XML support