Re: DBI::Test`s DESIGN.md

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


Martin J. Evans wrote:
> Some of these might be really difficult to deal with in test code. Over 
> the years I've submitted many patches to tighten the DBI specification 
> but at the end of the day having maintained a DBD for quite a while 
> deviations from the specification are just reality.

How about letting the DBDs opt-out of certain tests? Could simply be a 
list of items it provides to DBI::Test (where the items are arbitrary 
words but sometimes just a function name like 'last_insert_id'). Then 
we simply SKIP over the tests if there is a match.

- -- 
Greg Sabino Mullane [email protected]
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201307012133
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAlHSLgMACgkQvJuQZxSWSsiOfgCeJEcMe5zLd2kI1n6A9bkLnCWw
vJoAoK1Qx4sLMrKwwa2CNMURDiahv21E
=yl3l
-----END PGP SIGNATURE-----