Database Table Definition Proxy for Schema-Flexible Collections
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional systems do not provide an interface for applications to access database collections due to their schema flexibility, which prevents applications configured for database tables from retrieving, updating, or inserting data into database collections.
Innovation Solution
Using database table definitions tied to a database collection, applications can access the collection by generating proxy table definitions that allow them to process requests, enabling multiple applications to share a single data source while maintaining schema flexibility.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If database collections use schema flexibility to allow adding or removing fields, then adaptability is improved, but conventional applications configured for database tables cannot access the collections
Solution Approach 1:
The patent introduces a translation layer that acts as an intermediary between applications and database collections. This translation layer converts application requests designed for database tables into queries that can access database collections, and converts collection results into table-like formats. This mediator enables applications configured for strict schemas to access schema-flexible collections without modifying the applications themselves.
Solution Approach 2:
The patent dynamically changes the schema parameters when accessing database collections. Instead of requiring applications to adapt to collection flexibility, the system adjusts the schema parameters on-the-fly during query execution, translating between the rigid schema expectations of applications and the flexible schema reality of collections.
2Ease of operation
If conventional systems use database tables with strict schemas, then application compatibility is improved, but schema flexibility for adding or removing fields is lost
Solution Approach 1:
The translation layer serves as an intermediary that allows applications to continue using database tables with strict schemas while the underlying storage uses schema-flexible collections. The translation layer handles the schema conversion transparently, preserving application compatibility while enabling schema flexibility in the database layer.
Solution Approach 2:
The patent creates a virtual copy of the database table structure that applications interact with, while the actual data resides in schema-flexible collections. This copying approach allows applications to work with familiar table schemas while the underlying collection structure remains flexible and adaptable.
3Adaptability or versatility
If multiple applications with different schema requirements access the same data source, then adaptability is improved, but data migration and updates become complex
Solution Approach 1:
The translation layer acts as a central intermediary that manages data access for multiple applications with different schema requirements. Instead of requiring complex data migration between multiple data sources, the translation layer handles schema conversion for each application individually while all applications access the same underlying collection, simplifying data management and updates.
Solution Approach 2:
The patent implements a universal data access interface that serves multiple applications with different schema requirements through a single translation layer. This multi-functional approach allows the same underlying collection to serve multiple applications with varying schema needs, eliminating the need for separate data sources and reducing migration complexity.
Data Source
AI summary
Disclosed herein are system, method, and computer program product embodiments for accessing a database collection. In some embodiments, an application generates a database collection. The database collection is configured to store documents (e.g., records). The application generates a database table definition. The database table definition is a proxy or adapter for the database collection. The application receives a request to be executed to be executed on the database collection from a client device. The request specifies the database table definition. The application accesses the database collection, via the database, to process the request using the database table definition.