27.6.2 Restrictions When Using the Embedded MySQL Server
The embedded server has the following limitations:
No user-defined functions (UDFs).
No stack trace on core dump.
You cannot set this up as a master or a slave (no replication).
Very large result sets may be unusable on low memory systems.
You cannot connect to an embedded server from an outside process with sockets or TCP/IP. However, you can connect to an intermediate application, which in turn can connect to an embedded server on the behalf of a remote client or outside process.
libmysqlddoes not support encrypted connections. An implication is that if an application linked against
libmysqldestablishes a connection to a remote server, the connection cannot be encrypted.
InnoDBis not reentrant in the embedded server and cannot be used for multiple connections, either successively or simultaneously.
The Event Scheduler is not available. Because of this, the
event_schedulersystem variable is disabled.
The Performance Schema is not available.
The embedded server cannot share the same
secure_file_privdirectory with another server. As of MySQL 5.7.8, the default value for this directory can be set at build time with the
Some of these limitations can be changed by editing the
mysql_embed.h include file and recompiling MySQL.