-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 From: "Eric Simon" <esi...@theiqgroup.com> To: <dbi-users@perl.org> Subject: RE: DBD::Pg Implementation for cancel()? Date: 6:19 PM on Wednesday, August 04, 2010 X-Maillaunder-Av-Scan: YES:40743a065537e4cb1b81cbd0584176e7 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on incoming.maillaunder.com X-Spam-Level: X-Spam-Status: No, score=-10.5 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI, RDNS_NONE,SPF_PASS,TW_PG autolearn=ham version=3.2.5 X-Spam-PDF-Info: pdf=_PDFCOUNT_, pdfimg=_PDFIMGCOUNT_, ver=_PDFVERSION_, name=_PDFNAME_ X-Mailer: Microsoft Office Outlook 11 X-Mimeole: Produced By Microsoft MimeOLE V6.1.7600.16543 X-Old-Spam-Status: No, score=-2.5 required=3.3 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_RFC_BOGUSMX autolearn=no version=3.2.5
... > confusing. I meant to say that we wouldn't need to use pg_async if > if $sth->cancel() was implemented. To be more specific, we are doing > something very close to what the DBI docs show in their "Signal Handling > and Canceling Operations" section. Here is our abridged code that works > on DBD::Oracle: ... Ah, okay, now it makes sense with the alarm. I will look into if that will work with DBD::Pg but it may be a while, I'm very backed up at the moment. (Here's your chance, all you quiet potential dbdpg hackers on this list! :) > I'll see what I can do about narrowing down the destabilizing affect > that pg_async had in our test suite, although narrowing that down will > take quite some time (because I don't want to just shove a ton of code at > you). Yeah, small reproducible test cases are worth the wait. Send what you can, when you can. Better still, open a bug at rt.cpan.org if you think it's a problem on our end. Thanks. - -- Greg Sabino Mullane g...@turnstep.com End Point Corporation http://www.endpoint.com/ PGP Key: 0x14964AC8 201008051721 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAkxbK8cACgkQvJuQZxSWSsjhlQCeMc0RJMarcQRIEcdGJl1fjEyJ 9vkAoJ0Jm1xL55qJoegi3hFM75o/4Cnd =O9aR -----END PGP SIGNATURE-----
