Persistency Interface for Cross-Schema Data Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in allowing applications to access data structures across different database schemas without requiring complex schema naming and join operations, leading to decoupling issues and potential instability in data access.
Innovation Solution
A persistency interface is defined using table links and synonyms to enable access to tables and views across different database schemas, allowing applications to access data independently of schema names and runtime environments, with roles managing access permissions and stability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If applications access data structures across different database schemas using traditional methods, then data access is possible, but the system complexity increases due to schema naming and join operations
Solution Approach 1:
The patent introduces a persistency interface as an intermediary layer between applications and database schemas. This interface uses table links and synonyms to mediate access to data structures across different schemas, eliminating the need for applications to directly handle complex schema naming and join operations. The interface translates simple access requests into the appropriate database operations behind the scenes.
2Adaptability or versatility
If applications access data structures across different database schemas, then data sharing is enabled, but coupling between applications increases leading to instability
Solution Approach 1:
The persistency interface acts as a decoupling intermediary that enables data sharing while maintaining stability. By using table links and synonyms managed at the database level rather than the application level, the interface allows applications to access data from other schemas without creating direct coupling. Changes in source schemas do not propagate to consuming applications, as the interface abstracts these changes away.
3Ease of operation
If traditional schema access methods are used, then data access is possible, but decoupling between applications deteriorates
Solution Approach 1:
The patent introduces a persistency interface as an intermediary layer between applications and database schemas. This interface uses table links and synonyms to mediate access to data structures across different schemas, eliminating the need for applications to directly handle complex schema naming and join operations. The interface translates simple access requests into the appropriate database operations behind the scenes.
Solution Approach 2:
The patent segments the data access functionality into distinct components: the persistency interface layer, the table link/synonym layer, and the underlying database schemas. This segmentation allows each layer to operate independently, with the interface layer handling access logic and the schema layers maintaining their own structures. Applications interact only with the interface layer, which handles the complexity of cross-schema access internally.
Data Source
AI summary
Methods, systems, and computer program products for accessing a database element are described. A local schema comprising a table link is created and the table link is used to access a database table via a persistency interface.


