RE: Surprising DBD::Oracle error raised

2014-02-05 Thread John Scoles
way is to fetch is in a loop with 'while'. As there is no way to tell how many records will be in your set before you do you SQL unless you tell the SQL to return only x rows. Cheers John Date: Tue, 4 Feb 2014 13:36:50 -0600 Subject: Surprising DBD::Oracle error raised From: davidni

Re: Surprising DBD::Oracle error raised

2014-02-05 Thread Martin J. Evans
On 04/02/14 19:36, David Nicol wrote: $price_sth-execute; my ($o_file_price) = $price_sth-fetchrow_array(); if ($price_sth-fetch) { $this-log_error('ERROR: scalar select returned second row at %s line %d', __FILE__, __LINE__); } I expected the fetch to return

RE: Surprising DBD::Oracle error raised

2014-02-05 Thread John Scoles
, 5 Feb 2014 13:25:03 + From: martin.ev...@easysoft.com To: davidni...@gmail.com; dbi-users@perl.org Subject: Re: Surprising DBD::Oracle error raised On 04/02/14 19:36, David Nicol wrote: $price_sth-execute; my ($o_file_price) = $price_sth-fetchrow_array(); if ($price_sth-fetch

Re: Surprising DBD::Oracle error raised

2014-02-05 Thread Martin J. Evans
: Surprising DBD::Oracle error raised On 04/02/14 19:36, David Nicol wrote: $price_sth-execute; my ($o_file_price) = $price_sth-fetchrow_array(); if ($price_sth-fetch) { $this-log_error('ERROR: scalar select returned second row at %s line %d', __FILE__, __LINE__); } I

Re: Surprising DBD::Oracle error raised

2014-02-05 Thread John D Groenveld
In message cafwsco-tqp5yycpptawzqkkyhz6qjs3d_g+yv5r9x9apdbm...@mail.gmail.com , David Nicol writes: the error message claimed I hadn't executed the statement. Where is your DBI_TRACE? I can't reproduce. John groenv...@acm.org use strict; use DBI; my $dbh = DBI-connect( dbi:Oracle:, scott,

Re: Surprising DBD::Oracle error raised

2014-02-05 Thread David Nicol
On Wed, Feb 5, 2014 at 7:25 AM, Martin J. Evans martin.ev...@easysoft.com wrote: That is indeed interesting. When I run the following with DBD::ODBC to MS SQL Server: use strict; use warnings; use DBI; my $h = DBI-connect(); eval { $h-do(q/drop table mje/); }; $h-do(q/create

Re: Surprising DBD::Oracle error raised

2014-02-05 Thread Martin J. Evans
On 05/02/14 14:08, David Nicol wrote: On Wed, Feb 5, 2014 at 7:25 AM, Martin J. Evans martin.ev...@easysoft.com wrote: That is indeed interesting. When I run the following with DBD::ODBC to MS SQL Server: use strict; use warnings; use DBI; my $h = DBI-connect(); eval { $h-do(q/drop

Surprising DBD::Oracle error raised

2014-02-04 Thread David Nicol
$price_sth-execute; my ($o_file_price) = $price_sth-fetchrow_array(); if ($price_sth-fetch) { $this-log_error('ERROR: scalar select returned second row at %s line %d', __FILE__, __LINE__); } I expected the fetch to return undef, but it throws an Oracle error. My best

Re: Surprising DBD::Oracle error raised

2014-02-04 Thread John D Groenveld
In message CAFwScO-0DchsbSLPSmR9JY+KmBUF3BfUREH9XdDSVgEAo=p...@mail.gmail.com , David Nicol writes: $price_sth-execute; my ($o_file_price) = $price_sth-fetchrow_array(); if ($price_sth-fetch) { $this-log_error('ERROR: scalar select returned second row at %s line %d', __FILE__,

Re: Surprising DBD::Oracle error raised

2014-02-04 Thread David Nicol
the error message claimed I hadn't executed the statement. I changed it to if (eval { $price_sth-fetch}) { $this-log_error('ERROR: scalar select returned second row at %s line %d', __FILE__, __LINE__); } but I think I'll change it again to if ($price_sth-{Active} and