SET TRANSACTION ISOLATION LEVEL
Supporting "READ COMMITTED"
I am sorry for late replay.
Many table data has "delete" and "insert" of merge processing all day.
In the case of dirty read, referring to the "delete" processing table will cause data to be missing.
If "READ COMMITTED" is supported, data loss can be avoided.
Thanks for the request.
1. What is your use case? Do you have a mixed workload where updates happen alongside reads?
2. Will Read Committed Snapshot Isolation work for you?