Project Data Loading System Reference Table Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional methods are inefficient and CPU-intensive for determining and updating project files that reference other components, leading to difficulties in proper deployment and updating across project hierarchies.
Innovation Solution
A project data loading system that uses a database structure with a ProjectInfo table and a ProjectReference table to efficiently store and retrieve project file references, allowing for quick identification of which project files contain references to other components, thereby reducing the need for repeated CPU-intensive searches.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traditional CPU-intensive search methods are used to determine project file references, then reference information can be found, but the processing time and computational resources increase significantly
Solution Approach 1:
The patent applies preliminary action by pre-computing and storing the reference relationships between project files in a database during an initial loading phase. The BuildEngine analyzes project references upfront and populates the ProjectReference table with pre-established relationships, so that subsequent queries can retrieve reference information directly without performing CPU-intensive searches. This resolves the contradiction by performing the computationally expensive work before it is needed, enabling fast retrieval while maintaining accurate reference identification.
2Reliability
If traditional search methods are used to update referenced projects, then all referencing projects can be identified, but the deployment efficiency decreases due to repeated analysis
Solution Approach 1:
The system performs preliminary action by pre-establishing and storing all reference relationships in the ProjectReference table before deployment operations. When a project needs to be updated, the system simply queries the pre-computed reference data to identify all dependent projects, rather than re-analyzing the entire codebase. This ensures complete identification of all referencing projects (maintaining reliability) while dramatically improving deployment efficiency by avoiding repeated CPU-intensive analysis.
Solution Approach 2:
The patent applies copying by creating a database representation (copy) of the project reference relationships that mirrors the actual file system structure. The ProjectReference table contains copied reference information that can be queried and processed without accessing the original source files, enabling efficient deployment operations while ensuring all references are captured through the pre-computed database structure.
3Quantity of substance
If project reference information is not pre-loaded, then storage requirements are reduced, but repeated CPU-intensive searches are required for each query
Solution Approach 1:
The system applies preliminary action by pre-computing and storing reference relationships in the database during an initial loading phase. The BuildEngine analyzes project references upfront and populates the ProjectReference table, converting computational work into stored data. This resolves the contradiction by performing the energy-intensive analysis once during database initialization, enabling subsequent queries to retrieve reference information with minimal computational energy while maintaining reasonable storage requirements.
Data Source
AI summary
A method of loading project data comprising identifying project files with a project ID. The method includes determining a secondary project file is referenced in a primary project file. The method includes loading the project ID of the secondary and primary project files into a reference table. The primary project file project ID and the secondary project file project ID referenced in the respective primary project file are associated with one another in the reference table. The method includes receiving a query for the primary project files referencing a queried secondary project file. The method includes determining the project IDs of the primary project files in the reference associated with the project ID of the queried secondary project file. The method includes providing a results table including the primary project file project IDs associated with the queried secondary project file project ID in the reference table.