> Are your two tables in the same database ?
> If yes only one connection if enough, and you could use a join query
> to do it, thus having a speed improvement of several magnitudes.
I've just downloaded another 2 mysql manuals and have been sit on my chair all
day reading them, but still do not reach the join usage, I hope tomorrow...
> Have you checked that you free the correct result ? set it to NULL
> after used, and add a test for nullity, it may help.
> What version of the API are you using ? which OS ?
> Have you check bugs.mysql.com ?
It is Linux Slackware 10.1 with MySQL 4.1.4 installed from source... I have
tested it too (same program and same version of MySQL) with FreeBSD and the
result is almost the same, the difference is that Linux craches with glib
message and in FreeBSD just sends a warning that the results have been
I suspect that the current version of MySQL frees the resources automatically,
in FreeBSD the warning was more explicit, it said something like "trying to
free again a result chunk"... this one performed a single query and a single
result_free() so there was no place for a mistake...
> That would leave a nice memory leak indeed...
> eventually, recompile and set a break-point before calling mysql_free,
> and look at all variables.
MySQL internal variables? to see the status before? that's a good idea, I will
do it, thanks for your comments and will post it as soon as I get results :-)
I already posted it to bugs.mysql.com but still do not get response