On 8/2/04 5:36 PM, Tim Bunce wrote:
>> b. DBI v2.0 will not introduce new user features,
>
> Never say never, or even "will not" :)
>
> More like "the primary focus of DBI v2.0 is to enhance the DBI-to-DBD
> interface so that ..."
I meant to post this earlier, but here's my humble feature request for DBI
2.0 (or beyond):
The tied(?) hash interfaces in DBI grate on me. You know,
$dbh->{'RaiseError'}, $sth->{'Active'}, and all that jazz. I'd sorely like
to see these change to normal methods with more Perl-ish names:
$dbh->raise_error(0);
$sth->active;
$sth->ix_cursor_with_hold(1);
Reasons I suspect for the other interface:
* More efficient (maybe)
* Easier to local()ize attributes
* Easier to "no-op" on custom attributes (e.g. ix_CursorWithHold)
(...or a possible bug, depending on how you look at it; see below.)
* Youthful indiscretions of DBI 1.0 and earlier ;)
Reasons I like a regular method call interface better:
* More efficient (maybe)
* Easier to subclass
* Less likely for a typo to cause a "silent" bug
* More perl-ish naming
* Fewer quotes and curly braces :)
Maybe this is DBI 3.0 I'm talking about, or maybe I'll forever be doomed to
implement DBI wrapper after DBI wrapper, but I thought I'd give it a shot :)
-John
