Re: DBI drivers by duck-typing

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> I believe that DBI should go away as an actual piece of code and instead be 
> replaced by an API specification document, taking PSGI as inspiration.

I'm having a hard time envisioning how this would work in practice. What I 
see is lots of duplicated code across the DBDs. So a "DBI bug" would be 
handled by updating the API, bumping the version, and waiting for individual 
DBDs to implement it? A recipe for a large collection of supported API versions 
out in the wild, I would imagine.

> The concept of driver-specific methods, like pg_*, just become ordinary DBD 
> methods that are beyond what is defined by the DBI spec.

Seems a sure recipe for namespace collisions. Also makes it much harder to 
spot any DBMS-specific hacks in your Perl code.

- -- 
Greg Sabino Mullane [email protected]
PGP Key: 0x14964AC8 201109211632
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAk56SzcACgkQvJuQZxSWSsgdzwCguJbIqtX5zjAkDtUvbvUmEn87
Y4AAmwbQeD/KxyBbiUa8WL6fDOXX9wE3
=8RbY
-----END PGP SIGNATURE-----