{'fraction_non_alphanumeric': 0.017994858611825194, 'fraction_numerical': 0.0, 'mean_word_length': 6.018018018018018, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Detecting Offline Transaction Concurrency Problems

When multiple instances of a database application (DBA) are executing concurrently, transactions from these instances interleave. Due to unintentional grouping of operations of the DBA into transactions, some interleavings of these transactions may cause offline concurrency problems. Although these problems are analogous to lost update, dirty read, non-repeatable read, and phantom problems, the concurrency controller of a DBMS cannot ensure ACID properties because from the DBMS's point of view the transactions involved in the offline concurrency problems are executed successfully. This paper gives the enumeration of patterns of interleaving of operations which identify potential offline concurrency problems in a DBA.