MySQL (mysql)

MySQL data driver deployment, connection configuration and ad hoc verification.

Connect to MySQL via MySqlConnector and convert model queries and writes to the MySQL dialect. The application uses it through Data Access Interfaces or Data Services, and the public mapping, conditions and data schema still follow the organization of the data engine.

Item	value
source code directory	Zongsoft.Data/drivers/mysql
NuGet package	Zongsoft.Data.MySql
Connection and Script Driver Key	MySql

Deployment and Connection

Append the following snippet to the existing host's deployment manifest. If Data has been deployed, there is no need to declare the same package again; the driver's manifest, assembly and runtime dependencies should be delivered together, see Deployment Tool.

Existing host deployment manifest (append fragment)

[plugins zongsoft data]
nuget:Zongsoft.Data

[plugins zongsoft data mysql]
nuget:Zongsoft.Data.MySql

Traceable Integration Example

Discussions provides the corresponding database script. Follow the real Feedback, Forum, Thread, Post and other models and Discussions.mapping. For query and writing, see Data Services. The existence of the script does not mean that end-to-end verification has been completed for all tables and all driver combinations; in particular, model members, column lengths, default values, relationships, and tables used by the current business must be checked.

Source: framework/Zongsoft.Data/drivers/mysql/test/ConnectionSettingsTest.cs (excerpt; see source for context).

ConnectionSettingsTest.cs

public void MaximumPoolSizeMatchesProviderDefault()
{
	var settings = Configuration.MySqlConnectionSettingsDriver.Instance.GetSettings("Server=localhost");
	var builder = new MySqlConnectionStringBuilder();

	Assert.Equal(builder.MaximumPoolSize, settings.MaximumPoolSize);
}

This offline test only verifies that the connection settings are consistent with the provider's default connection pool limit; Server=localhost does not establish a database connection here. A complete connection also requires database name, identity credentials, and operating environment related settings.

The plugin host's connection items are still placed in /Data/ConnectionSettings, and the driver keys use the canonical names in the index of this page. The accessor name obtained by the business must correspond to the deployment configuration; Discussions obtains the accessor by module name, and the test fixture explicitly passes in the connection settings in the code. The difference between the two entrances is shown in Connections and data sources. The named SQL is still determined by its script's driver, and switching connections will not translate handwritten SQL.

What Should You Pay Attention to with This Driver?

💡Character set, collation and SQL mode may affect the results. Saving of Chinese and emoticons, string comparisons, null values and default values should be verified on the target database.

How to Verify After Integration

Check whether the account can access the target database, whether the connection character set is consistent with the table and column, and then check the case of the table name in the mapping, the generated identification and the batch import results. Read/write separation requires additional configuration of database replication; the driver does not create a replication topology.

Validation should cover a query, a set of actual written data, failure recovery, and then scale to production workloads. Common constraints can be checked against Driver selection and acceptance, Connection Configuration, and Transactions and Consistency.

Project Resources

source code directory · Plugin Manifest · Chinese project description