"Using DBI with perl threads is not yet recommended for production environments. "
Do you have any first hand experience of use DBI with threads?
Because citing decade old scaremongering quotes from docs that never get updated -- when there are thousands of people using DBI in conjunction with threads -- isn't useful.
Could that be the reason why there are problems with long queries and not with simple ones?
Care to explain the logic behind that piece of deduction?
It looks like you are using threads
The fact that the version of perl (and thus the version of DBI) was built with threading enables, does not mean "he's using threads". Neither do the presence of thread handles in the traces.
That simply means that he could (safely) use threads if his application required it.
If you look closely at those traced thread handles, you'll see they are all the same! So, at least the bit traced, is single threaded.
Bottom line: speculations on subjects you appear to know little about and have personal bias towards doesn't help anyone.
In reply to Re^2: sth->execute returns undef when successful
by BrowserUk
in thread sth->execute returns undef when successful
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |