Optionally you can use the driver configuration file. Note that "add argument" means "add argument to TFDPhysMySQLDriverLink.EmbeddedArgs list". Include the TFDPhysMySQLDriverLink component in your application.To prepare your application to work with a MySQL Embedded server, you should take the following actions: In case of incorrect arguments for libmysqld.dll initialization, the application may silently terminate.
For simplified setup, see examples later. The general MySQL Embedded setup may be hard.libmysqld.dll v 5.1.34, as probably some other versions, are broken and do not work.libmysqld.dll and errmsg.sys must be of the same version.You can specify paths relatively to the application EXE folder, which simplifies the deployment. All path argument values use Unix backslashes.Setting the MetaDefCatalog does not change the current database in the MySQL session.
The Design time code excludes the catalog name from the object name if it is equal to MetaDefCatalog.
The connection collation becomes the default collation of the character set. The default character set for the connection. If the Database is not specified, no current database is set up. Name of the current database for the connection. The TCP/IP port on which the MySQL server is listening. The TCP/IP address or host name of the server running a MySQL server. To connect to a MySQL DBMS, most applications require that you specify DriverID, Server, Database, User_Name, Password, and CharacterSet (see Defining Connection (FireDAC) for details). or include the unit in the uses clause.drop a TFDPhysMySQLDriverLink component from the "FireDAC Links" component palette page.Sudo ln -s /usr/lib64/mysql/libmysqlclient.so.18 /usr/lib64/mysql/libmysqlclient.so