Issue with upsert based on database generated Identity

As i am trying to use the Upsert with PostgreSql. I am getting the exception as I am doing upsert over database generated Identity. This exception is being introduces in v2.0.1 with comments :

Explicitly throwing an exception when using identity keys as upsert match columns (since it wouldn’t have worked correctly anyway)

In my use case i am not allowed to go away with database generated option hence i tried to run it with commenting with this code :

  //if (joinColumns.All(p => p.ValueGenerated != ValueGenerated.Never))
            //    throw new InvalidMatchColumnsException();

And this worked 😃

Hence i am exploring the option where we can allow user to flag this condition out and has the flexibility of allowing the database generated option

[artiomchi]

So I might not agree with upserting on identity keys (there are much better ways to do that if all you want to do is update an existing entry by PK), but I will agree that it’s not a bad idea to add that as an option… There might be cases when it would actually make sense anyway (IDENTITY_INSERT in MSSQL).

I’ve got basic support for it added just now, and it should go live with the next release.

To enable it, just call .AllowIdentityMatch() on the UpsertCommandBuilder

[Kronos11]

Thanks for adding in this feature. as @jlucaspains mentions it’s very useful for disconnected entities.