On 2013.01.23 1:07 AM, Jens Rehsack wrote:
I'd *love* to see that error fixed so all drivers authors could make use
of, and contribute to, a common DBI driver test suite.
You suggest a DBI::Test suite which is a separate module and is required by DBI?
This completely different to previous statements
where DBI should have no additional dependencies ...
I don't think having a sharable test suite as an external dependency is a
problem. Its like the DBI distribution simply being split in two, but that
other modules can then depend on just the test suite portion. In fact, if the
DBI metadata is appropriately setup, then this external would just be a "test
requires", and so ones simply wanting to install DBI and which trust it already
works don't even need to pull the other one.
On a slight tangent, I finally have a mini-sabbatical from work of 4 weeks,
during which time I hope to complete a working parser, syntax tree, and possibly
executable of my Muldis D language. This is relevant to you because I have also
designed a standardized way to represent arbitrary SQL as a syntax tree, the
same one as my language, and this could form the basis of a more comprehensive
cross-DBD test suite. In a nutshell, this involves taking the basic "rtn(args)"
format of calls for user-defined SQL routines and using the same format for all
the SQL built-ins too (eg, IUD and the parts of SELECT), rather than a pile pf
special syntax, and so analysis or further processing of parsed SQL is a lot
easier. If you don't see the benefit, then never mind, and I'll come back to
you when I have an executable, hopefully soon.
-- Darren Duncan
