We use gitter chat instead of discord.

Thanks for providing the details. I did some experiments myself. First, I created a simple .NET 6 WebApi project by following the steps from Getting Started and ended up with the following in Program.cs:

using DemoWebApiOnDotNet6.Data;
using DemoWebApiOnDotNet6.Resources;
using JsonApiDotNetCore.Configuration;
using Microsoft.EntityFrameworkCore;

var builder = WebApplication.CreateBuilder(args);

builder.Services.AddDbContext<AppDbContext>(options => options.UseNpgsql(
    "Host=localhost;Port=5432;Database=DotNet6Example;User ID=postgres;Password=postgres"));

builder.Services.AddJsonApi<AppDbContext>();

var app = builder.Build();

app.UseRouting();
app.UseJsonApi();
app.MapControllers();

using (var scope = app.Services.CreateScope())
{
    var dbContext = scope.ServiceProvider.GetRequiredService<AppDbContext>();
    dbContext.Database.EnsureDeleted();
    dbContext.Database.EnsureCreated();

    dbContext.People.Add(new Person { Name = "John Doe" });
    dbContext.SaveChanges();
}

app.Run();

For this demo API, I found the following:

NuGet reference to JADNC v4.2 on .NET 6 and EF Core 3.1 using PostgreSQL: works
NuGet reference to JADNC v4.2 on .NET 6 and EF Core 5 using PostgreSQL: works
NuGet reference to JADNC v4.2 on .NET 6 and EF Core 6 using PostgreSQL: runtime exception at application startup, because EF Core 6 has binary breaking changes

Next, I opened the solution from the master branch and found the following:

Switched to .NET 6 with EF Core 5 using PostgreSQL: all tests pass, despite nullability warnings during build, due to richer annotations and fixes in ASP.NET libraries
Switched to .NET 6 with EF Core 6 using PostgreSQL: 413/1729 tests fail, more nullability warnings because EF Core 6 got annotated too. After adding global AppContext.SetSwitch("Npgsql.EnableLegacyTimestampBehavior", true); as suggested here, still 66 failing tests.

Then I opened the solution from the 4.2 release branch and found the following:

Switched to .NET 6 with EF Core 3.1 using PostgreSQL: all tests pass
Switched to .NET 6 with EF Core 5 using PostgreSQL: all tests pass
Switched to .NET 6 with EF Core 6: 367/1859 tests fail, after setting EnableLegacyTimestampBehavior all tests succeed

Conclusion: Using .NET 6 seems to work fine, EF Core 6 has issues that we'll need to investigate. Note that all the above applies to a fresh start with an empty database, which is usually not very realistic. The release notes of PostgreSQL sum it up pretty well:

Npgsql 6.0 brings some major breaking changes and is not a simple in-place upgrade. Carefully read the breaking change notes below and upgrade with care.

Uh oh!

Version 5 for .NET 6 Support #1109

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions