Safe by defaultIdentifiers are validated and quoted by the configured dialect; values are passed as Dapper parameters.
Dapper stays in chargeDb4Net builds and executes commands, but does not add tracking, relationships, migrations, or SaveChanges().
Typed mappingStandard attributes such as Table, Column, Key, and NotMapped drive table and column metadata.
Entity conveniencesInsert, update, delete, many-entity, and conflict-aware shortcuts reuse the same validated builders.
Lightweight transactionsPass existing transactions through to Dapper or group explicit operations with BeginTransaction().
Multi-dialect renderingSQL Server, SQLite, PostgreSQL, and MySQL are supported for quoting, paging, and conflict SQL.