Brian Eley wrote:
> Thanks for your help. I have downloaded and installed the MySQL 4.1 development RPM:
> MySQL-devel-4.1.1-0.i386.rpm. I believe this contains the new C API?
> After rebuilding my programs, some of my problems have been solved, but I still have
> a few programs that have segmentation faults at startup. I have tracked this down to the
> Connection::ping() function. If I comment out all my calls to ping(), I no longer see the
> Are there any known issues with the ping() function? Are there restrictions on when
> or how it can be called? Should it ever be possible to cause a segmentation fault by
> calling it?
> Thanks again for all your help,
> -----Original Message-----
> Brian Eley wrote:
>>I am interested in upgrading to MySQL 4.1 but I have found that doing so breaks
> all of my applications that connect to the database using mysql++. These applications were
> working fine with MySQL 4.0.13 and 4.0.17. I suspect that the changes to the
> communications protocol that were introduced with MySQL 4.1 are the root of the problem.
>>Can you tell me if there are any plans to add support for MySQL 4.1 to mysql++.
> All you need to do is to rebuild mysql++ with latest 4.1 C API.
> Use both static mysql++ and static libmysqlclient.
> And then link in your application with new static libs.
> It will work just fine.
Do not know any problems with ping() function.
It should work fine.
I re-checked and ping() works just fine.
You should re-check that all include files that you used to build
MySQL++ came only from 4.1 just as the libmysqlclient.
I would suggest you double check this.
For technical support contracts, go to https://order.mysql.com/?ref=msmi
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic <sinisa@stripped>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB
/_/ /_/\_, /___/\___\_\___/ Full time Developer and Support Coordinator
<___/ www.mysql.com Larnaca, Cyprus
Meet the MySQL at User Conference ! (April 14-16, 2004)