Net4x.DapperLibrary.MySql 1.9.9

DapperLibrary.MySql

MySQL provider integration for DapperLibrary. This project supplies a MySQL-specific DapperContext implementation, a provider factory and MySQL-specific database model and type mappings using MySql.Data.

Purpose

Provide MySQL engine-specific behavior while preserving the common DapperLibrary API. The assembly includes:

• MySqlDapperContext � a DapperContext configured for MySQL and wired to MySqlProviderFactory and DapperConfigurationManager.
• MySqlProviderFactory � configures parameter handling, data adapter events and the database model factory for MySQL.
• MySqlDatabaseModel, MySqlDatabaseModelTypes and MySqlDatabaseEnumTypes � identifier delimiters, statement terminator, parameter naming and SQL type mappings for MySQL.

Key types

• MySqlDapperContext

  • Derives from DapperContext and initializes the context with MySqlProviderFactory and optional configuration.
  • Static helpers Use, Use(IContextCreator), Use(string, string) and UseOnce integrate with DapperContextFactory and set MySQL-friendly defaults when contexts are created:
    • DatabaseModel.IdentityInitializer = "AUTO_INCREMENT"
    • DatabaseModel.FormatDatetimeAsString = dateTime => $"STR_TO_DATE('{dateTime:yyyy-MM-dd HH:mm:ss}', '%Y-%m-%d %H:%i:%s')"

• MySqlProviderFactory

  • Inherits from ProviderFactoryBase and uses MySqlClientFactory.Instance as the underlying provider.
  • Sets ParameterModel.AddIndex = true and installs PrepareCommandParameters delegate.
  • Attaches to RowUpdating / RowUpdated events of MySqlDataAdapter and forwards them so consumers can listen to adapter lifecycle events.

• MySqlDatabaseModel and related types

  • Identifier delimiters: ` (backtick).
  • Statement terminator: ;.
  • Parameter prefix: @ and parameter base name: Par.
  • Type mappings reflect MySQL types (for example BIGINT, INT, TINYINT, DATETIME, JSON, LONGBLOB, DECIMAL, DOUBLE, etc.).

Usage examples

Create and use a MySqlDapperContext directly:

using var context = new MySqlDapperContext();
// use context.Operations / context.Schema / context.SaveDataTable etc.

Register a context creator in bootstrap code:

MySqlDapperContext.Use();

// or bind an explicit connection string and provider name
MySqlDapperContext.UseOnce(connectionString, providerName);

When contexts are created via the static helpers, the database model will be pre-configured with MySQL-sized defaults for identity columns and datetime literal formatting.

Multi-targeting & compatibility

• The project targets .NET Standard and is intended to work across modern .NET runtimes. Ensure your application references a compatible MySql.Data package version for the target framework.
• The broader solution contains conditional compilation for other providers and frameworks to produce framework-specific assets when building the full library.

Synchronous vs asynchronous behavior

• MySQL provider (MySql.Data) supports asynchronous operations. DapperLibrary exposes synchronous and asynchronous variants for operations (GetDataReaderAsync, GetDataTableAsync, SetDataAsync, QueryAsync<T>, etc.).
• Prefer Async methods in server and I/O-bound applications to avoid blocking threads. For legacy or synchronous-only scenarios you can use the synchronous APIs.

Events and data adapter behavior

• MySqlProviderFactory.CreateDataAdapter wires RowUpdating and RowUpdated events from MySqlDataAdapter and forwards them through the provider factory. Consumers using adapter-based persistence can subscribe to these events to inspect or change update lifecycle behavior.

Notes and best practices

• Use WithConnection overloads when executing operations against a different named connection for a single call to avoid contention around ConnectionStringToRead.
• Rely on schema helpers (IDapperContext.Schema) and the library�s caching for efficient metadata reads.
• When persisting entities or DataTables, verify the MySQL server character set and collation settings to avoid unexpected conversions for binary/text data.

For implementation details consult the source files under DbContexts and MySqlProviderFactory.