SLao,
Let me try to clarify...the perl scripts try to load the Pg.pm module by
stating "use Pg". You say this should be a binary file? I found a few
copies of Pg.pm under .../perl/src or something like that, but it was ascii
text, I didn't dig too deep in to what it was doing.
I've found this http://www.edmund-mergl.de/export/DBD-Pg.zip from
symbolstone (http://dbi.symbolstone.org/cgi/moduledump?module=DBD::Pg)...
hopefully it's all I need.
If I install postgresql-7.1.2 from Jason and drop in the libpq.dll and
Pg.dll in my winnt/system32 should I be able to access my database from cgi
scripts with simply stating "use Pg"??
There seems to be something missing here...
-----Original Message-----
From: s0lao@netscape.net [mailto:s0lao@netscape.net]
Sent: Monday, June 11, 2001 12:33 AM
To: rsharma@bigstep.net
Cc: Jason.Tishler@dothill.com; pgsql-cygwin@postgresql.org
Subject: Re: [CYGWIN] RE: tourble migrating from
linux/Apache/postgresql/perl to win2000/IIS/postgresql/perl
[After the previous reply I've noticed your posts in pgsql-general]
To quote one of the answers there, Pg and DBD::Pg are completely different.
You weren't very clear what interface your scripts use. If you used DBI/DBD
postgres interface for your scripts, you don't need any perl tweak to your
PostgreSQL build. For a Pg module, you should either find a binary distro
which has it included (very hard -- as this should be a solver build -- like
in openoffice -- including the prebuild source tree) or to build it
yourself.
As a last comment, DBD::Pg would be a better bet, because its build is not
based on PostgreSQL source, but on a working binary distribution, with
libpq.dll and headers included. If you have problems with CPAN direct access
using Perl, there's always the ftp/http download alternative -- don't forget
the DBI module also.
SLao
__________________________________________________________________
Get your own FREE, personal Netscape Webmail account today at
http://webmail.netscape.com/
