We're having another problem with MySQL 4.1 which may
or may not be related to mysql-python. I'll post as
much detail as I can.
Red Hat 7.2 and 7.3
We can't make the problem reoccur reliably. I am sure
the problem is happening at the C level since I can
make it happen with only the _mysql library.
The problem is that we're getting a bad resultset
from a query. The query will be a simple "SELECT foo
FROM bar" and a result will come back, but doing
result.describe() shows all the field names as '\x0'
and the type IDs are messed up and don't map to any
types in the conv dict. It looks like the resultset
is bad by the time it's passed to
We can only make this happen on RH 7.2 and 7.3
systems, it works fine on more recent distros. As
well we can't make it happen reliably.
In some other cases we are getting errors about
tables not existing which then show that the
connection is using the wrong database. We have
multiple connections open to the same database, and
it almost seems like select_db on one connection is
affecting the other connection.
This problem may exist in the MySQL 4.1 C libraries
(we have opened a support ticket with them), but I'm
wondering if you've ever seen anything like this
Log in to post a comment.