Computed column error when SetOutputIdentity is set to true during BulkInsert about efcore.bulkextensions HOT 5 CLOSED

Yes I can.
The problem is in QueryOutputTable method:
context.Set<T>().FromSql<T>(SqlQueryBuilder.SelectFromOutputTable(this));
where OutputTable does not have CalculatedColumn so Query can not Select it but Entity expects it for mapping.
EDIT:
After little more digging I have found that the error if happening even without CalculatedColumn.
Whenever SetOutputIdentity is True and not all columns are being selected either by explicitly selecting with PropertiesToInclude or excluding some with PropertiesToExclude.
This cause mismatch between Select and Entity.

I will see to fix it soon.
I think best solution is that Output should Select all Columns that have EntityProperty, even those that were not Inserted.

from efcore.bulkextensions.

Thanks, I am inserting more than 9 million records (on a daily basis) and I really look forward to use BulkInsert. Regular EF Core takes more than 20mins even with doing things in Parallel.

from efcore.bulkextensions.

Fixed and NuGet 2.1.2 published.
Also ComputedColumns are now automatically excluded so it's not required to use PropertiesToExclude for their explicit exclusion.

from efcore.bulkextensions.

Using 2.1.9 version.

Does not work with GeneratedValue Data Annotation, or FluentAPI.

Data Annotation
public class MyClass {
[DatabaseGenerated(DatabaseGeneratedOption.Identity)]
public MyProp { get; set; }
}

FluentAPI
modelBuilder.Entity<My_Table>().Property(p => p.MyProp).ValueGeneratedOnAddOrUpdate();

from efcore.bulkextensions.

Submitted as a new issue

from efcore.bulkextensions.