On Wed, 20 Mar 2002, Stas Bekman wrote:
Doug Silver wrote:
I don't know if this is a PostgreSQL oddity, but in the startup.pl file, I
can have the entry like so and it seems to start fine:
Apache::DBI-connect_on_init
(dbi:pg(PrintError=1,AutoCommit=0):, , )
or die Cannot
I don't know if this is a PostgreSQL oddity, but in the startup.pl file, I
can have the entry like so and it seems to start fine:
Apache::DBI-connect_on_init
(dbi:pg(PrintError=1,AutoCommit=0):, , )
or die Cannot connect to database: $DBI::errstr;
The error log shows a couple of
Doug Silver wrote:
I don't know if this is a PostgreSQL oddity, but in the startup.pl file, I
can have the entry like so and it seems to start fine:
Apache::DBI-connect_on_init
(dbi:pg(PrintError=1,AutoCommit=0):, , )
or die Cannot connect to database: $DBI::errstr;
The error log
I can't seem to get Apache::DBI to start up properly.
Here's my startup.pl:
#!/usr/bin/perl -w
use strict;
use Apache ();
use Apache::Status ();
use Apache::DBI (); # This *must* come before all other DBI modules!
use Apache::Registry;
use CGI ();
CGI-compile(':all');
use
I've seen similar behavior with DBD::Sybase; if your SYBASE env variable
is not set or points at an invalid directory Apache starts up but begins
segging every child process over and over again.
I'm not familiar with Postgres but this might point you in the right
direction.
On Thu, 2002-03-14
Ok, I found it, but this has got to be some kind of bug.
This works:
Apache::DBI-connect_on_init(dbi:pg:demo,demo);
This doesn't:
Apache::DBI-connect_on_init(dbi:Pg:demo,demo);
That's right, putting 'dbi:pg' in lowercase made it work. I looked through
some old newsgroup stuff and saw someone
Weird, although I bet if you had straced the apache processes you would
have seen the File not found.
For some reason I recall DBD Drivers being case sensitive.
On Thu, 2002-03-14 at 20:06, Doug Silver wrote:
Ok, I found it, but this has got to be some kind of bug.
This works:
