Roohallah Alizadeh

This feature could be implemented similarly to ExecuteDelete and ExecuteUpdate. The proposed API could be called ExecuteInsert and would allow server-side INSERT ... SELECT operations without materializing entities in memory....

@DocSvartz When using the overload to modify a record, the record is not changed because records are immutable. ` public static TDestination Adapt(this TSource source, TDestination destination)` Do you think...

Ok, that's right. it's the best solution!

In my opinion, the signature `public static TDestination Adapt(this TSource source, TDestination destination) ` implies that the data from `source` is be mapped onto `destination`. When `destination` is immutable and...

@stagep Your idea is also Correct. If the `destination` is immutable, what does the following line do, and what problem would arise if it were removed? `source.Adapt(destination);` When a line...

@DocSvartz You are absolutely right. I had not fully understood the correct way to use this method. I apologize for taking up your time.

@DocSvartz Although the ambiguity has largely been resolved for me, I still welcome the suggestion of having two methods.

@DocSvartz @stagep I think that using suitable parameter names can remove ambiguity. In the following method, based on the name of the second parameter (`destination`), it is expected that this...

@DocSvartz I would be happy to see your opinion.

@DocSvartz Not just for testing. In my opinion, in most cases, defining the mapping configuration locally in the code rather than in a global configuration makes the code clearer. Do...