Query Handler Selective Table Fragment Locking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database management systems face challenges in optimizing performance due to complex queries and high transaction volumes, leading to inefficient data access and increased computational resources, especially when only a limited number of rows and columns are required, resulting in unnecessary overhead and slowed query execution.
Innovation Solution
A query handler intercepts queries to selectively open and lock only the necessary fragments, rows, and columns of data tables, optimizing performance by minimizing time and computational resources required for query execution, rather than opening entire data tables.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If entire data tables are opened for query execution, then data access is simplified and ensured, but computational resources and time are wasted on unnecessary data loading
Solution Approach 1:
The patent segments data tables into fragments and further into rows, allowing selective access to only the necessary portions. The query handler divides the table opening operation into smaller units (fragments, rows) that can be individually managed and accessed only when needed, rather than loading entire tables.
Solution Approach 2:
The patent extracts the table opening operation from the query execution process. A separate query handler is introduced that independently manages table opening and fragment/row selection, extracting the necessary data access logic from the main execution flow to enable more efficient selective opening of only required data portions.
2Reliability
If entire data tables are opened for query execution, then data availability is ensured, but computational resources are increased
Solution Approach 1:
The patent segments data tables into fragments and rows, enabling selective opening of only the necessary portions. This segmentation allows the system to maintain data availability for queried rows while avoiding the computational burden of loading entire tables, thus reducing overall resource consumption.
Solution Approach 2:
The query handler autonomously manages table opening and fragment/row selection based on query requirements. It independently determines which fragments and rows need to be opened, eliminating the need for the execution engine to handle entire table loading, thereby optimizing resource utilization.
3Use of energy by moving object
If selective row and column access is implemented, then computational resources are reduced, but data access complexity increases
Solution Approach 1:
The patent introduces a query handler as an intermediary component between the execution engine and data tables. This mediator manages the complexity of selective fragment and row opening by intercepting queries, determining necessary data portions, and coordinating with the execution engine, thus reducing overall system complexity despite enabling selective access.
4Speed
If table opening is intercepted and optimized, then query execution speed improves, but system architecture complexity increases
Solution Approach 1:
The query handler serves as an intermediary layer that optimizes table opening operations without fundamentally altering the core execution engine architecture. It intercepts queries, manages fragment and row selection, and coordinates with the execution engine, improving speed while adding manageable architectural complexity through a focused intermediary component.
Data Source
AI summary
In some aspects, there is provided a method that may include: intercepting a query requiring access to data stored in a table. The query may include an identifier, which may be associated with a row of the table and a reference to a column of the table. The method may further include preparing a table object to enable access to the data stored in the row and the column of the table. The preparing may include locating the row associated with the identifier. The preparing may further include acquiring locks for the data stored in the located row and the column in the row. The method may also include executing the query upon preparing the table object. Related systems, methods, and articles of manufacture are also described.