Case Join Decomposition for Database View Extension
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Complex database queries often require multiple joins to extend predefined views, leading to inefficiencies in resource usage and inflexibility for end-users, as they cannot modify these views directly.
Innovation Solution
The implementation of a case join mechanism that allows for optimized joins by decomposing self-key joins and reducing the number of required joins, enabling the addition of columns to predefined views without modifying the underlying database tables, thereby enhancing query optimization and user interface flexibility.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple joins are performed to extend predefined views, then the views can include additional columns from extended database tables, but the computational expense and processing time increase significantly
Solution Approach 1:
The patent segments the join operation by identifying self-key joins (where a table is joined with itself) and handling them separately from other joins. This segmentation allows the query optimizer to apply specialized optimization techniques to self-key joins, reducing the overall computational expense while maintaining the ability to extend predefined views with additional columns.
Solution Approach 2:
The patent changes the approach parameter from performing multiple sequential joins to using a case join decomposition that can eliminate redundant join operations. By detecting self-key joins and applying decomposition rules, the system transforms the query execution parameters to minimize processing time while achieving the same view extension result.
2Adaptability or versatility
If predefined views are made modifiable by end-users, then user flexibility increases, but the complexity of view management and potential for errors increases
Solution Approach 1:
The patent enables self-service by allowing end-users to extend predefined views by simply adding columns from existing database tables through a user interface. The system automatically handles the complex join decomposition and query optimization in the background, so users gain flexibility without encountering the complexity of view management or potential errors associated with manual view modification.
Solution Approach 2:
The query optimizer acts as an intermediary between the user's simple column addition request and the complex database join operations. It detects self-key joins, applies decomposition rules, and generates optimized query plans automatically, shielding users from complexity while enabling flexible view extension.
3Productivity
If case join decomposition is implemented, then the number of joins needed is reduced, but the complexity of the query optimization process increases
Solution Approach 1:
The patent applies preliminary action by implementing the case join decomposition logic and self-key join detection rules within the query optimizer in advance. This preliminary configuration of optimization rules allows the system to automatically reduce the number of joins needed during query execution without requiring complex real-time decision-making, thereby improving productivity while managing optimizer complexity through pre-established decomposition patterns.
Data Source
AI summary
Methods and apparatus, including computer program products, are provided for a case join. In one aspect, there is provided method, which may include receiving a query for a predefined view that is configured to inhibit modification; detecting whether the predefined view includes a database table extended to include an additional column; and generating, in response to the query, a view based on a case join, when the predefined view includes the database table extended to include the additional column. Related apparatus, systems, methods, and articles are also described.


