Encoding Schema Version in Database Table Names
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile devices face performance limitations due to slower processors and storage, leading to suboptimal user experiences, particularly during application startup, where multiple queries are required to verify database schema versions, increasing launch time and reducing responsiveness.
Innovation Solution
Encoding database schema version identifiers into table names allows for a single initial query to retrieve data and verify schema version, reducing the number of queries needed during application startup, thereby minimizing launch time and improving responsiveness.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple queries are executed to verify database schema version during application startup, then schema version verification reliability is improved, but application launch time increases
Solution Approach 1:
The patent combines the schema version verification query and the initial data retrieval query into a single unified query operation. By encoding the schema version identifier into the table name of an existing data table, the system verifies schema version and retrieves data simultaneously, eliminating the need for separate verification queries and reducing application startup time.
Solution Approach 2:
The patent makes the initial data retrieval query serve multiple functions: it simultaneously performs schema version verification and data retrieval. By embedding the schema version identifier in the table name, a single query operation achieves what previously required multiple separate queries, improving efficiency without sacrificing verification reliability.
2Loss of time
If a single query is used to both retrieve data and verify schema version, then application launch time is reduced, but query complexity increases
Solution Approach 1:
The patent performs preliminary encoding of the schema version identifier into the table name during database schema creation or update. This pre-prepared encoded table name is then used in the initial query, allowing the query to inherently verify schema version without requiring complex runtime verification logic. The complexity is shifted from runtime query execution to offline schema preparation.
3Reliability
If schema version is verified before data retrieval, then data retrieval reliability is improved, but the number of queries increases
Solution Approach 1:
The patent merges the schema verification function and data retrieval function into a single query operation. By encoding the schema version identifier into the table name, the system performs both verification and retrieval simultaneously, maintaining data retrieval reliability while eliminating the need for separate verification queries, thus improving overall query execution efficiency.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
The subject matter of this disclosure can be implemented in, among other things, a device that includes processors, a data repository, and a table version module configured to create a first version of a database within the data repository using a first version of a database schema that defines a set of tables for the database, and receive a result that is responsive to a command, such that when the result indicates a success condition, execution of the command allows access to data contained in the database and verification of the database schema version, wherein the result does not include database schema version information. The device further includes means for executing the command to access the data, wherein the command includes one or more encoded table names, and wherein each of the encoded table names included in the command is generated based on at least a database schema version identifier.