A third option is to help improve the code for SQL::Statement and the other underlying technologies. That way, you improve the speed of your code and you give back to the community that has helped you solve your problem so quickly and easily.
I like that option. :-)
My criteria for good software:
Does it work?
Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
Comment on Re: How to make my DBD::CSV DB code faster.
I like that option too, patches are welcome :-). In this particular case, though, I suspect the OP's loop approach is a significant portion of the problem.