I'm perplexed.
My company develops a browser-based application that uses the mySQL 'C' API
to talk to the MySQL backend.
I'm currently trying to find a solution to a problem my company is having
with migrating from MySQL v.3.22 to v.3.23. Here are the details:
1. Running a MySQLd service, v. 3.22, on a Solaris 7 server. Our
application's CGI is also mounted on a Solaris box.
2. We tried upgrading the libmysqlclient.a file that our app uses to V.
3.23.40. This means we'll have an app using a v3.23 mysql API to talk to a
MySQL v. 3.22 server. No features new to V. 3.23 were used.
3. The Segmentation Faults we got because of this change were countless.
mysql_fetch_row(), mysql_error(), mysql_affected_rows() were all failing or
returning garbage values.
So my question sort of boils down to this: Are there any incompatibility
issues here that I have overlooked? Do I need a MySQL V3.23 server to talk
to the MySQL V3.23 API? Any help with this issue would be appreciated.
Brad Morris
Software Developer
Core Networks Inc.
[EMAIL PROTECTED]
Phone: (902) 481-5750 ext. 2163
Fax: (902) 481-5799
CoreOS - Broadband Provisioning System - Streamline account provisioning,
support processes, IP address and DHCP management and RF level monitoring,
for both DOCSIS and proprietary systems.
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
