Tim Bunce wrote:
On Fri, Jul 22, 2005 at 01:18:07PM -0700, Dean Arnold wrote:
In the DBI 1.48 POD, it says...
"Multiple variables can be bound to a single column, but there's rarely
any point."
Is that true ?
Yes.
Does that mean that I have to explicitly
$sth->bind_col($colnum, undef);
before binding a new variable (assuming I don't want the
old variable to get updated on the next fetch) ?
If it does work that way, is that desirable behavior ?
Actually there's no way to unbind a column, and no one has noticed :)
Hmm, thats a bit of a pickle for DBIx::Threaded to emulate.
At the moment I'm permitting multiple threads to use the same
stmt handle concurrently (at least, in appearance). Which means
one thread can bind one set of column variables, while another
thread can bind another set. My assumption is that the first thread
certainly won't want to see the results of a fetch() on the 2nd
thread (and vice versa), so I'm attempting to isolate the bind variables. I
think
my current implementation will be OK, tho it may carry a bit more
baggage than I expected (the real issue is the behavior of
bound variables on a fetchall_XXX() call, otherwise a simple
copy would work OK).
Wish me luck...
Dean Arnold
Presicient Corp.
