- 21.8 MySQL C API
- 21.8.1 MySQL C API Implementations
- 21.8.2 Simultaneous MySQL Server and MySQL Connector/C Installations
- 21.8.3 Example C API Client Programs
- 21.8.4 Building and Running C API Client Programs
- 21.8.5 C API Data Structures
- 21.8.6 C API Function Overview
- 21.8.7 C API Function Descriptions
- 21.8.8 C API Prepared Statements
- 21.8.9 C API Prepared Statement Data Structures
- 21.8.10 C API Prepared Statement Function Overview
- 21.8.11 C API Prepared Statement Function Descriptions
- 21.8.12 C API Threaded Function Descriptions
- 21.8.13 C API Embedded Server Function Descriptions
- 21.8.14 Common Questions and Problems When Using the C API
- 21.8.15 Controlling Automatic Reconnection Behavior
- 21.8.16 C API Support for Multiple Statement Execution
- 21.8.17 C API Prepared Statement Problems
- 21.8.18 C API Prepared Statement Handling of Date and Time Values
- 21.8.19 C API Support for Prepared CALL Statements
The MySQL C API is a C-based API that client applications written in C can use to communicate with MySQL Server. Client programs refer to C API header files at compile time and link to a C API library file at link time. The library comes in two versions, depending on how the application is intended to communicate with the server:
libmysqlclient: The client version of the library, used for applications that communicate over a network connection as a client of a standalone server process.libmysqld: The embedded server version of the library, used for applications intended to include an embedded MySQL server within the application itself. The application communicates with its own private server instance.
Both libraries have the same interface. In terms of C API calls,
an application communicates with a standalone server the same way
it communicates with an embedded server. A given client can be
built to communicate with a standalone or embedded server,
depending on whether it is linked against
libmysqlclient or libmysqld
at build time.
There are two ways to obtain the C API header and library files required to build C API client programs:
Install a MySQL Server distribution. Server distributions include both
libmysqlclientandlibmysqld.Install a MySQL Connector/C distribution. Connector/C distributions include only
libmysqlclient. They do not includelibmysqld.
For both MySQL Server and MySQL Connector/C, you can install a binary distribution that contains the C API files pre-built, or you can use a source distribution and build the C API files yourself.
Normally, you install either a MySQL Server distribution or a MySQL Connector/C distribution, but not both. For information about issues involved with simultaneous MySQL Server and MySQL Connector/C installations, see Section 21.8.2, “Simultaneous MySQL Server and MySQL Connector/C Installations”.
The names of the library files to use when linking C API client applications depend on the library type and platform for which a distribution is built:
On Unix (and Unix-like) sytems, the static library is
libmysqlclient.a. The dynamic library islibmysqlclient.soon most Unix systems andlibmysqlclient.dylibon Mac OS X.For distributions that include embedded server libraries, the corresponding library names begin with
libmysqldrather thanlibmysqlclient.On Windows, the static library is
mysqlclient.liband the dynamic library islibmysql.dll. Windows distributions also includelibmysql.lib, a static import library needed for using the dynamic library.For distributions that include embedded server libraries, the corresponding library names are
mysqlserver.lib,libmysqld.dll, andlibmysqld.lib.Windows distributions also include a set of debug libraries. These have the same names as the nondebug libraries, but are located in the
lib/debuglibrary. You must use the debug libraries when compiling clients built using the debug C runtime.
User Comments
Add your own comment.