Sender: goran@hanna.kiruna.se
Message-ID: <35CDD8C3.8539ADA7@bildbasen.se>
Date: Sun, 09 Aug 1998 17:13:39 +0000
From: Goran Thyni <goran@bildbasen.se>
Organization: JMS Bildbasen
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Re: thread-safe libpq and DBD::Pg
References: <4095.902676804@sss.pgh.pa.us>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Tom Lane wrote:
> 
> Goran Thyni <goran@bildbasen.se> writes:
> > DBD::Pg dos indeed use PQconnectdb(),
> > but at least in my light test I get SEGV in $sth->fetch.
> > The problems are probably somewhere in DBDI or DBD::Pg or
> > somewhere in the interaction of the parts.
> 
> FWIW, I finally got around to installing Perl5 (5.004 pl4 to
> be specific), and so far the perl5 interface supplied with pgsql
> seems to work fine.  I only just now realized that what you
> are talking about is something different ... the code included
> in the distribution calls itself Pg not DBD::Pg.  What versions
> of everything are you using?

I am using perl 5.005_01 with threads support and DBI/DBD::Pg.
DBI/DBD is the "standard" RDBMS-interface for perl available
from CPAN.

> > I am looking into how much work a "pure Perl" interface
> > should amount to. Using native perl IO and pgsql-fe/be-protocol
> > should make "pgsql-clienting" even more portable over platforms.
> 
> Of course, it will also mean that you have to maintain that code
> every time we change the fe/be protocol ... there is a change
> upcoming for 6.4.

I have done some experimenting:
The easy parts are done (if not cleanly), connect/exec/close.
The hairy parts is to extract row descriptors and tuples
from select/fetch statements.

I am working against the current CVS tree, are there more
protocol changes in the pipeline?

	regards,
		Göran.