{'fraction_non_alphanumeric': 0.02510460251046025, 'fraction_numerical': 0.0, 'mean_word_length': 5.970873786407767, '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}}
Incorporating object relationship notation (ORN) into SQL

Entity-Relationship (ER) Diagrams are widely used in information requirements analysis and database modeling and capture much knowledge of relationship semantics. Even more such knowledge is captured when ER Diagrams are extended with Object Relationship Notation (ORN). Unfortunately, however, much of the relationship semantics expressed in ER Diagrams are not directly translatable into the Structured Query Language (SQL), and, therefore, the implementation of these semantics in relational database management systems is made difficult. In this paper we demonstrate the feasibility and desirability of incorporating ORN into SQL to address this problem.