efcore | EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, upda | Object-Relational Mapping library

I'm using efcore and I scaffolded from an existing database, but I forgot to make an initial migration when I did that so it picked up my new model. I decided that I wanted to keep them separate so I removed the migration, deleted the snapshot, and now every time I create another migration, it still has the new model in it.

On top of this, using dotnet ef migrations list will list pending migrations that no longer exist. If I do dotnet ef database update they will get 'migrated` and show up in __MigrationHistory, but again, they don't actually exist in the directory.

I've tried creating the files again, going as far as adding the class names to the files, doing a dotnet ef migrations remove, but I still have the same issue. It will delete the files, tell me everything is rolled back, but then the files will still be listed as pending, the database snapshot will still contain the new table (that doesn't exist) if I do any future migrations.

Not really sure how to proceed. Everything I've read says that if I delete the snapshot and migrations, it will create a fresh snapshot, but it doesn't seem to do that. Is this stuff cached somewhere locally that I can clear out?

To visualize - naively - if I would like to complete such an operation, I would probably use the code below.

Assume that dbContext and dbContext.Entries are of type DbContext (PostgreSQL) and DbSet respectively.

So I'm running into a rather odd issue here. I've got a PostgreSQL 14 server and I'm using the Npgsql Entity Framework Core provider to access it. If I have an Entity Framework Core entity that contains a date as a NodaTime Instant type (which becomes timestamp with time zone in the database) and try to project that via .InZone(timeZone).LocalDateTime, I run into 3 situations.

Actual example query would be something like this:

I'm trying to create a docker-compose script to fire a stack with a PostgreSql database and an ASP.NET Core 6 Web API. To test the scenario, I've created a new ASP.NET Core 6 Web API using the default template. I have then added NuGet package Npgsql (6.0.3), and a sample controller which just queries the DB engine version, e.g.:

I came across this error when modifying a DB first project (using fluent migrator) and scaffolding the EF context to generate models. I have reproduced it by making a code-first simplification. This means that I can't accept answers that suggest modifying the annotations or fluent configuration, because this will be deleted and recreated on the next migration and scaffold.

The simplified idea is that a device has:

• many attributes
• many histories representing changes to the device over time
  • each history entry has an optional location

IOW you can move a device around to locations (or no location) and keep track of that over time.

The code-first model I came up with to simulate this is as follows:

I have the following configuration for which I want to provide some seed values.

The below LINQ query works perfectly fine in EF6 world where the whole query seems to be evaluated at the server (checked with SQL Profiler) but fails in EFCore6.

I get on creating Migration some Warnings like this one:

The foreign key property 'AppUserClaim.UserId1' was created in shadow state because a conflicting property with the simple name 'UserId' exists in the entity type, but is either not mapped, is already used for another relationship, or is incompatible with the associated primary key type. See https://aka.ms/efcore-relationships for information on mapping relationships in EF Core.

It applies to all entities with AppUser navigation property. Other navigation properties has no warning.

I juste upgraded my web api to .net6 using EFCore and NPGSQL (Postgres). I had to Set a Switch for my code to work: AppContext.SetSwitch("Npgsql.EnableLegacyTimestampBehavior", true);

Now EFCore Creates my DateTime fields to 'timestamp with time zone' which breaks everything.

How can I get the old 'timestamp without time zone' for DateTime Types?

Should I remove the LegacyTimestamp switch?

Thanks for your help!