On Wed, 29 Oct 2003, Tim Bunce wrote:

> On Tue, Oct 28, 2003 at 04:39:59PM -0500, Rudy Lippan wrote:
> > > 
> > > Also, I am taking requests for features to be added in the next version of
> > > DBD::mysql; The list, as of right now, is:
> > > 
> > > - Basic UTF-8 support
> > > - column_info()
> 
> Tese, if any are not there already:
> 
>  - $dbh->last_insert_id
> 
>  - $sth->{ParamValues}
> 
>  - $dbh->data_sources

Added to the list. The first two are trivial to do, but I don't know about 
the the third, but I don't expect it to be much harder than column_info(), 
which looks like it is going to be the ugly one.

>  - Use DBD::mysql::*->install_method (if DBD::mysql::*->can('install_method'))
>    to install driver-private methods with mysql_* prefixes
>    and deprecate the old func() versions.

Okay.

> 
>  - From the change notes in DBI 1.31:
>    Change DBIS to DBIc_DBISTATE(imp_xxh)   [or imp_dbh, imp_sth etc]
>    Change DBILOGFP to DBIc_LOGPIO(imp_xxh) [or imp_dbh, imp_sth etc]
>    Any function from which all instances of DBIS and DBILOGFP are
>    removed can also have dPERLINTERP removed (a good thing).
>    (Will make DBI >= 1.31, now almost a year old, a prerequsite)
> 

I think that these are used off and on in the code, so it would probably 
be good to clean up the usage anyway. I guess DBD::Pg should do this too. 
Appended to the list.

> What's the story with the new v4 protocol and server-side placeholders?
> 

I'd like to do the v4 & server-side prepare in || with the changes above.  
My plan at the moment is to do a 2.9004 release that ads the features that
are missing from the newer DBIs, and put the protocol/placeholders in a
3.0 dev branch.  I have a project that I am about to start that will use
server-side placeholders so I will have a good testbed for the changes.

Rudy

Reply via email to