Database Driver Schema Exposure via Configuration File
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional database systems are limited in updating and exposing database schema information, leading to tight coupling between drivers and databases, and lack flexibility in schema representation, resulting in inefficient data access and manipulation.
Innovation Solution
A configuration file is used to retrieve database schema information through query, hard-coded data, or an override method, allowing for flexible and efficient exposure of schema details without requiring updates to driver or database binaries, enabling separate collections for structure and content and supporting new data types without corresponding driver versions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If database schema information is exposed through conventional query mechanisms or hard-coded data, then the driver can provide metadata about existing data types, but the driver must be updated simultaneously with the database when new data types are introduced, creating tight coupling between driver and database
Solution Approach 1:
The patent introduces a configuration file as an intermediary layer between the database and the driver. This configuration file stores schema information in a separate, accessible location that the driver can read without requiring direct integration with the database binary. When the database introduces new data types, the configuration file can be updated independently to provide metadata about these new types, eliminating the need to update the driver simultaneously with the database.
2Productivity
If database schema information is exposed through pre-determined collections with fixed formats, then the driver can retrieve schema data, but the structure and content become unduly large and complex, increasing the time required to read and search collections
Solution Approach 1:
The patent segments the schema information into separate, organized collections within the configuration file. Instead of a single monolithic collection containing both content and structure, the system divides the information into distinct collections (e.g., one for structure metadata, another for content metadata). This segmentation reduces the complexity of individual collections, making them easier and faster to read and search while maintaining complete schema information.
Data Source
AI summary
Systems and methods for improved exposure of database schema information are disclosed. Generally, a database driver may retrieve and provide database schema information according to one of two default methods or, also, a third override method. The first default method is to execute a query on the database. The second default method is to retrieve information from a hard-coded collection stored locally at the driver. The third override method is to retrieve information from a designated file that may be updated at any time without having to update the database and/or driver binaries.