What difficulties can arise when using the Read Committed isolation level in transactions?

The Read Committed isolation level guarantees that a transaction only sees committed data, preventing dirty reads. However, the following issues may still occur:

• Non-repeatable Read: if within a single transaction, the same data is queried again, it may have changed if another transaction updates and commits it.
• Phantom Reads: when re-executing a query with a condition, new rows added by other transactions may appear.

This can lead to data inconsistency in business logic if the application does not account for such changes. To address this, stricter isolation levels (such as Repeatable Read) are sometimes used, or additional locking logic is implemented.