Problem with mysql_num_rows() on HP and MySql 3.x.x

[Hebron Mak]

Has anyone ran into problems where mysql_num_rows() return 0 when I
know the result set contains a certain number of rows? My code looks
something like this:

MYSQL_RES *result;
int numRows = -1;
mysql_query(conn, "show databases");
result = mysql_store_result (conn);
numRows = mysql_num_rows (result);

On an HP machine running MySql 3.23.x, mysql_num_rows() always returns
0. It works fine on a sparc and alpha. Looks like
mysql_store_result() messed up the connection object, and num_rows is
one of the elements that got messed up. I can do mysql_fetch_row()
just fine, but mysql_num_rows() would still return 0. Anyone have
this same problem?

[Hebron Mak]

Looks like mysql_store_result() doesn't mess up anything. However,
the result set that it returns has num_rows set to 0. I am wondering
whether this has anything to do with the fact that num_rows is a
ulonglong, which is 64-bits on an HP system, but 32-bits on Sparc and
Alpha.