Updated Version

[onexkacpermarcisz]

Hello everyone,

I've just updated my project from .NET 6 to .NET 8 along with PiranhaCMS from 10.2.0 to 12.0.0. Now I'm encountering an issue at runtime related to the IdentityPostgreSQLDb context.

The error is as follows:

InvalidOperationException: An error was generated for warning 'Microsoft.EntityFrameworkCore.Migrations.PendingModelChangesWarning': The model for context 'IdentityPostgreSQLDb' has pending changes.

I attempted to generate a migration using the following command:

Add-Migration EFUpdate -Context IdentityPostgreSQLDb

However, I received a connection error (tried to connect to SOME IP) and I'm not sure how to make it use my local database and than on production server.

Could someone please help me figure out how to properly configure the context so that migrations run against my local setup?

Thanks in advance for any guidance!

[tommy-bear]

Hi.
Today I faced same issue when trying to run fresh copy o PiranhaCMS with PostgreSQL database.
MS introduced breaking change in EF.Core 9. It seems that only packages references was updated without proper change in codebase.

Change following lines:

    options.UseEF<PostgreSqlDb>(db => db.UseNpgsql(connectionString));
    options.UseIdentityWithSeed<IdentityPostgreSQLDb>(db => db.UseNpgsql(connectionString));

to something like this:

options.UseEF<PostgreSqlDb>(db =>
  {
      db.UseNpgsql(connectionString);
      db.ConfigureWarnings(w => w.Ignore(RelationalEventId.PendingModelChangesWarning));
  });
  options.UseIdentityWithSeed<IdentityPostgreSQLDb>(db =>
  {
      db.UseNpgsql(connectionString);
      db.ConfigureWarnings(w => w.Ignore(RelationalEventId.PendingModelChangesWarning));
  });

I face also issues with DateTime columns despite fact that ctor of PostgreSqlDb is calling proper switch.
I had to call it once again in Program.cs
AppContext.SetSwitch("Npgsql.EnableLegacyTimestampBehavior", true);

[onexkacpermarcisz]

Thanks for the tip! It will indeed suppress the startup error, but I’ll be masking any schema mismatches and will likely run into issues down the road. I appreciate the guidance!

[tommy-bear]

Here's a solution without suppressing warnings:

1. Started with setting up proper connection string to my local PostgreSql database in appSettings.Development.json
2. I've added reference to Microsoft.EntityFrameworkCore.Design within my project
3. I've needed to make explicit reference to MigrationsAssebly in Program.cs (default is Piranha.Data.EF.PostgreSql) for both PostgreSqlDB and IdentityPostgreSqlDb

options.UseEF<PostgreSqlDb>(db =>
        {
            db.UseNpgsql(connectionString, op =>
            {
                op.MigrationsAssembly(Assembly.GetExecutingAssembly().GetName().Name);
            });
        });
    options.UseIdentityWithSeed<IdentityPostgreSQLDb>(db =>
    {
        db.UseNpgsql(connectionString, op =>
        {
            op.MigrationsAssembly(Assembly.GetExecutingAssembly().GetName().Name);
        });
    });

4. Then I fired in console dotnet ef migrations add InitialMigration --context PostgreSqlDb - that created schema for pages, sites, blocks etc.
5. Then I fired in console dotnet ef migrations add IdentityInitialMigration --context IdentityPostgreSqlDb - that created schema for Identity

That solution adds new directory Migrations with migrations & snapshots for both of contexts.

[onexkacpermarcisz]

This completely solves the problem—thank you!