in reply to Re^3: DBD::ODBC and FreeTDS / limited to one statement handle
in thread DBD::ODBC and FreeTDS / limited to one statement handle
So it turns out I'm a goof (this is not surprising), and after posting here, ruminating, and digging through the FreeTDS code, my brain proposed another solution. If I can't have multiple statement handles for a single database handle, can I have multiple database handles, each with its own statement handle? I should try that, right? The solution couldn't be that obvious, right? RIGHT?
Good grief. I just tried it, and it works. I just created two $dbh guys, each with their own $sth; they each called my good friend fetchrow_hashref, and it all went swimmingly.
I understand this is called Rubber Duck Debugging. Now it's time for some Scotch to celebrate. You goofball.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^5: DBD::ODBC and FreeTDS / limited to one statement handle
by Corion (Patriarch) on May 15, 2024 at 10:26 UTC | |
|
Re^5: DBD::ODBC and FreeTDS / limited to one statement handle
by stevieb (Canon) on May 15, 2024 at 07:04 UTC |