hi
// https://www.npgsql.org/efcore/release-notes/6.0.html#opting-out-of-the-new-timestamp-mapping-logic
AppContext.SetSwitch("Npgsql.EnableLegacyTimestampBehavior", true);
hi
You can move the business code into a service, and then use this service in the application service and Received method.
Thanks, we will check this.
We will fix it as soon as possible.
If it still doesn't solve the problem, how to reproduce it with a new project?
liming.ma@volosoft.com
after adding "IsActive" property to abpusers and ran the dbmigrator project, getting the attached error.
Did you add new migrations? Will the error still occur if change the connection string to a new database?
You can also try to delete all migrations and create a new one to test.
If it still doesn't solve the problem, how to reproduce it with a new project?
ApplicationService is mainly designed for UI, and it also exposes http endpoints. So there is an trust problem.
You don't have this problem if you use domain services in your code.