-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> 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.
Could get_info be expanded to include 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.
On the other hand, making it a non-core module greatly increases the
chances that they will have a more reasonably recent version of DBI. :)
My own:
* Gettting rid of bind_param, or at least making it flexible so that I
can specify a placeholder type without sending a value (and vice-versa)
and bind a bunch of params in one command (e.g. a hashref of placeholder
names).
* Making the fetch series a bit more intuitive (and shorter named), so I
can avoid doing things like this:
$info = $sth->fetchall_arrayref({});
* Fixing this problem:
$dbh->connect(... {RaiseError = 0}) or die "Blah..\n";
$dbh->{RaiseError} = 1;
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200507072147
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iD4DBQFCzd1XvJuQZxSWSsgRAk+jAJ9/vHxKhP3isi0s0KMw6ZHdNQS7bQCXXleY
RVycoFRYgwgonRmIzkLhPg==
=c0mP
-----END PGP SIGNATURE-----
