On Mon, Jun 12, 2006 at 03:24:55PM +0100, Martin J. Evans wrote:
Hi,
DBI documentation says execute on a an active statement should imply a finish
call but DBD::DB2 does no appear to do this - see example below.
This issue is now causing me a severe amount of grief as we have no finish
On 13-Jun-2006 Ron Savage wrote:
On Mon, 12 Jun 2006 15:24:55 +0100 (BST), Martin J. Evans wrote:
Hi Martin
This seems to fall into the category of the first quote from the
I saw the original post, and expected someone else to answer.
I don't agree that it falls in the first category.
On Tue, 13 Jun 2006 10:28:00 +0100 (BST), Martin J. Evans wrote:
Hi MArtin
When I add the dbd_st_finish call it works and I cannot as yet see
any side effects other than making DBD::DB2 do what the DBI docs
say.
OK. Fair enough.
I was really trying to provoke you to reassess your
On 13-Jun-2006 Tim Bunce wrote:
On Mon, Jun 12, 2006 at 03:24:55PM +0100, Martin J. Evans wrote:
Hi,
DBI documentation says execute on a an active statement should imply a
finish
call but DBD::DB2 does no appear to do this - see example below.
This issue is now causing me a severe
Hi,
DBI documentation says execute on a an active statement should imply a finish
call but DBD::DB2 does no appear to do this - see example below.
This issue is now causing me a severe amount of grief as we have no finish
calls anywhere in our code and we are finding more and more cases where
On Mon, 12 Jun 2006 15:24:55 +0100 (BST), Martin J. Evans wrote:
Hi Martin
This seems to fall into the category of the first quote from the
I saw the original post, and expected someone else to answer.
I don't agree that it falls in the first category. I strongly suspect you'll
have to amend
Hi,
I'm using DBD::DB2 0.78 and DBI 1.51. I am finding that code which is working
to DBD::ODBC and DBD::mysql fails with invalid cursor state but inserting a
call to finish makes it work. Up until now, I've never used finish because the
docs say:
If execute() is called on a statement handle
WAG here: will the DBD::DB2 driver implicitly finish the resources if
you try calling $sth-fetchrow_array() again?
I don't know if DBD::DB2 can know whether there are more rows left in
the result set until you try fetching the next row, ergo it keeps the
statement handle active.
Dan
On
On 09-Jun-2006 Dan Scott wrote:
WAG here: will the DBD::DB2 driver implicitly finish the resources if
you try calling $sth-fetchrow_array() again?
Yes.
I don't know if DBD::DB2 can know whether there are more rows left in
the result set until you try fetching the next row, ergo it keeps the
