Thanks to those who responded to me privately.
It seems the problem is caused by the connection timing out, after which it
automatically reconnects - but set names is not then done. (I am not using
Apache::DBI.)
Possible solutions:
- modify code to issue set names at the start of every request (
Hi all.
My project is built on Apache+mod_perl2 + PostgreSQL, so I use DBI::Pg
to connect to database and Apache::DBI for connection reuse. My DBI
connections are initialized at ChildInit phase. I examined Apache::DBI
sources and found that it creates one connection per dsn (am i right?)
b
I need to install Mason on Fedora 2 with Apache 2.
When I try to install Mason i receive:
* ERROR: Prerequisite Apache::Request isn't installed
I need to install the Apache2::Request (libapreq2) module for Apache
2, and when I try to install it:
build/version_check.pl failed: no version_string
On Fri, 2005-11-04 at 13:50 -0200, Victor Dias wrote:
> Im using:
[...]
> mod_perl-1.99_12-2.1
You need a newer mod_perl. The latest is 2.0.2.
- Perrin
On Fri, 2005-11-04 at 13:34 +, Daniel McBrearty wrote:
> It seems the problem is caused by the connection timing out, after which it
> automatically reconnects - but set names is not then done. (I am not using
> Apache::DBI.)
>
> Possible solutions:
> - modify code to issue set names at the s
On Fri, 2005-11-04 at 17:43 +0200, Taras Yurij Vasylovitch wrote:
> I've tried to write my own "db connections factory" but I found
> out that DBI connections cannot be shared between threads because they
> are objects.
This could be changed, but it would require some work. Hardly anyone
actually
But I can't help feeling I'm redesigning the wheel here - would I have the same
problem if I used Apache::DBI? Are there other easier ways to handle this?
IIRC, Apache::DBI just makes the connection persistant. It could still
time out and disconnect if a handle in the handle cache isn't used. A
I did the same install on Fedora 4 with mod_perl-2.0.1-1.fc4.
cd libapreq2-2.06-dev
perl Makefile.PL --with-apache2-apxs=/usr/sbin/apxs
make
receive:
/var/www/html/libapreq2-2.06-dev/glue/perl/xsbuilder/apreq_xs_postperl.h:21:34:
error: modperl_perl_unembed.h: Arquivo ou diretório não encontrado
You could also just make sure something like the following is in a my.cnf file (on my system it's /var/lib/mysql/my.cnf):
[perl]
default-character-set=utf8
And then when you connect, you'll need to specify two options to DBI to make DBD::mysql read from the option file:
DBI->connect( 'dbi:mysql:lo
On Fri, 2005-11-04 at 11:53 -0500, Philip M. Gollucci wrote:
> > But I can't help feeling I'm redesigning the wheel here - would I have the
> > same
> > problem if I used Apache::DBI? Are there other easier ways to handle this?
> IIRC, Apache::DBI just makes the connection persistant. It could st
On Friday 04 November 2005 12:14 pm, Perrin Harkins wrote:
> Apache::DBI checks the handle to make sure it is still connected before
> handing it back to you. If it has been disconnected, a new connection
> will be made.
Not always though. Something I've run into (but had problems tracking dow
On Fri, 2005-11-04 at 12:33 -0500, Malcolm J Harwood wrote:
> Not always though. Something I've run into (but had problems tracking down
> the
> cause) is that if the db server is rebooted between requests, Apache::DBI can
> think it's still got a valid handle and the db doesn't.
The check is o
On Thursday 03 November 2005 17:08, Geoffrey Young wrote:
> > so, please try the attached patch to Apache::Test. hopefully this fixes
> > things once and for all (without breaking more stuff :)
>
> Torsten, any luck with this?
yep, it works:
0 [EMAIL PROTECTED]:~/work/libapreq-1.33$ perl Makefil
Adam Worrall wrote:
I ended up hacking Apache::DBI to place the $conn into a @global, to
prevent DESTROY from kicking in. Naughty resource leaks ahoy.
The moral: it's surprisingly hard to get all this stuff working well !
Could maybe attach a diff ?
--
END
On Fri, 4 Nov 2005 9:33 am, Victor Dias wrote:
I did the same install on Fedora 4 with mod_perl-2.0.1-1.fc4.
Any help?
Try building 2.0.2 from source. The redhat / fedora packages have never
been completely error free in my experience. I've built 2.0.2 with
libapreq 2.0.6-dev several tim
Tyler MacDonald <[EMAIL PROTECTED]> wrote:
> > Can you try this on another system? That would tell you whether or not
> > there is truly anything wrong with the code, or if you should be looking
> > at reinstalling this system.
> I'm going to test this extensively this weekend if I get the t
16 matches
Mail list logo
