Re^3: MAC OS 10.6 upgrade breaks DBD:mysql

I'm running the stock Perl 5.10.0 that came with Snow Leopard, and it's definitely running as a 64 bit app on my machine. For me, the version of Perl 5.10.0 that shipped with Snow Leopard worked okay with a fresh install of 64 bit MySQL and clean build of DBD::mysql

I wonder if you're seeing problems from multiple incompatible versions of Perl libs being installed or having a library path issue?

Comment on Re^3: MAC OS 10.6 upgrade breaks DBD:mysql

Replies are listed 'Best First'.
Re^4: MAC OS 10.6 upgrade breaks DBD:mysql by DaGaMs (Initiate) on Sep 16, 2009 at 11:34 UTC
I did exactly the same: Install mysql 5.4.1beta 64bit binary from mysql developer website. recompile dbd::mysql. It SEEMS to work fine, but I am having a load of very very strange issues when selecting from tables with blob/text columns. Basically, what happens is that I get `NULL` return values sometimes. Sometimes in this case means not just sporadic, but reproducibly for one script while I'm testing it. However, it's also random, because changing the script, without changing any of the queries, suddenly causes the queries to return data. It's driving me nuts, this error. Yesterday I thought I nailed it, it seemed that always the last requested column of the query returned `NULL`. Today, I changed the query back to where it was failing yesterday, and suddenly it works again. I'm at a loss. I tried the DBD::mysql mailing list, noone had a clue there, either. Oh wise perl Monk, hast though any idea how to salvage my script? UPDATE Actually, I figured out why the behaviour is so unpredictable: The bug must have to do with the actual mysql server doing some caching: When I run a query on the table containing the TEXT column in Sequel (a mysql client for Mac), and then run the perl script immediately afterwards, it works. A few hours later, it doesn't work any more. Now how weird is that?!	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^4: MAC OS 10.6 upgrade breaks DBD:mysql
by DaGaMs (Initiate) on Sep 16, 2009 at 11:34 UTC

I did exactly the same: Install mysql 5.4.1beta 64bit binary from mysql developer website. recompile dbd::mysql.

It SEEMS to work fine, but I am having a load of very very strange issues when selecting from tables with blob/text columns.
Basically, what happens is that I get NULL return values sometimes. Sometimes in this case means not just sporadic, but reproducibly for one script while I'm testing it. However, it's also random, because changing the script, without changing any of the queries, suddenly causes the queries to return data. It's driving me nuts, this error. Yesterday I thought I nailed it, it seemed that always the last requested column of the query returned NULL. Today, I changed the query back to where it was failing yesterday, and suddenly it works again. I'm at a loss. I tried the DBD::mysql mailing list, noone had a clue there, either.
Oh wise perl Monk, hast though any idea how to salvage my script?

UPDATE

Actually, I figured out why the behaviour is so unpredictable: The bug must have to do with the actual mysql server doing some caching: When I run a query on the table containing the TEXT column in Sequel (a mysql client for Mac), and then run the perl script immediately afterwards, it works. A few hours later, it doesn't work any more. Now how weird is that?!

[reply]
[d/l]
[select]