Upgrade ZERO from v7.2.0 to v 8.0.0 failed with EditionFeatureSetting cannot be mapped to a table #8074

trendline created 5 years ago

I am upgrading my application from v 7.2.0 to v 8.0.0, the soulution builded successed, but when run the start up project, below exception occurred InvalidOperationException: The entity type 'EditionFeatureSetting' cannot be mapped to a table because it is derived from 'FeatureSetting'. Only base entity types can be mapped to a table. What is going wrong?

4 Answer(s)

0

trendline created 5 years ago

It seems cuased by this breaking changes on EF Core 3.0 when call ChangeAbpTablePrefix on model creating.

Can we remove below code when invoke the ChangeAbpTablePrefix method? SetTableName<TenantFeatureSetting>(modelBuilder, prefix + "Features", schemaName); SetTableName<EditionFeatureSetting>(modelBuilder, prefix + "Features", schemaName);
0

maliming created 4 years ago
Support Team

see https://github.com/aspnetboilerplate/aspnetboilerplate/issues/4959
0

trendline created 4 years ago

As you have removed the related code, why it still occurred this issue? I checked the source code, the latest code not remove the related code, any reason rollback it again?
1

maliming created 4 years ago
Support Team

Abp 5.1 will solve this problem, but 5.1 has not been released yet.

You can look at the temporary solution Https://github.com/aspnetboilerplate/aspnetboilerplate/issues/4959#issuecomment-546184336

Have an answer to this question? Log in and write your answer.