doc/WebSite/EF-Core-PostgreSql-Integration.md
Download the starter template with ASP.NET Core and Entity Framework Core to integrate PostgreSQL. Multi-page template with ASP.NET Core 2.x + .NET Core Framework + Authentication will be explained in this document.
Install the Npgsql.EntityFrameworkCore.PostgreSQL NuGet package to the *.EntityFrameworkCore project.
Some configuration and workarounds are needed to use PostgreSQL with ASP.NET Core and Entity Framework Core.
Replace YourProjectNameDbContextConfigurer.cs with the following lines
public static class PostgreSqlDemoDbContextConfigurer
{
public static void Configure(DbContextOptionsBuilder<PostgreSqlDemoDbContext> builder, string connectionString)
{
builder.UseNpgsql(connectionString);
}
public static void Configure(DbContextOptionsBuilder<PostgreSqlDemoDbContext> builder, DbConnection connection)
{
builder.UseNpgsql(connection);
}
}
Change the connection string to your PostgreSQL connection in *.Web.Mvc/appsettings.json. For example:
{
"ConnectionStrings": {
"Default": "User ID=postgres;Password=123;Host=localhost;Port=5432;Database=PostgreSqlDemoDb;Pooling=true;"
},
...
}
Starting from Npgsql 6.0, Npgsql changed the datetime handling, see the related issue. This causes an exception in AspNet Boilerplate's default template. So, you need to switch back to old behavior by following https://www.npgsql.org/efcore/release-notes/6.0.html#opting-out-of-the-new-timestamp-mapping-logic. Basically you need to set;
AppContext.SetSwitch("Npgsql.DisableDateTimeInfinityConversions", true);
Before you create the database, you should change the max length of the "Value" property of ApplicationLanguageText by adding the following lines to DbContext. This is because the max length of char in MS SQL and PostgreSQL are different.
public class PostgreSqlDemoDbContext : AbpZeroDbContext<Tenant, Role, User, PostgreSqlDemoDbContext>
{
public PostgreSqlDemoDbContext(DbContextOptions<PostgreSqlDemoDbContext> options)
: base(options)
{
}
// add these lines to override max length of property
// we should set max length smaller than the PostgreSQL allowed size (10485760)
protected override void OnModelCreating(ModelBuilder modelBuilder)
{
base.OnModelCreating(modelBuilder);
modelBuilder.Entity<ApplicationLanguageText>()
.Property(p => p.Value)
.HasMaxLength(100); // any integer that is smaller than 10485760
}
}
Remove all migration classes(include DbContextModelSnapshot) under *.EntityFrameworkCore/Migrations folder.
because Npgsql.EntityFrameworkCore.PostgreSQL will add some of its own configuration to work with Entity Framework Core.
Now it's ready to build database.
add-migration Initial_Migration command.update-database command.The PostgreSQL integration is now complete. You can now run your project with PostgreSQL.
Note: By default ABP's UnitOfWork uses IsolationLevel.ReadUncommitted but it is treated as IsolationLevel.ReadCommitted in PostgreSQL. This behavior can cause problems in some cases. For more information see.