Hi Warren,
The answer is yes to all these questions, but I noticed that ping()
makes the program core dump when it is called on a Connection object
that hasn't been connected yet (real_connect not yet called, in my case).
I tested this using the mysql c api and the same thing happened
also. If I call mysql_ping on a MYSQL handle that hasn't been connected
to the db, then the program core dumps.
At least now I know this isn't caused by mysql++.
I would assume that this should return a non-zero response as
opposed to core dumping. Is my assumption correct? I can't seem to find
any reference to this online.
Thanks,
Nash
Warren Young wrote:
Quote:
Nash Kabbara wrote:
My case is very similar to http://lists.mysql.com/plusplus/2779.
Then I would suggest the same answer Sinisa gave: are you certain that
MySQL++ is built against the same MySQL C library as you're linking
your program against?
Are you by chance using a binary release of MySQL++?
Do the examples work? |
--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw