Sharp.DM.EntityFrameworkCore
10.0.1
dotnet add package Sharp.DM.EntityFrameworkCore --version 10.0.1
NuGet\Install-Package Sharp.DM.EntityFrameworkCore -Version 10.0.1
<PackageReference Include="Sharp.DM.EntityFrameworkCore" Version="10.0.1" />
<PackageVersion Include="Sharp.DM.EntityFrameworkCore" Version="10.0.1" />
<PackageReference Include="Sharp.DM.EntityFrameworkCore" />
paket add Sharp.DM.EntityFrameworkCore --version 10.0.1
#r "nuget: Sharp.DM.EntityFrameworkCore, 10.0.1"
#:package Sharp.DM.EntityFrameworkCore@10.0.1
#addin nuget:?package=Sharp.DM.EntityFrameworkCore&version=10.0.1
#tool nuget:?package=Sharp.DM.EntityFrameworkCore&version=10.0.1
Sharp.DM.EntityFrameworkCore
Entity Framework Core provider for Dameng (DM). Original implementation, MIT licensed.
Status: EF Core 10 release candidate. The provider is feature-complete within the server limits recorded in the Capability Matrix; all EF Core 10 specification bases are inherited and the live suite passes with only the cases recorded in Skipped.md skipped. The v10.0.1 tag is pending the final review. Changes are recorded in the Changelog.
Supported versions
| Branch | EF Core | Target framework | Package line | Role |
|---|---|---|---|---|
efcore/10.0 |
10 | net10.0 |
10.0.x |
Development and release for the EF Core 10 line; v10.x tags are here |
efcore/9.0 |
9 | net9.0 |
9.0.x |
Development and release for the EF Core 9 line; v9.x tags are here |
efcore/8.0 |
8 | net8.0 |
8.0.x |
Development and release for the EF Core 8 line; v8.x tags are here |
dev |
11 | net11.0 (planned) |
11.0.x (planned) |
Reserved for EF Core 11 integration |
master |
11 | net11.0 (planned) |
11.0.x (planned) |
Reserved for EF Core 11 packaging and v11.x tags |
Changes are committed on the version branch and tagged there. EF Core 8, 9 and 10 are not merged into dev or master; those branches are held for EF Core 11. EF Core 8 and 9 reached end of official support on 2026-11-10, so those lines serve existing deployments: they receive defect fixes and capability backports on demand and do not track new features.
Usage
A context configures the provider the way it configures any other. The model is built with the ordinary EF Core API; only the parts that depend on Dameng spelling need this provider.
public sealed class MyContext : DbContext
{
protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
=> optionsBuilder.UseDm("Server=localhost;Port=5236;User Id=SYSDBA;Password=SYSDBA");
public DbSet<Order> Orders => Set<Order>();
}
An application that builds its services up front makes the same call in the registration. There is also an overload that takes a DbConnection the caller owns, and each overload accepts an options action that reaches the relational settings through DmDbContextOptionsBuilder: command timeout, batch size, migrations assembly and the execution strategy.
services.AddDbContext<MyContext>(options =>
options.UseDm(connectionString));
Design time needs nothing extra: dotnet ef finds the context the way it finds any other, so a context that reads its connection string in OnConfiguring or from the environment is enough. The DDL a migration generates is recorded row by row in the Capability Matrix.
The consumer-facing types keep the namespaces the previous provider declares — Microsoft.EntityFrameworkCore, Microsoft.EntityFrameworkCore.Metadata, .Infrastructure, .Migrations, .Diagnostics — and the entry point is still UseDm(), so migrating requires updating one PackageReference. Application code that uses the provider through those types needs no change.
The previous provider also put its internals under Microsoft.EntityFrameworkCore.Dm. Those are not part of the public surface and this provider keeps its internals under DM.EntityFrameworkCore. The one public type a consumer calls from that tree is DmDbFunctionsExtensions (EF.Functions), which this provider ships under Microsoft.EntityFrameworkCore.Dm.Extensions: it carries the date difference members and IsDate, and the Capability Matrix records what each one translates to.
The assembly is DM.EntityFrameworkCore, the same identity the EF Core providers use, and the package id is Sharp.DM.EntityFrameworkCore: the publisher prefix plus that identity. The package is not binary compatible with the previous provider, so consumers recompile, which a package change requires anyway. Consumers using a compiled model (dotnet ef dbcontext optimize) regenerate it.
Building and verifying
Four commands, each proving something the previous one cannot:
dotnet build DM.EntityFrameworkCore.slnx # zero warnings, zero errors
dotnet test DM.EntityFrameworkCore.slnx # the unit and SQL shape suite, no server needed
dotnet run --project samples/DmProviderValidation -- --dry-run # the acceptance model, its migration and its idempotent script
pwsh -File scripts/package-smoke.ps1 # packs, restores in an isolated cache and runs a consumer
Nothing above needs a Dameng instance. The live acceptance run does, and it takes the connection string from user secrets, the ConnectionStrings__Dm environment variable, or its first argument — in that order of specificity — so no credential has to sit in the repository:
dotnet user-secrets set "ConnectionStrings:Dm" "<connection string>" --project samples/DmProviderValidation
dotnet run --project samples/DmProviderValidation -- --secrets=Dm # the secret, under a name
dotnet run --project samples/DmProviderValidation -- --secrets=DmFull # a second instance
pwsh -File scripts/design-time-smoke.ps1 -Secrets Dm # the `dotnet ef` tooling: migrations and scaffolding
It exits non-zero when any step fails and never prints the connection string. Testing records what a run covers, what it does not, and what stays marked as awaiting verification until an instance is reachable.
The functional probe is the second live program and is not part of CI: dotnet run --project samples/DmProviderFeatureProbe -- "<connection string>" exercises the EF Core feature surface — types, keys, relationships, inheritance, owned and complex types, raw SQL and the update pipeline — and reports each step separately.
Design principles
- Dialect separated from version. Dameng dialect knowledge lives in an EF Core-free
Dialect/layer that is shared across branches. Pipeline classes that inherit EF Core base types are implemented per version, with no cross-version abstraction. - Specification suite as the gate. Acceptance is defined by the EF Core specification test suite. Self-authored SQL assertions never stand alone as proof.
- Live database required. A capability not verified against a real Dameng instance is reported as awaiting verification, not as complete.
- Clean licensing. Original code under MIT. No decompiled source is used. Every file's origin is traceable.
Documentation
- Documentation index
- Architecture
- Branching and Release
- Version Matrix
- Testing
- Changelog
- Roadmap
- Provenance
Licence
MIT. MIT covers original code in this repository only. Third-party fragments are registered separately in Provenance.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- DM.DmProvider (>= 8.3.1.47463)
- Microsoft.EntityFrameworkCore.Relational (>= 10.0.0 && < 11.0.0)
NuGet packages (4)
Showing the top 4 NuGet packages that depend on Sharp.DM.EntityFrameworkCore:
| Package | Downloads |
|---|---|
|
SharpAbp.Abp.EntityFrameworkCore.DM
SharpAbp EntityFrameworkCore DM Module |
|
|
SharpAbp.Abp.DbConnections.DM
SharpAbp DbConnection Module |
|
|
SharpAbp.Abp.Data.SqlBuilder.DM
SharpAbp Data SqlBuilder DM Module |
|
|
SharpAbp.Abp.Dapper.DM
SharpAbp Dapper DM Module |
GitHub repositories
This package is not used by any popular GitHub repositories.