Mysql C Api Implementations - Oracle 5.0 Reference Manual

values that contain up to 16MB of data, you must have a communication buffer limit of at least
BLOB
16MB (in both server and client). The client's default maximum is 16MB, but the default maximum in
the server is 1MB. You can increase this by changing the value of the
parameter at server startup. See
The MySQL server shrinks each communication buffer to
each query. For clients, the size of the buffer associated with a connection is not decreased until the
connection is closed, at which time client memory is reclaimed.

20.6.1. MySQL C API Implementations

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
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
libmysqld.
• Install a MySQL Connector/C distribution. Connector/C distributions include only libmysqlclient.
They do not include libmysqld.
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. It is possible that installing both can cause problems.
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 is
libmysqlclient.so
For distributions that include embedded server libraries, the corresponding library names begin with
libmysqld
• On Windows, the static library is
Windows distributions also include libmysql.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, and libmysqld.lib.
Windows distributions also include a set of debug libraries. These have the same names as the
nondebug libraries, but are located in the
compiling clients built using the debug C runtime.
MySQL C API Implementations
Section 8.9.2, "Tuning Server
or at build time.
libmysqld
on most Unix systems and
rather than libmysqlclient.
mysqlclient.lib
Parameters".
net_buffer_length
libmysqlclient.dylib
and the dynamic library is libmysql.dll.
library. You must use the debug libraries when
lib/debug
2131
max_allowed_packet
[477] bytes after
and
libmysqlclient
on Mac OS X.
[466]