Andrew Feren wrote:
It's been a while since I looked at all of these. I have some code
using EasyDBI and other code using SimpleDBI.
Me too ... I settled on EasyDBI as well, but made that decision two ago
and don't specifically recall my exact reasoning :-). I do know that
EasyDBI met most of my requirements (would return data in arrays of
arrays, placeholder support, clean easy-to-understand interface). The
one place I ran into problems was with queries to show status on tables,
but a quick ping to the author fixed those errors immediately.
The app the uses EasyDBI is running in production servers and shuffles
around 2TB of uploaded user data a day; I have ran into 0 problems.
Initially EasyDBI was the only one I could get to work on both Linux
and Windows. As of version 1.27 SimpleDBI also works on both
platforms. EasyDBI seems to offer a few more specialized ways to get
data back ('single' for example), but you can get the same info with
either module. My very limited benchmarking of the two modules
yielded comparable results.
I haven't looked at LaDBI or DBIAgent in a long while so I can't
really comment other than to say that when I looked at them they
wouldn't run on Windows.
-Andrew
Josh803316 wrote:
I've read the cpan module docs and have looked at the cookbook example (
http://poe.perl.org/?POE_Cookbook/DBI_Helper_Processes). The following
modules all run non-blocking async dbi calls for poe but I'm not sure
which
I should choose. I would love to see a pro/con list for these or get
some
sort of guidance on which would work better in my network testing app.
I'm sure everyone has favourites out there, but is there any reason
to use
one over another in certain scenarios? Are there any drawbacks or
things to
watch out for on specific modules?
POE::Component::LaDBI
POE::Component::EasyDBI
POE::Component::DBIAgent
POE::Component::SimpleDBI
