mysql>  SELECT id, NDB$OP_TYPE, NDB$CFT_CAUSE FROM employee$EX; +-------+-------------+-------------------+ | id | NDB$OP_TYPE | NDB$CFT_CAUSE | +-------+-------------+-------------------+ ... | 998 | READ_ROW | TRANS_IN_CONFLICT | | 999 | READ_ROW | TRANS_IN_CONFLICT | | 1000 | READ_ROW | TRANS_IN_CONFLICT | ... +-------+-------------+-------------------+ NDB Cluster Release Notes Read tracking is performed on the basis of existing rows only. A read based on a given condition track conflicts only of any rows that are  found  and not of any rows that are inserted in an interleaved transaction. This is similar to how exclusive row locking is performed in a single instance of NDB Cluster. Changes in NDB Cluster releases are documented separately from this reference manual; you can find release notes for the changes in each NDB Cluster 8.0 release at NDB 8.0 Release Notes. You can obtain release notes for older versions of NDB Cluster from NDB Cluster Release Notes. 23.7 NDB Cluster Release Notes 4654