"prashanthbudi" 'in aktiviteleri

Hi,

The ConcurrencyStampshould never be null, because ABP will set it up internally. I'm wondering why your database value is NULL.
See: https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.EntityFrameworkCore/Volo/Abp/EntityFrameworkCore/AbpDbContext.cs#L533

I think you need to check your database table.

• https://github.com/npgsql/efcore.pg/issues/884#issuecomment-607546356
• https://stackoverflow.com/questions/73563589/system-invalidcastexception-c

Understood that ABP handles inserting the values and ConcurrencyStamp would never be null. But the columns allows null as they are nullable fields. so reading those values should not cause any issue right?

Could you suggest any workaround, instead of manually find all the tables which have null values for these columns and update.

Hi,

The ConcurrencyStamp should not be NULL by default.

You can try to manually assign values to ConcurrencyStamp in the database and test again.

Thanks for the suggestions. I was just wondering anything got changed in V7.4.2, because it was working fine with null values in previous version and its happening for all the tables with concurrencystamp and extraproperties column. To update manually is not valid solution considering there are so many tables with those columns.

Could you suggest please.