View Business Object Key Management via Composite Node Identification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In client-server architectures, determining unique keys for view business object nodes is challenging, especially when these nodes are formed by combining or transforming source business object nodes, leading to inefficiencies and inconsistencies in data management.
Innovation Solution
A computer-implemented method and apparatus that determine keys for view business object nodes by combining the keys of the business object nodes used to form the view node, including the use of a key manager to identify view business object nodes during queries or retrieve operations, and optionally shortening keys to meet syntactical requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If keys are determined by combining source business object node keys, then unique identification of view business object nodes is achieved, but key complexity and data management overhead increase
Solution Approach 1:
The key determination process is segmented into distinct operations: generating composite keys from source business object keys, storing these keys in the view business object metadata, and using them for identification during queries. This segmentation manages complexity by breaking down the key management task into manageable, independent steps.
Solution Approach 2:
Keys for view business object nodes are determined and stored in advance during metadata generation, before actual query operations occur. This preliminary action ensures that unique identification keys are readily available when needed, eliminating the need for complex runtime key generation and improving query performance.
2Measurement precision
If composite keys are stored for all view business object nodes, then accurate node identification is enabled, but storage space and data redundancy increase
Solution Approach 1:
Composite keys are stored selectively in the metadata of each view business object node only where needed for identification, rather than duplicating full key information across all data structures. This local quality approach ensures accurate identification while minimizing unnecessary storage consumption.
3Stability of the object's composition
If key combination logic is implemented for transformed nodes, then consistency with source nodes is maintained, but processing time and computational overhead increase
Solution Approach 1:
The key combination logic is executed in advance during the metadata generation phase, not during query processing. This preliminary computation establishes consistent keys for all view business object nodes beforehand, ensuring data consistency while avoiding time-consuming key generation during runtime operations.
Data Source
AI summary
The subject matter disclosed herein provides methods and apparatus, including computer program products, for determining keys for use with data structures, such as objects, business objects, view business objects, and the like. In one aspect, there is provided a computer-implemented method. The method may include determining a first key of a view business object node by combining one or more keys of the business object nodes used to form the view business object node, the first key used to identify the view business object node when the view business object node is a root node. The method may also include determining, when the view business object node has a parent node, a second key of the view business object node by combining the first key and at least one key of the parent node, the second key used to identify the view business object node. Next, the method may store at least one of the first key and the second key to identify the view business object node during a query or a retrieve operation associated with a database. Related apparatus, systems, methods, and articles are also described.