I thought this nntp gateway worked in both directions, but apparently it is
read only. I guess that
explains I no one ever responds to my posts (or maybe I just never say
anything worth responding to...)
So I'm copying and pasting below what I tried to post on perl.dbi.dev.
Martin J. Evans wro
On Wed, 2006-09-06 at 15:01 -0400, Steven N. Hirsch wrote:
> > What I need assistance with is to change DBD::Oracle's execute_for_fetch to
> > understand array context so it can return the tuples executed and the rows
> > affected (which it already has). At the same time we could fix the bug I
> >
> What I need assistance with is to change DBD::Oracle's execute_for_fetch to
> understand array context so it can return the tuples executed and the rows
> affected (which it already has). At the same time we could fix the bug I
> reported in DBD::Oracle so in scalar context it returns the tuples
On Wed, 2006-09-06 at 13:16 -0400, John Scoles wrote:
> Hi Martin.
>
> I have been following it closely but I have no cycles this week to work on
> it.
>
> >This rendered execute_array with DBD::Oracle useless to me. However,
> >looking at
> > DBD::Oracle and OCI I've discovered OCI can return
Hi Martin.
I have been following it closely but I have no cycles this week to work on
it.
This rendered execute_array with DBD::Oracle useless to me. However,
looking at
DBD::Oracle and OCI I've discovered OCI can return the total rows affected
(which I want) and in fact due to a bug in DBD:
For anyone in dbi-user list you may have been following my discussion on
execute_array in DBI. Usually what I do in my code is:
$affected = $sth->execute(for an insert statement);
die "did not insert expected number of rows"
if ($affected != $the_expected_number_of_inserts);
which works because
Tim Bunce wrote:
> It would be simpler to
>
> $h->{PrintWarn} = 0;
>
> at the right spot. (Perhaps in a block and using local.)
Hi Tim,
Yeah, that would be simpler (and it's what I do in my own code), but my
impression was that John wanted to leave the warning in there to test
that it wou
It would be simpler to
$h->{PrintWarn} = 0;
at the right spot. (Perhaps in a block and using local.)
Tim.
On Wed, Sep 06, 2006 at 10:13:15AM -0400, Garrett, Philip (MAN-Corporate) wrote:
> John Scoles wrote:
> >
> >> t/26exe_array...DBD::Oracle::st execute_array warning:
> >> OR
Ok I will put it in the next version.
Most likely I will work on it next week so I can get a new version out at
the end of the month.
Cheers
John Scoles
- Original Message -
From: "Garrett, Philip (MAN-Corporate)" <[EMAIL PROTECTED]>
To: "John Scoles" <[EMAIL PROTECTED]>; ;
Sent: We
John Scoles wrote:
>
>> t/26exe_array...DBD::Oracle::st execute_array warning:
>> ORA-24381: error(s) in array DML (DBD SUCCESS_WITH_INFO: error
>> possibly near <*> indicator at char 66 in 'INSERT INTO
>> dbd_ora__drop_me ( row_1, row_2, row_3) VALUES (:p1,:<*>p2,:p3)')
>> [for Statement "
Patrick Galbraith wrote:
Steve Hay wrote:
Steve,
I'm really sorry I didn't respond to this and your subsequent emails. I
have been involved with our falcon project which is top priority right
now, as well as selling a home and moving across country so much of my
free time has been non-existe
11 matches
Mail list logo
