EntglDb.Persistence.EntityFramework 0.9.1

EntglDb.Persistence.EntityFramework

Entity Framework Core persistence provider for EntglDb, supporting SQL Server, PostgreSQL, MySQL, and SQLite.

Features

• ✅ Multi-Database Support: Works with SQL Server, PostgreSQL, MySQL, and SQLite
• ✅ EF Core Integration: Leverage familiar EF Core patterns and migrations
• ✅ Transaction Support: ACID-compliant batch operations
• ✅ Conflict Resolution: Built-in Last-Write-Wins strategy
• ✅ Type-Safe: Strongly-typed entity models

Installation

dotnet add package EntglDb.Persistence.EntityFramework

Quick Start

SQLite

services.AddEntglDbEntityFrameworkSqlite("Data Source=entgldb.db");

SQL Server

services.AddEntglDbEntityFrameworkSqlServer(
    "Server=localhost;Database=EntglDb;Trusted_Connection=True;");

PostgreSQL

services.AddDbContext<EntglDbContext>(options =>
    options.UseNpgsql("Host=localhost;Database=EntglDb;Username=user;Password=pass"));
services.AddEntglDbEntityFramework();

MySQL

var serverVersion = ServerVersion.AutoDetect(connectionString);
services.AddEntglDbEntityFrameworkMySql(connectionString, serverVersion);

Migrations

Create and apply migrations using EF Core tools:

# Install EF Core tools
dotnet tool install --global dotnet-ef

# Add initial migration
dotnet ef migrations add InitialCreate --context EntglDbContext

# Update database
dotnet ef database update --context EntglDbContext

Custom Configuration

services.AddDbContext<EntglDbContext>(options =>
{
    options.UseSqlServer(connectionString);
    options.EnableSensitiveDataLogging(); // Dev only
    options.UseQueryTrackingBehavior(QueryTrackingBehavior.NoTracking);
});

services.AddEntglDbEntityFramework();

Performance Considerations

• Query Expressions: Evaluated in-memory. For production workloads with complex JSON queries, use PostgreSQL provider with JSONB support
• Indexing: Create indexes via migrations for better performance
• Batching: EF Core automatically batches multiple operations

Comparison with Other Providers

When to Use

Use EF Core when:

• You need multi-database support
• You want automated migrations
• Your team is familiar with EF Core patterns
• You're building an enterprise application

Use Direct SQLite when:

• You need maximum performance
• You're building a single-node app
• Database portability isn't required

Use PostgreSQL when:

• You need advanced JSON querying
• You're running in production with high load
• JSONB indexes are important

License

MIT