Is it possible to turn off concurrency violation checking?

Description

Using the SQL Programmability Provider, I'm trying to use it for updates to existing rows. I only have a subset of columns in the table that need updating, and don't need to load in data first. The way I'm doing it currently is:

1. Create a new data row with blank values.
2. Call AcceptChanges()
3. Modify the appropriate fields with the values to update.
4. Call Update().

The issue is that the generated SQL also adds in where clauses to ensure that all the other values are the same as before, which obviously doesn't work since it expects all values to be blank. Is it possible to turn this check off for the dynamically generated SQL? The only other alternatives that I can see are:

1. Load in the data before performing the update - not needed in my scenario and will greatly increase the number of SQL calls.
2. Switch to hand-crafted update statements, either using a custom data adapter or using the SQL Command Provider.

Start by tracing the SQL Programmability Provider's generated SQL from the DataRow Update() path, focusing on how AcceptChanges() and original column values become WHERE clauses. Compare this with the SQL Command Provider behavior and determine where an opt-out could be exposed. Done means the provider supports updates without requiring unchanged values for every column, with coverage for the described partial-row scenario.