Igor Tkachev

@viceroypenguin, should we use then `UpdateWhenMatchedWith(For)` instead of `UpdateWhenMatched` to indicate that the expression is not completed?

Another "consistent" way - we use MS (3rd) option and implement the similar extensions for our Insert/Update methods.

Ok. Just add a compatibility flag.

/azp run test-all

/azp run test-all

We do not need to change default behavior. It should be possible to map to both TimeSpan and int64 depending on object property/field type.

> > but we also could have a timespan inside of a where wich is not mapped to field in the database. > > And you calculate timespans by subtracting...

Is this specific database feature?

We can add a database specific option.

We already have it for other types. See `Expressions.cs` line 555.