This is a quick RFC concerning database wrapper modules and
frameworks, large and small, which are quite common on CPAN;
specifically it concerns such things that are not any of my creations.
I am going to propose a Lightning Talk for OSCON in the next few days
(deadline is July 22, a practice is on July 19th) on the subject of
databases and SQL generation and portability and such things.
Without naming names, I want to address all the important features
that users want out of modules and frameworks for SQL generation,
portability, easier-of-use, etc.
Please reply and summarize or list all the things you want to do with
such modules but can't do easily or at all; eg, what kind of database
features and SQL constructs and features do you want to use that the
modules you otherwise like don't provide an API for. That is, what
kinds of tasks do you still have to write raw SQL statements and/or
SQL fragments for because there is no alternative to doing so, or the
alternative is unpleasant enough to avoid.
Also list the features the modules do provide that you wouldn't want
to give up, particularly if very few modules support those features
and others don't.
Alternately, if you were going to use a single SQL generator /
database wrapper exclusively for all of your tasks, what types or
functionality would it need, including ease of use features.
Please write back to me asap, either in private or on list as
appropriate, but keep in mind that I will post the aggregated
responses on the forum anyway.
While you can name names in your responses, I will not be naming any
particular modules you bring up in my talk, but just talk about
common issues.
Thank you in advance for any help. -- Darren Duncan
