Re^3: DBI and finish (risk of calling finish twice)

... cached ... Though it all depends on the actual driver ...

I doubt that :) See inside DBI.pm look for "sub prepare_cached"

Comment on Re^3: DBI and finish (risk of calling finish twice)

Replies are listed 'Best First'.
Re^4: DBI and finish (risk of calling finish twice) by andal (Hermit) on Jun 27, 2014 at 06:22 UTC
Well, "cached" does not mean only "prepare_cached" :) Whichever caching mechanism is used, prepared statement with unfinished fetch may introduce problems. I guess you've seen the description of $if_active flag for DBI::prepare_cached :) That is why, calling finish in this case might be important.	[reply]


good chemistry is complicated, and a little bit messy -LW
	PerlMonks