possible problem with DBD::mysql and new mysql clients

"Andreas Nolte" <[email protected]>
Newsgroups gmane.comp.db.mysql.perl
Message-ID <003a01c4ca6f$b4882b60$6602a8c0@INELUKI>
Hi all,

hopefully this email does not qualify me as a total noob, but I just wanted to point at a possible problem with DBD::mysql and new mysql clients.

We are running a few sites with mysql and OpenInteract as a web application server. Since now MySQL 4.1.7 is marked productive, we thought we should test it out.

So well, I upgraded to DBI 1.45 and DBD::2.9004 after installing the new client and all tests ran successfully. But when I start the web server, apache keeps on segfaulting.

So you might say - this is an OpenInteract bug or whatever, but this is what I tested:

- downgraded DBI to 1.44 and 1.43 and recompiled -> same result. I did this, because there where rumors about DBI 1.45 bugs.
- upgraded DBD::mysql to newes devel version -> same result.
- downgraded MySQL client to 4.0.21 gcc -> everything works ok.

The strange thing is, that all of my test scripts w/o apache worked ok, as did some OpenInteract test scripts that go w/o apache.

I `d be suppling more thorough input, if I knew how to approach this problem. Any hints ? The only thing I did not test ( yet ) is reading and storing BLOB data with the new client. OpenInteract uses Apache::Session to store session data - maybe this is what breaks the code.

So - if I got more, I`ll tell you. So far I just wanted to alert you, that there might be a problem - but maybe I am just doing s.th. wrong. If you got an idea, how I could generate some more useful input for you - please just tell me.

Regards

Andreas Nolte

[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.