On Fri, 25 Jul 2003, Merlin, The Mage wrote:
> oix ppl,
>
Hello,
> there are two diferent modules in CPAN for DBD::mysql.
>
Yeah that is somewhat confusing, but it has been that way for a while, and
I don't know enough about CPAN to know why it is happening?
> The older one is from Jochen Wiedmann, and is the (from my view) working
> one. The new one, from Rudy Lippan, says in it docs that it is form Jochen
> Wiedmann, but this isn't the same module.
>
> The original one, for example, allow execution of
>
> $sth=$dbh->prepare("SELECT zbr FROM xpto LIMIT ?"); $sth->execute(10);
>
> And the new version from RUDY doesn't.
>
>From the ChangeLog:
* Fixed bug where strings that were used in numeric
context were not getting quoted on execute(). Now all
parameters are bound as varchar by default.
**NOTE** this is a change in behaviour that MAY cause problems
with some SQL statements. If quoted integers, for example,
cause any problems, use bind_param(<column_id>, SQL_INTEGER) to
force a column to be bound as an integer.
And the thread:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg02133.html
> I said new version because this version is 2.9002, while the version from
> JWEID is 1.2219, so when someone does a install DBD::mysql get the RUDY
> version.
The last version that JWEID uploaded was 2.2028 on 25 Jun 2003; 1.2219 is
way old -- uploaded 30 Oct 2001.
>
> My question is why is this new version, uploaded at Jun26 is in the CPAN,
> should it be removed? Why does this new module have the same name, without
> even a case diference, and why was it upload by Rudy if it is from the
> JWEID?
>
Sorry, I did not make note of the change in maintainership in the
documentation... I did not know exactly what to change to indicate that I
am now maintaining the module, but that it was originally by Jochen, and I
did not want to step on all of the great work that he has done -- I just
made a pass at clarifying the docs.
Rudy
