We use a server-setup with a mod_perl enabled backend server. The server
only runs mod_perl and mySQL for about 5 virtual hosts.
Our problem is that a syntax-error in a program used on only one virutal
host, causes an internal server error across all virtual hosts.
I suspect it's not possible
Hi there,
On Wed, 2 May 2001, Tommy Davis wrote:
We use a server-setup with a mod_perl enabled backend server. The server
only runs mod_perl and mySQL for about 5 virtual hosts.
Our problem is that a syntax-error in a program used on only one virutal
host, causes an internal server
* Tommy Davis ([EMAIL PROTECTED]) [010502 04:11]:
We use a server-setup with a mod_perl enabled backend server. The server
only runs mod_perl and mySQL for about 5 virtual hosts.
...
Another problem is that the solutions uses diffferent databases. That
means we end up with 5 ttimes as
Chris Winters ([EMAIL PROTECTED]) said something to this effect on 05/02/2001:
package MyServer::DB;
use strict;
use DBI;
my $DB_USER = '';
my $DB_PASS = '';
sub connect {
my ( $class, $dbname ) = @_;
my $dbh = DBI-connect( 'DBI:mysql:mysql', $DB_USER, $DB_PASS,
G.W. Haywood wrote:
[EMAIL PROTECTED]">
We use a server-setup with a mod_perl enabled backend server. The server only runs mod_perl and mySQL for about 5 virtual hosts.Our problem is that a syntax-error in a program used on only one virutal host, causes an "internal server error" across all
Chris Winters wrote:
[EMAIL PROTECTED]">* Tommy Davis ([EMAIL PROTECTED]) [010502 04:11]:
We use a server-setup with a mod_perl enabled backend server. The server only runs mod_perl and mySQL for about 5 virtual hostsAnother problem is that the solutions uses diffferent databases. That means
Chris Winters [EMAIL PROTECTED] wrote:
I'm not sure how you create your database handles (in a central
location then passed around, or in each handler as you need it), but
in MySQL (as with other databases) you can execute a 'use dbname' to
start using a different database.
FWIW, MySQL is
