Compiler-Driven Object Version History Access at Runtime
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing programming technologies lack efficient mechanisms for automatically maintaining and accessing version history of data entities at runtime without requiring developer intervention.
Innovation Solution
A compiler is developed to generate code that automatically creates and maintains version history for data entities, allowing access to prior versions through a versioned query construct, and supports versioned data entity access instructions, including version references and update instructions, which are integrated into the programming language.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If automated version history management is implemented, then productivity is improved, but device complexity worsens
Solution Approach 1:
The compiler performs preliminary actions by automatically generating version history management code during the compilation phase. Version history update instructions are inserted into the executable code before runtime execution, capturing version information proactively when data entities are created or modified. This eliminates the need for runtime intervention and reduces manual overhead.
Solution Approach 2:
The system implements self-service mechanisms where the runtime environment automatically maintains version history without requiring developer intervention. The executable code contains embedded instructions that autonomously capture and store version information when data entities undergo creation, modification, or deletion operations, enabling the system to manage its own version history.
2Loss of time
If version history tracking is automated, then loss of time is reduced, but manufacturing precision worsens
Solution Approach 1:
The system implements feedback mechanisms where version history update instructions continuously monitor and capture changes to data entities. The runtime environment receives feedback about creation, modification, and deletion operations, automatically recording version information with timestamps and change details. This ensures accurate tracking of all version transitions without manual intervention.
Solution Approach 2:
The patent replaces manual version history management mechanisms with automated computational processes. Instead of developers manually tracking and recording version changes, the system uses embedded executable instructions and runtime processing to automatically capture and store version information, substituting mechanical human operations with automated digital processes.
3Device complexity
If manual version history management is used, then device complexity is reduced, but ease of operation worsens
Solution Approach 1:
The system introduces an intermediary layer in the form of version history query instructions and runtime processing mechanisms. These intermediaries facilitate easy access to version history by translating high-level access requests into automated retrieval operations. Developers can easily query version information without dealing with the underlying complexity of version tracking, as the intermediary runtime system handles the retrieval automatically.
Data Source
AI summary
Automated version history support for data entities is disclosed. A versioned query programming construct is provided that allows a developer to access a prior version of the data entity. A compiler is disclosed which automatically generates code to create and maintain version history for data entities at runtime. The version history is then available at runtime to service a query for a prior version, such as from query instructions compiled from the versioned query construct. A versioned data entity access instruction, used to access a prior version of the data entity, includes a data entity access construct modified by a versioned reference construct having a version reference. The version reference may be a time, a version number, or an event.