Greg Sabino Mullane wrote:
-----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?
Seems the proper place for it...
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. :)
Or, it gives us the opportunity to coax people to upgrade
their perl versions ;^). And of course, just cuz its CORE, doesn't
preclude interim updates.
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).
Does $sth->bind_param(1, undef, { TYPE => SQL_VARCHAR });
not work for your case ?
bind_param_all() or some such does sound like a nice idea...
and/or an lvalue'd $sth method ? ie, just assigning values
* Making the fetch series a bit more intuitive (and shorter named), so I
can avoid doing things like this:
$info = $sth->fetchall_arrayref({});
Not certain thats solvable. Assuming Perl6 is still 'TMTOWTDI',
some ability to provide explicit differentiation is probably needed,
tho I spose some wantarray tests might help reduce the number of i/f's.
(albeit at the price of possible confusion).
* Fixing this problem:
$dbh->connect(... {RaiseError = 0}) or die "Blah..\n";
$dbh->{RaiseError} = 1;
I'd hope that Perl6 exception handling would be the ultimate
solution to such issues.
Dean Arnold
Presicient Corp.
