{'fraction_non_alphanumeric': 0.012958963282937365, 'fraction_numerical': 0.0, 'mean_word_length': 5.72463768115942, '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}}
POSTGRES revisited: a business application perspective

This paper describes changes to the POSTGRES Rule Manager that are required in order to guarantee sequential evaluation of POSTGRES rules based on assigned priority values. The proposed rule management algorithm relies on the identification of elementary rules and elementary user commands, and requires that all elementary rules be managed by tuple-level processing rather than by query-rewrite processing.