Re: RFC on other database wrapper modules

Sorry for the delayed response; I hope this is still helpful.

I'm the author of DBIx::SQLEngine and basically use it for all of my
database work, so take my comments with a grain of salt.

I'm glad Terrence Brannon has already pointed you towards my previous
attempt to summarize DBI wrapper features:
http://search.cpan.org/dist/DBIx-SQLEngine/SQLEngine/Docs/Related.pod


Of the features in that comparison matrix, the ones I think I could
live without for most projects are the named configs and schema
management. The others I tend to think of as mandatory:
- A DBI wrapper with easy, single-statement calls for the common types
of interactions.
- Portable generation of common kinds of queries from Perl-ish data
structures, with a pass-through option for when the generation logic is
insufficient.
- Extensible object-mapping mechanism, so that I can easily bind the
rows in some table to a particular class of objects.

There are parts of DBIx::SQLEngine that could use improvement -- like a
richer set of formats for expressing criteria in Perl datastructures to
be converted to a SQL WHERE clause, and more extensive support for
DBMS-specific type conversions and column bindings -- but the overall
structure seems to work and it's clear how one could go about making
those improvements without breaking anything. (In fact that reminds me,
I need to find some time this weekend to integrate a Pg patch a user
posted with bind_params fir BLOB columns...)

-Simon

.