Page State Queries for Efficient Data Paging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Business Intelligence systems face inefficiencies when paging through large sets of returned values, requiring additional programming logic to maintain query state, which complicates data access and retrieval.
Innovation Solution
A method where the repository generates and returns page state queries that embed query state within the query, allowing for efficient segmentation and retrieval of objects from a segmented index, eliminating the need for maintaining query state in the accessing application.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the entire group of objects is returned by the query, then the data access is simple, but the efficiency deteriorates when dealing with large datasets
Solution Approach 1:
The patent segments the large dataset into pages, where each page contains a subset of objects. The query state (current page number, page size, sort criteria) is embedded within each page object, allowing the system to retrieve and navigate through large datasets efficiently without loading everything into memory at once.
Solution Approach 2:
Each page object contains embedded state information (current page, total pages, sort criteria) that enables the page itself to serve as a complete navigation unit. This eliminates the need for external state management logic in the accessing application, as the page carries its own state information.
2Ease of operation
If paging logic is implemented in the accessing application, then the data retrieval becomes manageable, but the programming complexity increases
Solution Approach 1:
The page objects are self-contained with embedded state information including current page number, total page count, and sort criteria. This allows the page to serve its own navigation needs without requiring external state management logic in the accessing application, significantly simplifying the programming required.
Solution Approach 2:
The patent introduces an intermediary layer (the page object with embedded state) between the querying application and the data repository. This intermediary carries all necessary state information, eliminating the need for complex state management logic in the accessing application while maintaining ease of operation.
3Productivity
If additional helper logic is added to maintain query state, then the paging functionality is achieved, but the system complexity increases
Solution Approach 1:
Instead of adding external helper logic to maintain query state, the patent embeds the state information directly within the page object itself. Each page contains its own state information (current page, total pages, sort criteria), eliminating the need for separate helper logic and reducing system complexity.
Solution Approach 2:
The patent merges the query state information with the page data structure itself. Rather than maintaining state separately in helper functions or external variables, all state information is combined within the page object, reducing the number of separate components and simplifying the overall system.
Data Source
AI summary
A computer readable storage medium includes executable instructions to receive from a requester a query for objects within a system. An index for the objects within the system that match the query is generated. The index is segmented into pages. A set of page state queries is returned to the requester. The page state queries specify criteria for retrieving objects from segments of the index.