Use the great Sys::SigAction by Lincoln Baxter.
It has never failed me.
Take a look at DBIx::HA for sample usage.
On Sep 16, 2006, at 2:27 AM, CAMPBELL, BRIAN D (BRIAN) wrote:
I've done something similar to what you did...
It went something like this...
- Run query in a separate thread.
-
On Sat, 16 Sep 2006, Henri Asseily wrote:
Use the great Sys::SigAction by Lincoln Baxter.
That's just a wrapper around POSIX sigaction(), right? As I
understand it that's equivalent to the old unsafe signals in Perl
before 5.8. I'd rather avoid that if it all possible!
-sam
On Sep 16, 2006, at 8:58 PM, Sam Tregar wrote:
On Sat, 16 Sep 2006, Henri Asseily wrote:
Use the great Sys::SigAction by Lincoln Baxter.
That's just a wrapper around POSIX sigaction(), right? As I
understand it that's equivalent to the old unsafe signals in Perl
before 5.8. I'd rather
On Sep 17, 2006, at 12:05 AM, Henri Asseily wrote:
On Sep 16, 2006, at 8:58 PM, Sam Tregar wrote:
On Sat, 16 Sep 2006, Henri Asseily wrote:
Use the great Sys::SigAction by Lincoln Baxter.
That's just a wrapper around POSIX sigaction(), right? As I
understand it that's equivalent to the
On Sun, 17 Sep 2006, Henri Asseily wrote:
You've got a catch-22: If you ALWAYS want the signal to fire on time, then
you should expect unsafe signals.
Just clean up after yourself.
It's hard to clean up after the kind of problems unsafe signals can
cause. For example, imagine the DB client
Hi, I'm no Perl expert, but I also would not consider myself a newbie. I
seem to have a memory leak issue with the DBI module (1.52) on Windows
connecting to Oracle (10gR2).
For reasons I won't go into at this time, I need to have a continuous loop
that will connect to many Oracle instances.
I'm not really qualified to comment on DBD::mysql, but...
I just saw your note on mysql internals, and suspect your
request there is unlikely to be given serious consideration.
I think your best bet might be to work with the DBD::mysql maintainers
to implement some driver-specific nonblocking
On Sat, 16 Sep 2006, Dean Arnold wrote:
I just saw your note on mysql internals, and suspect your
request there is unlikely to be given serious consideration.
Always a possibility. Maybe they'd be more interested in a patch.
(For the curious, I wrote a message to the MySQL internals
Hi,
I'm using DBI for a proof of concept project that I thought should be rather
quick.
But I see DBI is rather quirky to the novice :)
I'm on FreeBSD 5.4 using perl 5.8.8 and DBI 1.52
Using the connection string in the Subject line, I created a table as follows:
Create Table Folders
Lane wrote:
my $dbh = DBI-connect('dbi:DBM:mldbm=Storable;f_dir=/foo/bar');
$dbh-{RaiseError} = 1;
I can't reproduce your problem. Please run the following script and
send the output back to the list.
#!/usr/bin/perl -w
use strict;
use DBI;
my $dbh =
On Saturday 16 September 2006 20:23, Jeff Zucker wrote:
Lane wrote:
my $dbh = DBI-connect('dbi:DBM:mldbm=Storable;f_dir=/foo/bar');
$dbh-{RaiseError} = 1;
I can't reproduce your problem. Please run the following script and
send the output back to the list.
#!/usr/bin/perl -w
On Saturday 16 September 2006 20:23, Jeff Zucker wrote:
Lane wrote:
my $dbh = DBI-connect('dbi:DBM:mldbm=Storable;f_dir=/foo/bar');
$dbh-{RaiseError} = 1;
I can't reproduce your problem. Please run the following script and
send the output back to the list.
#!/usr/bin/perl -w
Changes
- First release!
Description
This module provides a safe method of timing out DBI requests. An
unsafe method is described in the DBI docs:
http://search.cpan.org/~timb/DBI/DBI.pm#Signal_Handling_and_Canceling_Operations
The problem with using POSIX sigaction()
13 matches
Mail list logo
