Re: Clarification sought on execute_array

I'm sorry to arrive here late. Seems I've been missing all the fun!

Some observations:

- I think it's reasonable for execute_array() and execute_for_fetch()
    to return an error (ie err() true and so trigger RaiseError etc.)
    if execution of any of the tuples encountered an error.

- That'll need a spec clarification and a clear warning in Changes.

- We should avoid breaking existing batch apps that use DBD::Oracle.

- I'm hopeful that the above change wouldn't. (John?)

- We should review other database APIs that provide batch execution
    in order to spec a reasonable common subset behaviour for the DBI.

- Clearly we should bring DBD::Oracle, the DBI default behaviour, and the
    DBI spec into agreement with each other.

- We *really* need a way to share tests across drivers.
    Perhaps something like a separate DBI::TestSuite distro that the DBI
    and drivers could have as a prerequisite. That would contain tests in
    modules.  The DBI and DBDs would have a test file that uses the
    DBI::TestSuite module and calls a function that runs the tests.
    This issue could provide the first test.

Tim.