Hi Peter,
I’ve been using Perl CGI to connect to a Postgreql 7.3.4 database with Perl 5.8.0, although on an XP machine using Apache2. I had trouble installing the DBD-Pg module and ended up using the DBD-PgPP. Which works for the most part, you might give that a try. There are a few bugs in it, but someone has posted a bugfixed version if your interested in trying it (http://int.mw-itcon.de/PgPP.pm). I never did try and figure out why Pg didn’t work.
Good luck,
Jennifer
-----Original Message-----
From: Peter Lom [mailto:peterlom@bigpond.net.au]
Sent: Thursday, September 25, 2003 6:04 AM
To: pgsql-cygwin@postgresql.org
Subject: [CYGWIN] advice please
please please advice to solve a frustration.
Where to post the following question (I asked on other forums - no answer; people did not respond either) ?
I am attempting to create and exerimental environment under W2000 which includes
Perl 5.8.0 - MSWin32-x86-multi-thread, binary build 806
I installed PostgreSQL under the latest cygwin and created a test database, inserted some data into it - no problems.
Note: announced Native Win PostgreSQL 7.4 will not be released (only 8.0 in 2004)
The problem is to connect from CGI into this database using Perl with DBI e.g with DBD-Pg ( the module is Edmund Mergl's and asks for Perl build 805 - he doid not respond to my email).
I cannot link this module into Perl (note: I failed also with the cygwin Perl).
This email is from the Scottish Crop Research Institute, but the views expressed by the sender are not necessarily the views of SCRI and its subsidiaries. This email and any files transmitted with it are confidential to the intended recipient at the e-mail address to which it has been addressed. It may not be disclosed or used by any other than that addressee.
If you are not the intended recipient you are requested to preserve this confidentiality and you must not use, disclose, copy, print or rely on this e-mail in any way. Please notify mail@scri.sari.ac.uk quoting the name of the sender and delete the email from your system.
Although SCRI has taken reasonable precautions to ensure no viruses are present in this email, neither the Institute nor the sender accepts any responsibility for any viruses, and it is your responsibility to scan the email and the attachments (if any).