The account is able to access the database given the same args in DBI->connect. I have written several CGI programs and lots of DBI programs, but this is the first script using DBI and CGI together, where either CGI works (using CGI.pm and instances created from CGI.pm), or DBI works via command line, but not in the same script using the CGI package:(
I'm uncertain if there are system env variables that should be set on the webserver. I'm sure its something simple that I'm overlooking, but I don't know what it is. At 02:41 PM 5/16/02 -0700, Stephen Keller wrote: >If by "fails to connect when using CGI.pm" you mean that the CGI.pm >version of the application fails when run from the web server, then >I'd look at the configuration of the user account that the web server >launches CGI programs as. It is likely that account is not configured >to access the database. In other words, its not the program but the >run time environment that is the problem. > >Stph > > > -----Original Message----- > > From: Jonathan Gines [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, May 16, 2002 1:59 PM > > To: [EMAIL PROTECTED] > > Cc: Jonathan Gines > > Subject: DBI works, but CGI + DBI bombs? > > > > > > Hello, > > > > I have 2 scripts below, where DBI is used in the former and > > DBI and CGI is > > used in the latter. The first script connects fine via > > command line, and > > the latter fails to connect, but using the same DBI code from the > > former. I'm puzzled and RTFM before deciding to send this > > email. Can > > anyone shed any light on why my script fails to connect when > > using CGI.pm?
