Re: DBD::mysql make test failures (another instance)

Rudy Lippan <[email protected]>
Newsgroups gmane.comp.db.mysql.perl
Message-ID <[email protected]>
On Mon, 6 Dec 2004, angie ahl wrote:

> Hi List
> 
> I'm having a little fun (in a massochistic sense) trying to get
> DBD::mysql installed.
> 
> I've got mysql (4.1.7) in a not so standard directory, my own
> compilation of perl 5.8.6 and mod_perl. on OS X 10.3.6

> 
> I've added the cflags and libs to Makefile.PL and have got happily
> through make at last.
> 

It should pick those up from mysql_config -- but it has to be in your path 
before Makefile.PL can execute it.


> make test is erroring though, and make test TEST_VERBOSE=1 is
> identifying the following errors:
> 
> please note I am trying to get unicode working so this may have
> something to do with length failing, I'm not sure though.
> 

Unicode is not well supported in DBD::mysql -- this is on my to-do list for
December; however, there are a few patches floating around on the list that will
give Unicode support that will work but I don't think that the implentations 
that I have seen heretofore are clean enough for inclusion in the
distribution proper (they don't detect the diff between binary columns and text 
columns).

> First we have t/akmisc:
> t/akmisc...........Verifying whether fetchrow returns TRUE for results.
> 1..351
> 
> Checking $sth->length
> not ok 51
> Error in length array, expected 32 32 32, got 96 96 96.
> 
> Fetchrow from non-select handle Mysql::Statement=HASH(0x41733c)


Mysql::Statement is a compatibility layer for the old pre-DBI Mysql module. 
Although I don't know why it is doing this, but it might very will have to do 
with unicode.

> not ok 342
> Error in control character hash at 129, ? <-> ?.
> 
> 
> FAILED tests 51, 342
>         Failed 2/351 tests, 99.43% okay
> 
> next we have t/mysql
> 
> t/mysql............1..68
> Checking number of rows.
> not ok 30
> not ok 46
> not ok 47
> not ok 48
> FAILED tests 30, 46-48
>         Failed 4/68 tests, 94.12% okay
> 
> Any ideas what these failures are, can I go ahead and install or is
> there anything I can do to fix the above:
> 

IIRC, this is because OS X has a broken file system that does not know the
difference between 'File' and 'file', and since mysql just stores the table
names as files on disk, the caps in the test are screwing with the test results
(I think this might be fixed in CVS, but I'd have to check).

Rudy


-- 
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe:    http://lists.mysql.com/[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.