HistoryRepository should return filtered list of applied migrations where the list of migrations in code serves as a baseine.

[voroninp]

Repo to reporduce: https://github.com/voroninp/EfMultipleContextsSameHistoryTable

When working with migrations, active database context should provide a list of migrations defined in code, and this list should be the baseline.

By default the call to GetAppliedMigrations should return only the migrations which belong to the active context.

Currently, HisroryRepository just returns the list of migrations from history table.

Yet migrations history table can be reused by multiple contexts. (At least I could not find the warning in the documentation that each context should have its own history table.)

---

Alternatively, I'd propose that each migration withing the same history contains some fixed id, so it's easy to understand which context it belongs to.

[DbContext(typeof(Ctx2))]
[MigrationHistory(id: "abc-def")]
[Migration("20240730133611_Bar", historyId: )]

and

[DbContext(typeof(Ctx2))]
[MigrationHistory(id: "abc-def.")]
partial class Ctx2ModelSnapshot : ModelSnapshot

This HisotoryId should be the column in __EFMigrationsHistory table.

[AndriySvyryd]

IHistoryRepository is a low-level service, so it's by-design that it returns rows for all contexts. But we should filter them in Database.GetAppliedMigrationsAsync and Database.GetPendingMigrationsAsync

@ErikEJ FYI, in case you have thoughts about this

[ErikEJ]

@AndriySvyryd I have removed my migrations tooling in case that's what you are referring to?

https://github.com/ErikEJ/EFCorePowerTools/wiki/Migrations-Tool

[AndriySvyryd]

Oh, didn't realize that

[ErikEJ]

It is a quite recent decision. Never heard from anyone missing it 😅