C#•7d ago

.NET 10 EF Core Postgres Migrations always Fail, __MigrationsHistory doesn't get filled

I'm so frustrated, I've already wasted the last hour trying to fix this.

So I migrate the DB at the beginning like this:

        await using (AsyncServiceScope scope = bot.Services.CreateAsyncScope())
        {
            try
            {
                await using PostgresDbContext db = scope.ServiceProvider.GetRequiredService<PostgresDbContext>();
                
                await db.Database.EnsureCreatedAsync();

                IEnumerable<string> pendingMigrations = await db.Database.GetPendingMigrationsAsync();
                
                if (pendingMigrations.Any())
                {
                    Console.WriteLine("Applying pending migrations...");
                    await db.Database.MigrateAsync();
                    Console.WriteLine("Migrations applied successfully.");
                }
                else
                {
                    Console.WriteLine("No pending migrations found.");
                }
                
            }
            catch (Exception ex)
            {
                ILogger<StartCommand> logger = scope.ServiceProvider.GetRequiredService<ILogger<StartCommand>>();
                logger.LogError(ex, "An error occurred while migrating or initializing the database.");
            }
        }

        await using (AsyncServiceScope scope = bot.Services.CreateAsyncScope())
        {
            try
            {
                await using PostgresDbContext db = scope.ServiceProvider.GetRequiredService<PostgresDbContext>();
                
                await db.Database.EnsureCreatedAsync();

                IEnumerable<string> pendingMigrations = await db.Database.GetPendingMigrationsAsync();
                
                if (pendingMigrations.Any())
                {
                    Console.WriteLine("Applying pending migrations...");
                    await db.Database.MigrateAsync();
                    Console.WriteLine("Migrations applied successfully.");
                }
                else
                {
                    Console.WriteLine("No pending migrations found.");
                }
                
            }
            catch (Exception ex)
            {
                ILogger<StartCommand> logger = scope.ServiceProvider.GetRequiredService<ILogger<StartCommand>>();
                logger.LogError(ex, "An error occurred while migrating or initializing the database.");
            }
        }

        await using (AsyncServiceScope scope = bot.Services.CreateAsyncScope())
        {
            try
            {
                await using PostgresDbContext db = scope.ServiceProvider.GetRequiredService<PostgresDbContext>();
                
                await db.Database.EnsureCreatedAsync();

                IEnumerable<string> pendingMigrations = await db.Database.GetPendingMigrationsAsync();
                
                if (pendingMigrations.Any())
                {
                    Console.WriteLine("Applying pending migrations...");
                    await db.Database.MigrateAsync();
                    Console.WriteLine("Migrations applied successfully.");
                }
                else
                {
                    Console.WriteLine("No pending migrations found.");
                }
                
            }
            catch (Exception ex)
            {
                ILogger<StartCommand> logger = scope.ServiceProvider.GetRequiredService<ILogger<StartCommand>>();
                logger.LogError(ex, "An error occurred while migrating or initializing the database.");
            }
        }

        await using (AsyncServiceScope scope = bot.Services.CreateAsyncScope())
        {
            try
            {
                await using PostgresDbContext db = scope.ServiceProvider.GetRequiredService<PostgresDbContext>();
                
                await db.Database.EnsureCreatedAsync();

                IEnumerable<string> pendingMigrations = await db.Database.GetPendingMigrationsAsync();
                
                if (pendingMigrations.Any())
                {
                    Console.WriteLine("Applying pending migrations...");
                    await db.Database.MigrateAsync();
                    Console.WriteLine("Migrations applied successfully.");
                }
                else
                {
                    Console.WriteLine("No pending migrations found.");
                }
                
            }
            catch (Exception ex)
            {
                ILogger<StartCommand> logger = scope.ServiceProvider.GetRequiredService<ILogger<StartCommand>>();
                logger.LogError(ex, "An error occurred while migrating or initializing the database.");
            }
        }

When I ran it locally it always worked. I had multiple migrations so I thought maybe that was the issue. It seemed like the

Calender

Calender

Calender

Calender Table was added multiple times. But removing all Migrations and adding a Single one didn't change anything.

When running it completely new using my docker compose it threw the exceptions... You can gladly check my repo here and run it yourself: https://github.com/baltermia/study-companion

The error is attached as a file (discord did that automatiacally somehow)

Any help will be well appereciated

GitHub

GitHub - baltermia/study-companion

Contribute to baltermia/study-companion development by creating an account on GitHub.

BalteOP•12/14/25, 7:54 PM

Ok seems discord didn't attach my logs... Here they are again:

BalteOP•12/14/25, 7:54 PM

message.txt4.74KB

Bytes Don’t Bite•12/14/25, 7:56 PM

Did you manually create the Calender table?

BalteOP•12/14/25, 7:56 PM

I do complete reinstall with docker compose down --volumesdocker compose down --volumes, db should be deleted then right? Or maybe I'm messing this step up already...

BBytes Don’t Bite Did you manually create the Calender table?

BalteOP•12/14/25, 8:02 PM

What's weird is all Tables get created in the end, even __EfMigrationsHistory__EfMigrationsHistory gets created, but not filled. And then it starts adding tables from the beginning. When I look into the generated Migration code, the

Calender

Calender

Table is the first. Why would it get created twice?

BalteOP•12/14/25, 8:03 PM

The app completely works. But it just throws that exception. I just logg it rn but still seems not really nice to just let it throw on each start, no?

Bytes Don’t Bite•12/14/25, 8:07 PM

Just call MigrateAsync. It will create the database and apply pending migrations if necessary

BBytes Don’t Bite Just call MigrateAsync. It will create the database and apply pending migrations...

BalteOP•12/14/25, 8:08 PM

I mean I'm not doing anything much else, just some checks beforehand but nothing special really if you look at the code...

Bytes Don’t Bite•12/14/25, 8:12 PM

Yeah I mean you can remove this stub:

await db.Database.EnsureCreatedAsync();

IEnumerable<string> pendingMigrations = await db.Database.GetPendingMigrationsAsync();

await db.Database.EnsureCreatedAsync();

IEnumerable<string> pendingMigrations = await db.Database.GetPendingMigrationsAsync();

Just use MigrateAsync() and see if it works.

Bytes Don’t Bite•12/14/25, 8:13 PM

MigrateAsync always creates database if it doesn't exist and then applies pending migrations

BalteOP•12/14/25, 8:14 PM

okay i'll try

BBytes Don’t Bite MigrateAsync always creates database if it doesn't exist and then applies pendin...

BalteOP•12/14/25, 8:19 PM

Yea it's still the same error unfortauntely

Bytes Don’t Bite•12/14/25, 8:21 PM

You can execute into the postgres service and check the state of your database
Use \d to see the relations

Bytes Don’t Bite•12/14/25, 8:23 PM

If EF Core applied a migration, it would have been tracked in migration history in which case it won't apply that same migration

BBytes Don’t Bite If EF Core applied a migration, it would have been tracked in migration history ...

BalteOP•12/14/25, 9:17 PM

It's 100% a complete reinstall.. Idk man I'll just leave it like this for the moment. I dont have more time to waste.... project is due on tuesday

Thanks for the help!

Keswiik•12/15/25, 1:15 AM

@Balte

You don't need to check for pending migrations.
If your DB, schema, and migrations are out of sync, it could be causing these problems.

All of my side projects using a database just call await dbContext.Database.MigrateAsync()await dbContext.Database.MigrateAsync().

Show your DBContext class

Mayor McCheese•12/15/25, 3:56 AM

Iirc on a recent project I had the same issue, I didn't look at the table contents, maybe I should

Jimmacle•12/15/25, 6:37 AM

EnsureCreated is not compatible with migrations at all

Jimmacle•12/15/25, 6:37 AM

You need to call one of the Migrate methods instead

KKeswiik <@281462812281274368> 1. You don't need to check for pending migrations. 2. If ...

Jimmacle•12/15/25, 6:39 AM

This is the answer, this is the only line you need to check for and apply pending migrations at runtime including creating the database if it doesn't exist

JJimmacle EnsureCreated is not compatible with migrations at all

Mayor McCheese•12/15/25, 8:58 AM

I used ef tools to dotnet ef update-database or whatever

JJimmacle This is the answer, this is the only line you need to check for and apply pendin...

BalteOP•12/15/25, 10:49 AM

Thanks I will give it a try

MMayor McCheese I used ef tools to dotnet ef update-database or whatever

BalteOP•12/15/25, 10:49 AM

I want the App to update the DB automatically tho, so users can simply pull the latest docker image and the rest is done on its own

BalteOP•12/15/25, 10:52 AM

await using (AsyncServiceScope scope = bot.Services.CreateAsyncScope())
{
    try
    {
        await using PostgresDbContext db = scope.ServiceProvider.GetRequiredService<PostgresDbContext>();

        await db.Database.MigrateAsync();
    }
    catch (Exception ex)
    {
        ILogger<StartCommand> logger = scope.ServiceProvider.GetRequiredService<ILogger<StartCommand>>();
        logger.LogError(ex, "An error occurred while migrating or initializing the database.");
    }
}

await using (AsyncServiceScope scope = bot.Services.CreateAsyncScope())
{
    try
    {
        await using PostgresDbContext db = scope.ServiceProvider.GetRequiredService<PostgresDbContext>();

        await db.Database.MigrateAsync();
    }
    catch (Exception ex)
    {
        ILogger<StartCommand> logger = scope.ServiceProvider.GetRequiredService<ILogger<StartCommand>>();
        logger.LogError(ex, "An error occurred while migrating or initializing the database.");
    }
}

This is now the only code that is being run, the issue still persists.

MMayor McCheese Iirc on a recent project I had the same issue, I didn't look at the table conten...

BalteOP•12/15/25, 10:52 AM

Did you find any way to fix it only using code? Instead of manual commands

BBalte Did you find any way to fix it only using code? Instead of manual commands

Mayor McCheese•12/15/25, 11:16 AM

Nah I've been busy with other non hobby projects

Mayor McCheese•12/15/25, 11:17 AM

It works as is for now, so I'll fix it the next database update

BBalte I'm so frustrated, I've already wasted the last hour trying to fix this. So I m...

TeBeCo•12/15/25, 11:59 AM

for clarification of what was said
EnsureCreatedAsyncEnsureCreatedAsync will completly bypass all migration and directly oneshot the DB
MigrateAsyncMigrateAsync already internally check the current code and apply all the missing delta

so they play complete opposite role

TeBeCo•12/15/25, 12:00 PM

the question is ... do you have this issue on a long running DB, or you have that from a fresh database ?

TeBeCo•12/15/25, 12:00 PM

because running both will potentially corrupt the ef history stored on the DB and probably crash MigrateAsyncMigrateAsync indicating that stuff are already existing

TeBeCo•12/15/25, 12:01 PM

EnsureCreatedAsyncEnsureCreatedAsync is NOT incremental
MigrateAsyncMigrateAsync is incremental

TeBeCo•12/15/25, 12:01 PM

which means it created the target and lost "source control"
but then try to re-apply diff from the start

TeBeCo•12/15/25, 12:01 PM

and if that diff tell to create intermediate object ... it's gonna do that as long as no validation rule are violated

TeBeCo•12/15/25, 12:02 PM

    catch (Exception ex)
    {
        ILogger<StartCommand> logger = ....<ILogger<StartCommand>>();
        logger.LogError(ex, "An error occur....");
    }

    catch (Exception ex)
    {
        ILogger<StartCommand> logger = ....<ILogger<StartCommand>>();
        logger.LogError(ex, "An error occur....");
    }

TeBeCo•12/15/25, 12:02 PM

this block also mean:

TeBeCo•12/15/25, 12:02 PM

"hey if there's an anomre ... just log and continue running, trust me bro(tm)"

TeBeCo•12/15/25, 12:03 PM

which mean that if you start adding more and more migration and this never update the DB

TeBeCo•12/15/25, 12:03 PM

your code is not aware of that

TeBeCo•12/15/25, 12:03 PM

and the db schema is NOT the one from the app

TeBeCo•12/15/25, 12:03 PM

so unless you properly have rollover non-breaking change code, you're going to hit a very very bad data corruption as soon as the first migration fails

TeBeCo•12/15/25, 12:04 PM

last but not least ....

TeBeCo•12/15/25, 12:04 PM

are you pointing at a DEV / QA db when you dev locally ? or your own local database ?

TeBeCo•12/15/25, 12:04 PM

because as I can see your code, if you have the same connectionstring locally than on ANY OTHER SHARED env, you're going to take that application down and corrupt the DB as well

TeBeCo•12/15/25, 12:05 PM

all your local run will mutate the DB schema of an already running app

TeBeCo•12/15/25, 12:05 PM

and that app will crash

TeBeCo•12/15/25, 12:05 PM

---
please concider adding .idea/.idea/ to your

.gitignore

.gitignore

BTW

TTeBeCo > "hey if there's an anomre ... just log and continue running, trust me bro(tm)"

BalteOP•12/15/25, 12:55 PM

Yes that is the very intended purpose. I know it's very bad to just forget about it but I need this to work by tomorrow

When I'm running locally, I'm also running the postgres in a container, but the app itself runs in rider. You can see it in the repo it's the docker-compose.dev.ymldocker-compose.dev.yml file.

I do not have the EnsureCreatedEnsureCreated in the code anymore. I will test this on a complete new machine though in the evening. Maybe I'm messing up something when I try to delete the existing containers, and somehow it still persists soem data...
Thanks for the help.

TTeBeCo --- please concider adding `.idea/` to your `.gitignore` BTW

BalteOP•12/15/25, 12:57 PM

Yes will do

BBalte Yes that is the very intended purpose. I know it's very bad to just forget about...

TeBeCo•12/15/25, 1:25 PM

Yes that is the very intended purpose. I know it's very bad to just forget about it but I need this to work by tomorrow

just add throw;throw; so the app crash, easy

When I'm running locally, I'm also running the postgres in a container, but the app itself runs in rider. You can see it in the repo it's the docker-compose.dev.yml file

so it's not shared by anything else ? that's fine then, you should never apply a migration onto another environment if the app is not designed to receive the app with the source that goes with it

.NET 10 EF Core Postgres Migrations always Fail, __MigrationsHistory doesn't get filled

Similar Threads

Similar Threads

Similar Threads