{'fraction_non_alphanumeric': 0.019745222929936305, 'fraction_numerical': 0.0006369426751592356, 'mean_word_length': 5.284, '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}}
A real-time object-oriented data model and prototype implementation

Real-time databases are different from conventional databases in that they have timing constraints on data and on transactions upon the data. The timing constraints of data require that the current status of the real world must be close enough to the state represented by the contents of the database. The timing constraints of transactions are typically expressed in the form of deadline which indicates a certain time in the future by which a transaction must be completed. Conventional data models can not be directly applied to describe the conceptual data model of a real-time database, since there is no mechanism to deal with the representation of timing constraints. A real-time data model should simultaneously satisfy many goals. It should clearly and concisely provide support for specifying timing constraints on data and transactions, semantics of real-time data and real-time transactions, concurrency control mechanisms, and transactions scheduling policies to meet the timing constraints defined by the real-time applications. This paper presents a real-time object-oriented data model and its use in designing real-time extensions to the DB4O database management system. This data model supports expression of time-constrained data, time-constrained transactions, concurrency control mechanisms, and transactions scheduling policies. It also can be integrated easily in existing object-oriented method and permits automatic code generation of all the real-time code of an application.