$dbh->column_info changed behaviour between 4.0 and 4.1? Bug in DBD::mysql?

Greetings.

I just upgraded our server from mysql-4.0.25 to mysql-4.1.14.
I *haven't* upgraded DBD::mysql, as this was already compiled against
5.0.x on our clients ( currently DBD-mysql-3.0002_p3 ... I've been
testing stuff against 5.0.x ).

Previously, our applications that did:

$sth = $self->{dbh}->column_info ( undef, $self->{schema},
$self->{sql}->{from}, '%' );

returned a statement handle that I could walk through for *each* field
in the table ( ie in $self->{sql}->{from} ). Now, however, we get 1 or 2
records, and that's it. We should get a record for each field, right?

Am I doing something wrong, or should I file a bug report?

--
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: dkasak@nusconsulting.com.au
website: http://www.nusconsulting.com.au

--
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe: http://lists.mysql.com/perl?unsub=gcdmp-msql-mysql-modules@m .gmane.org

Re: $dbh->column_info changed behaviour between 4.0 and 4.1? Bugin DBD::mysql?

Daniel Kasak wrote:

> Greetings.
>
> I just upgraded our server from mysql-4.0.25 to mysql-4.1.14.
> I *haven't* upgraded DBD::mysql, as this was already compiled against
> 5.0.x on our clients ( currently DBD-mysql-3.0002_p3 ... I've been
> testing stuff against 5.0.x ).
>
> Previously, our applications that did:
>
> $sth = $self->{dbh}->column_info ( undef, $self->{schema},
> $self->{sql}->{from}, '%' );
>
> returned a statement handle that I could walk through for *each* field
> in the table ( ie in $self->{sql}->{from} ). Now, however, we get 1 or
> 2 records, and that's it. We should get a record for each field, right?
>
> Am I doing something wrong, or should I file a bug report?
>
I just reverted to DBD-mysql-2.9007 and it's working fine.
Maybe it broke when we upgraded to DBD-mysql-3.0002_p3 ... I didn't
notice then though =-O
Anyway, should I file a bug report, or is this post sufficient?

--
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: dkasak@nusconsulting.com.au
website: http://www.nusconsulting.com.au

--
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe: http://lists.mysql.com/perl?unsub=gcdmp-msql-mysql-modules@m .gmane.org