On Thu, Jan 22, 2004 at 02:02:45PM -0500, Jeff Urlwin wrote: > > I, actually, think the "Driver" test would be more useful for Driver writers
I would definitely appreciate a framework that would be testing individual DBI features of the driver. It would be up to the driver author to specify which of the RDBMS features the driver / database does not support and the framework would test the rest. I admit that my DBD::XBase lacks many of the features present in the newest DBI specs / versions. Having a quick way to find those would drag me closer to implementing them. The other part is ensuring that the driver does not corrupt the database operation, e.g. that select 1 really return 1, not 2. Here I believe it's up to the individual authors to write the driver specific tests for the code present in their drivers and I see it as a much lower priority to have a unified test suite for each and every possible database operation. -- ------------------------------------------------------------------------ Honza Pazdziora | [EMAIL PROTECTED] | http://www.fi.muni.cz/~adelton/ .project: Perl, mod_perl, DBI, Oracle, large Web systems, XML/XSL, ... Only self-confident people can be simple.
