Object relationship mapping model with fixed database schema

Abstract

The invention relates to an object relationship mapping model with a fixed database schema, which can store object-oriented information modeling elements (such as entities, attributes, relationships and the like). The invention is suitable for specific programming environments in which the database table structure can not or is not allowed to change and the users must be allowed to store various user defined data after the software development is completed and the software is delivered to the user. Since the database model uses limited number of database tables, when an object in a new format needs storing, the user does not need to create a database table and only needs to insert a new record into the fixed database table. The model supports the object-oriented information modeling concept, such as entities, relationships, attributes and the like, thereby ensuring that the information model reflecting the real world can be smoothly mapped to the fixed database schema.

Description

Technical field [0001] The invention is a database model that can store object-oriented information modeling elements (such as entities, attributes, relationships, etc.). It is suitable for the specific programming environment where the database table structure cannot or is not allowed to be changed after the software development is completed and delivered to the user, but the user must be allowed to store various user-defined data. The database model uses a limited number of database tables to store persistent data that can meet the needs of most applications, and is particularly suitable for storing business data in workflow applications. Background technique [0002] In the implementation of software engineering projects, it is often necessary to store information models and instance data after data modeling in a relational database for application access. Because of the mismatch between the relational model and the object-oriented description language (design object model) a...

AI Technical Summary

Problems solved by technology

This creates the following problem: If the user's business data model changes frequently, or needs to develop software suitable for different fields that requires the user to customize the business data model, because the user does not know or can not determine in advance what kind of data the user needs to store And the data format, it is impossible to determine the database table structure at design time, and a new database table has to be created to store data in a new format-causing frequent changes in the database schema, which will inevitably require frequent corresponding modifications to the client software , otherwise the client cannot access its data because it does not know the new database schema

A small number of workflow engines, such as the famous open source jBPM, support business data itself, but the process variables they support are generally simple data types and are not related to each other. They do not support the concept of object-oriented information modeling. Such as entities, attributes, relationships, etc., so it is quite different from the data model generated during data modeling, and it is difficult to support application requirements such as complex query statistics on business data

More importantly, if this problem cannot be solved well, it will be difficult to realize the automatic generation of process task forms

Images