Perl script

Hi All, This is my first email to the group and I hope that I landed in the correct place. Ok now coming to the problem. Can someone explain to me that what this script is doing. I want to know the meaning of all the lines in the script. $val = defined $val ? $val

RE: Problem with DBI

We are using, DBD::Sybase v1.02_01. The latest one seems to be v1.07. We could try the upgrade but it would be difficult to convince the production group unless we can say for sure that the latest version addresses this problem. cc:ing the author to see if he has something to offer. -Mohan -

RE: Problem with DBI

Thanks for looking into this. [EMAIL PROTECTED]:~$ perl -MDBIx::ContextualFetch -le 'print $DBIx::ContextualFetch::VERSION' 1.02 [EMAIL PROTECTED]:~$ -Original Message- From: Garrett, Philip (MAN-Corporate) [mailto:[EMAIL PROTECTED] Sent: Monday, July 24, 2006 7:37 PM To: Palisetti, Kris

Re: Query Timeout / Subclassing DBI

Without support from the driver and underlying database client library, timeouts using alarm signals may leave the driver and/or underlying database client library in an inconsistent state. Always disconnecting after a timeout may help, but isn't guaranteed. Tim. On Mon, Jul 24, 2006 at 04:05:52

Query Timeout / Subclassing DBI

I've been trying to find a reliable method for timing out queries that take too long. I only see a connect timeout in DBI but nothing for timing out a query. We can't set a timeout on our database either. I've attempted to use DBIx::DWIW without success. I'm also trying to subclass DBI and ove

ANNOUNCE: DBD:Oracle 1.18

DBD::Oracle 1.18 has been released. With this release DBD::Oracle finally implements Oracle's native Array Interface. You will see very dramatic increase in speed. For example; the time for a 2 million plus insert query dropped from well over an hour to less than 10 minutes when using execute_

RE: Problem with DBI

Palisetti, Krishna_Mohan wrote: > Hi, I'm seeing the following warning message from > DBIx::ContextualFetch intermittently. Use of uninitialized value > in null operation at > /usr/local/lib/perl5/site_perl/5.8.6/DBIx/ContextualFetch.pm line > 51. > > What does it mean?

RE: Problem with DBI

Palisetti, Krishna_Mohan wrote: >> >>> Hi, I'm seeing the following warning message from >>> DBIx::ContextualFetch intermittently. Use of uninitialized value in >>> null operation at >>> /usr/local/lib/perl5/site_perl/5.8.6/DBIx/ContextualFetch.pm line >>> 51. >>> >>> What does it mean? Sorry, I

RE: Problem with DBI

Palisetti, Krishna_Mohan wrote: > Hi, I'm seeing the following warning message from > DBIx::ContextualFetch intermittently. > Use of uninitialized value in null operation at > /usr/local/lib/perl5/site_perl/5.8.6/DBIx/ContextualFetch.pm line 51. > > What does it mean? Sorry, I am not in a position

Problem with DBI

Hi, I'm seeing the following warning message from DBIx::ContextualFetch intermittently. Use of uninitialized value in null operation at /usr/local/lib/perl5/site_perl/5.8.6/DBIx/ContextualFetch.pm line 51. What does it mean? Sorry, I am not in a position to provide a simple test case as I still c

Re: [DBD-ADO] bind_param broken in version 2.95?

jderrick wrote: > Hi Everybody, > > DBD-ADO version 2.95 appears to have a problem with the bind_param = > command when using the SQL type constants. The problem does not occur = > with version 2.94. See the dbi-users posting "Possible bug in DBD-ADO = > 2.94 bind_param" from September 24, 2005