Should the absense of migration hisotry table it be logged as error?

[voroninp]

Question

When the database is completely new, when migrating EF tries to read from the migration history table and logs the following error:

Failed executing DbCommand (4ms) [Parameters=[], CommandType='Text', CommandTimeout='30'] SELECT migration_id, product_version FROM public."__EFMigrationsHistory" ORDER BY migration_id;

But it's a valid case, isn't it? Should not this error be logged with a different level?

Your code

Stack traces

Verbose output

EF Core version

9.0.0

Database provider

No response

Target framework

No response

Operating system

No response

IDE

No response

[roji]

@voroninp please fill in the above questions, specifically which database provider are you using...