Releases · 2 min read

MySqlConnector (Bulk)

This page contains the latest information of the releases of RepoDb.MySqlConnector.BulkOperations library.

View the NuGet package here or download it directly here.

RepoDb.MySqlConnector.BulkOperations (v1.17.0)

Released: TBA

Adopted the Roslyn and Meziantou static code analyzers across the codebase and applied the resulting fixes — including ConfigureAwait(false) on async calls, ArgumentNullException over NullReferenceException, and other code-quality corrections. #1328 #1331
Updated the NuGet package icon to the new logo and refreshed the README with a consistent header, description and a link to the get started tutorial.
Referenced the RepoDb package v1.17.0.
Referenced the RepoDb.MySqlConnector package v1.17.0.

RepoDb.MySqlConnector.BulkOperations (v1.16.0)

Released: September 9, 2026

First general availability (non-preview) release of the MySqlConnector Bulk Operations package, promoting the v0.0.1-alpha1 release below to stable. No functional changes since v0.0.1-alpha1 — see that entry for the full feature set and known limitations.

RepoDb.MySqlConnector.BulkOperations (v0.0.1-alpha1)

Released: August 81, 2026

New

First release of the bulk operations extension for RepoDb.MySqlConnector, providing BulkInsert, BulkMerge, BulkUpdate, BulkDelete, and BulkDeleteByKey, each with an Async overload, callable against a MySqlConnectorConnection, a table name, or a DataTable.

Verification status: this package has been implemented and reviewed, but not yet exercised against a live MySqlConnector instance. Verify the bulk-load path, the identity read-back, and the staging-table strategy end-to-end before relying on this package in production.

What’s included

BulkInsert, BulkMerge, and BulkUpdate.
BulkDelete — matched by qualifiers, staging the qualifier columns only.
BulkDeleteByKey — matched by primary key, as a dedicated overload separate from BulkDelete.
MySqlConnectorBulkImportIdentityBehavior (Unspecified, KeepIdentity, ReturnIdentity) — controls whether identity values are sent, ignored, or read back.
MySqlConnectorBulkImportPseudoTableType (Auto, Memory, Physical) — picks the staging-table strategy used by BulkMerge/BulkUpdate/BulkDelete.
MySqlConnectorBulkInsertMapItem — explicit source-to-destination column mapping for BulkInsert.

Known limitations (v1)

The bulk-load step is agnostic of the caller’s transaction — rows it writes commit independently, so a rolled-back transaction will not undo a plain BulkInsert’s already-copied rows. Request ReturnIdentity to force the transactional array-bind path if this matters for your workload.
Memory staging currently always resolves to Physical, which has no per-session isolation — concurrent callers bulk-writing to the same table will race each other’s staged data.
The staging table for a given (table name, pseudo table type) combination is created once per process and reused; the first call against it commits any pending work in its transaction.
Referenced the RepoDb package v1.16.0-alpha2.
Referenced the RepoDb.MySqlConnector package v1.16.0-alpha1.