At the risk of speaking redundantly, I volunteer myself to co-lead
the common test suite effort, citing the benefits that Tim listed.
Considering that my own wrapper over DBI ("Rosetta") is intended to
have a very rigorously defined API and behaviour from an
application's/user's point of view, I am as a consequence becoming
very sensitive to the differences between different DBD modules.
Therefore, I should be and am able to point out updates that need to
be made with DBD modules in order to commoditize their behaviour,
API, and feature sets. Often this involves a lack of support for
newer meta-data/information functions that have recently been added
to the DBI.
I will of course run everything I find through this list, should a
consensus be required as to the proper way to deal with issues I
bring up.
I hope that all of the important DBD modules are still being actively
maintained, and said maintainers will be able to respond quickly to
raised issues.
In order to keep from bloating this Roadmap thread, I will post my
first suggestion in a few moments under a different subject line.
-- Darren Duncan
- DBI Roadmap Tim Bunce
- Re: DBI Roadmap Darren Duncan
- Re: DBI Roadmap H.Merijn Brand
- Re: DBI Roadmap Michael Peppler
- Re: DBI Roadmap Jonathan Leffler
- sth after a prepare (was: Re: DBI Roadma... Henri Asseily
- Re: DBI Roadmap Tim Bunce
- Re: DBI Roadmap Michael Peppler
- Re: DBI Roadmap Tim Bunce
- Re: DBI Roadmap Darren Duncan
- Re: DBI Roadmap Henri Asseily
- Re: DBI Roadmap Tim Bunce