Not to be rude, but in addition to EZDBI there are also DBIx::Abstract, DBIx::DWIW, DBIx::Easy.

EZDBI: See my reply to the other post mentioning it.

DBIx::Abstract: aims at SQL abstraction, not just making things easier. I often find myself wanting to write queries myself.

DBIx::DWIW: New to me (again, a lowzy name, just like EZDBI), but is MySQL specific and seems not to be capable of returning rows one at a time.

DBIx::Easy: Another SQL abstractor.

So there isn't really competition, just different approaches to using DBI.

I think writing a DBI wrapper is becoming one of those tasks every Perl programmer undertakes, like writing a templating system :-)

That's why you see a lot of CGI scripts with sub query { ... } and sub dbopen { ... } in them. This just proves that DBI itself isn't easy enough.

I've written multiple DBI wrappers myself, and until recently, I created a new one for every project. I thought about how I would really like it, and how error handling in between prepare, execute and fetch* could be done, so that you can safely stack method calls and discover it went wrong later. The result is presented to you in this thread.

U28geW91IGNhbiBhbGwgcm90MTMgY
W5kIHBhY2soKS4gQnV0IGRvIHlvdS
ByZWNvZ25pc2UgQmFzZTY0IHdoZW4
geW91IHNlZSBpdD8gIC0tIEp1ZXJk

Don't get me wrong -- I think you should submit this to CPAN. The module is well-written, documented and serves a specific purpose. IMO competition is good, and one of the unfortunate things about CPAN modules is that many of them are heavily upgraded for ~6 months and then abandoned. If you maintain your module for the long-haul, keeping up with upgrades to the DBI, then you'll be a step ahead in my book.

That said, I think the comparisons you draw with the other modules are distinctions without differences. They do much the same tasks but just in different ways. Some ways might fit the way a developer approaches a problem, some might not. None of these modules fit your approach enough to contribute to it rather than develop your own. No problem.

Fortunately, there's not an all-powerful gatekeeper to CPAN who gives the thumbs-up or thumbs-down to a module. IMO this is one of the features of Perl that makes it organically vital. The fact that there are so many DBI wrappers (and templating modules) means this is a problem everyone tackles, and problems like this are often too generic to have one solution. This might annoy or turn away developers from other languages, particularly ones that have been handed down from the mount (Java), but so what?

Keep up the great work!

Chris
M-x auto-bs-mode