SQLiteConstraintException during Room insert retries

Idempotency in Room Database Operations

When implementing a retry mechanism for database writes in Android Room, ensuring idempotency is critical to prevent duplicate entries or application crashes. The goal is to handle scenarios where a write operation may have partially succeeded or been interrupted, leading to a retry of the same data payload.

Using OnConflictStrategy.REPLACE can resolve conflicts but may lead to data loss if the entity being inserted contains only a subset of columns, as the existing row is deleted and replaced. Conversely, OnConflictStrategy.IGNORE prevents the exception but provides no feedback on whether the write was successful or skipped due to a constraint violation.

• How does the choice between IGNORE and REPLACE impact the integrity of unrelated columns in a partial entity update?
• Is there a documented way to detect if an insert was ignored due to a conflict versus a different failure without triggering a SQLiteConstraintException?