Dean Arnold wrote:
>
> - High-level support for cursors
Seconded.
<snip>
I think some of the following have been raised before, but to reiterate:
1. A standard conformance test suite for DBDs: a very big
(and likely mundane) chore, but really needed/valuable.
2. Full thread safe support.
3. A std. i/f for multistatement result sets.
4. Std. 2PC i/f (XA) ?
5. A better set of metadata for DBDs to report the functionality
they support. E.g., today, the only way to find out if a DBD
is threadsafe (at runtime) seems to be try it and hope for the best.
6. Std. i/f support for exotic datatypes (intervals, UDTs, ARRAY, etc.)
7. Better docs for DBD developers (hopefully PDBI2E will address this ?)
8. (I know I've argued against this in the past, but I've
had a change of heart) DBI inclusion as a Perl CORE module. Database
access is too prevalent these days for it to continue as an afterthought,
and it would likely increase test coverage/exposure.
Forgot another item:
9. A standard resultset/rowset object. High level cursor support
(esp. scrollable cursors) probably requires it anyway, but
separating the resultset from the executable statement seems
to be a popular idea (see OLEDB/ADO/JDBC/etc....and, in some sense,
Class::DBI, for that matter)
Dean
