Database Table Content Transport via Unified Deployment Infrastructure
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In database applications, transporting and delivering table content and metadata while ensuring consistent deployment and implicit dependencies is challenging, as existing methods lack an efficient mechanism for handling runtime-authored content and separate storage of table content and metadata.
Innovation Solution
A deployment infrastructure imports and exports table description artifacts and content data files between design-time and runtime containers, using a version control system to manage table content transport, allowing for consistent deployment and separate storage of table content and metadata, enabling efficient transport of updated content and metadata.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate transport mechanisms are used for table content and metadata, then flexibility in handling different data types is improved, but deployment consistency and dependency management deteriorate
Solution Approach 1:
The patent merges the transport of table content and metadata into a single unified transport mechanism. The deployment infrastructure exports both table descriptions (metadata) and table content through the same process, ensuring they are transported together and deployed in the correct sequence, thereby maintaining deployment consistency while handling both data types.
Solution Approach 2:
The patent segments the transport process into two phases: first transporting metadata (table descriptions) to create the table structure, then transporting content (table data) to populate the table. This segmentation within a unified mechanism ensures proper dependency management while maintaining overall transport consistency.
2Ease of operation
If table content and metadata are stored separately, then storage flexibility and access efficiency are improved, but transport complexity and dependency management worsen
Solution Approach 1:
The patent creates a universal transport mechanism that handles both metadata and content through a single export process. The deployment infrastructure is designed to export table descriptions and table content together, eliminating the need for separate transport processes and reducing overall transport complexity.
Solution Approach 2:
The patent performs preliminary action by first exporting and deploying table descriptions (metadata) before exporting table content. This preliminary establishment of the table structure ensures that the target system is ready to receive and properly handle the content, simplifying the overall transport process by establishing dependencies in advance.
3Adaptability or versatility
If runtime-authored content is transported using traditional methods, then compatibility with existing systems is improved, but transport efficiency and timeliness deteriorate
Solution Approach 1:
The patent implements self-service by enabling the deployment infrastructure to automatically export and transport runtime-authored content without requiring manual intervention or conversion to static files. The system directly exports content from the runtime container, maintaining compatibility with existing deployment workflows while significantly improving transport efficiency.
Solution Approach 2:
The patent introduces dynamics by allowing content to be exported directly from the runtime environment where it was authored, rather than requiring static file exports. This dynamic approach enables real-time or near-real-time transport of content generated during runtime, improving efficiency while maintaining system compatibility.
Data Source
AI summary
A deployment infrastructure (DI) imports at least one object description artifact and at least one content data file associated with a database object to a design-time container. The DI deploys the database object in a runtime container based on the at least one object description artifact and the at least one content data file. The DI exports the at least one object description artifact in the design-time container and at least one updated content data file based on an updated database object in the runtime container, wherein the updated database object includes updated content of the database object generated at runtime of a database application.