I would tend to think that such a ping would be a special case, but I agree
with you to keep it as is:
Simply because overloading ping() with a complete eval'ed select statement
would be trivial. And the opposite isn't.
---
Henri Asseily
henri.tel
On Nov 5, 2012, at 4:35 PM, Charles Jardine c
On Oct 22, 2012, at 10:57 AM, Tim Bunce tim.bu...@pobox.com wrote:
On Sun, Oct 21, 2012 at 03:59:56PM +0200, Henri Asseily wrote:
Some more comments from the user (he should probably modernize his whole
stack but that's not the point here :)):
What perl and DBI versions?
He's using:
Perl
Hey guys, I just received a patch by a contributor on DBIx::HA and he said that
$dbh-swap_inner_handle causes deep C assertion errors in DBI.
Has anyone seen such a behavior?
Thanks.
---
Henri Asseily
henri.tel
))-sv_flags
0x0080)) ? Perl_mg_size(my_perl, (SV *) name_av) : ((XPVAV*)
(name_av)-sv_any)-xav_fill)+1 failed: file DBI.xs, line 2001
On Oct 21, 2012, at 3:12 PM, Henri Asseily he...@asseily.com wrote:
Hey guys, I just received a patch by a contributor on DBIx::HA and he said
that $dbh
Cool!
I had the same problem with SD cards, also switched to Debian Wheezy.
Any quick howto for installing DBI on it?
I was actually pretty impressed that one could run a decent X implementation on
it.
--
Henri Asseily
henri.tel
On Jul 2, 2012, at 9:01 PM, Tim Bunce wrote:
On Sun, Jul 01
On Jun 8, 2010, at 11:15 AM, Martin Evans wrote:
My belief was that the DBI docs were more en_EN than en_US. Given Tim
probably wrote most of it that is no surprise. I think the documentation
should be consistent and probably should be en_EN.
Isn't it instead EN_IE? :)
---
Henri Asseily
On 3/7/2010 11:11 PM, Stuart Johnston wrote:
Pass userid and a hash of userid and password.
The server uses the password to hash userid and password and tests for
equality.
That's something similar to what Amazon and others do.
The idea here is to add support for Basic HTTP Authentication,
On May 9, 2007, at 1:39 AM, Tim Bunce wrote:
On Tue, May 08, 2007 at 10:51:52PM +0100, David Cantrell wrote:
Tim Bunce wrote:
So, David, which version of Math::BigInt are you using?
According to the change notes for Math::BigInt 1.86 there should
be test failures for 1.85 on 32bit systems.
Similarly:
Mac OS X 10.4.8 Intel, GCC 4.0.1 (5363), Perl 5.8.8-nothread,
DBI-1.54-RC8, DBD-Mysql 1.2401, Mysql 5.0.19
DBI compiles, tests and installs fine.
In addition, simple scripts using the Gofer streams transport work.
H
On Feb 23, 2007, at 9:46 AM, Darren Duncan wrote:
As a
FWIW, RC7 compiles fine on my MacBook Pro 10.4.8 with default Perl.
Not surprising.
Anyway, I wanted to discuss the Gofer http transport, where it
relates to caching.
In order to add seamless integration of a caching engine (squid,
Redline accelerator, etc...), there are some issues.
Same 13taint.t test problem here that others have found.
Summary of my perl5 (revision 5 version 8 subversion 8) configuration:
Platform:
osname=darwin, osvers=8.6.1, archname=darwin-2level
uname='darwin henri-asseilys-computer.local 8.6.1 darwin kernel
version 8.6.1: tue mar 7
On Sep 18, 2006, at 6:18 PM, Tyler MacDonald wrote:
Dean Arnold [EMAIL PROTECTED] wrote:
Which brings me back to the notion of non-blocking requests.
Assuming
many/most client libs do support an async capability, and a OOB
cancel, then it should be possible to standardize the behavior
All make+tests OK on Intel Mac OS X 10.4.7, Perl 5.8.8 no threads.
One duplicate minor error on Intel Mac OS X 10.4.7, Perl 5.8.6 with
threads (default Perl on that OS):
In t/50dbm and t/zvpp_50dbm:
Argument 2.121_02 isn't numeric in subroutine entry at /System/
On May 4, 2006, at 5:39 PM, Patrick Galbraith wrote:
Henri,
Please see the latest 3.0006_1 branch via SVN (which will be
released to CPAN tonight). It has support for multiple result sets,
and even now includes examples of how to use them.
Kind regards,
Patrick
Hi Patrick, thanks
On a slightly different topic, I noticed yesterday that DBD::mysql
still doesn't have support for multiple statements (and result sets).
There's a patch out there that I applied and that seems to work, but
having also been using DBD::Sybase's multiple return set technique
extensively, I
On Fri, 22 Oct 2004, Tim Bunce wrote:
On Fri, Oct 22, 2004 at 09:00:23AM -0700, Tim Howell wrote:
1. Better support for dead connections. In our setup we have
applications running with Apache::DBI on linux that need to connect to a
ProxyServer running on Win2K. Currently, if the
Try to use RaiseError = 1, otherwise the DBI connect won't die and
the alarm won't be triggered. Or modify your connect statement to be:
DBI-connect(dbi:ODBC:GARDEL,Gardel,Gardel,{RaiseError = 0}) or
die DBI-errstr;
Also try to use the Sys::SigAction module by Lincoln Baxter and report
back.
Someone has logged a bug against DBD::Informix because it wasn't
cleaning up properly as a handle was destroyed. It turns out that the
statement-level active flag was not set. But, simply setting it on
means DBD::Informix runs foul of all sorts of issues during destroy.
Of course it's a bug
* A DBI handle is a reference to a tied hash and so has an 'outer'
hash that the handle reference points to and an 'inner' hash holding
the DBI data. By allowing the inner handle to be changed, for
example swapped with a different handle, many new behaviors become
possible. For example a database
On Aug 4, 2004, at 11:15 AM, John Siracusa wrote:
There are better ways to implement encapsulation and extensibility
than tied hashes. They're called objects and methods :) If ties
were
sufficient and just as good, then Perl 5 (and 6) would have no need
for
proper objects and methods.
and:
Hello,
included is a patch that adds the function set_internal_handle().
From the POD:
set_internal_handle
$rc = $sth-set_internal_handle( $sth2 );
Makes a statement handle internally point to the same
structures as
another statement handle. In essence,
I'm trying to do the following, and was wondering where I should look
to get a good handle on what's going on:
I have an $sth that's pointing to a dead server.
I have a new $sth2 that's pointing to a good server.
upon the user doing $sth-execute, I want to be able to get $sth
pointing to $sth2,
I need to write tests for the DBIx::HA module that overloads connect()
and execute(). Does anyone have a standard way of doing those,
considering that to do anything in DBI you need a datasource?
I read today on the list about DBD::Mock, which would be great if we all
had that. Should I simply
Sorry to get back to the old signal handling thing, but I was wondering
about what was said below, a couple of weeks ago:
my $alarm = 0;
eval {
local $SIG{ALRM} = sub { $alarm=1 };
alarm(3);
$dbh = DBI-connect( dbi:Oracle:$dbn, $usr, $pwd
,{
you to
choose which DB handles you want to subclass.
I can work around that using the connected() stuff you talked about, so
it's not a big deal, but I just thought it wouldn't be too logical to
have 2 different behaviors for what seemed (to me) to be the same
subclassing idea.
--
Henri
I may be missing something, but it seems that connect() is not being
overloaded when I subclass via the RootClass method.
Is that correct behavior or is my code broken?
Henri.
that
it exists? In any case, without sysusers, Sybase ASE won't even run.
---
Henri Asseily
[EMAIL PROTECTED]
Chief Technology Officer
BizRate.com
Que les inopérants laissent passer ceux qui font
Achille Talon
27 matches
Mail list logo