Document Validator for Non-Relational Database Schema Adaptation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional relational databases are inflexible and require a static schema, making it difficult to adapt to changes, necessitating redesign and additional development resources, while non-relational databases lack a rigid schema, complicating validation and error control, especially across multiple development languages.
Innovation Solution
A system with a document validator integrated into the database engine that reviews documents against validation rules, allowing for adaptive schema creation and validation, enabling flexible schema imposition on document collections, and supporting validation across different languages and modes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Stability of the object's composition
If a static schema format is used in relational databases, then data structure consistency is maintained, but adaptability to changes deteriorates
Solution Approach 1:
The patent implements a dynamic schema system where the schema can be modified at runtime without requiring application redesign. The schema is stored in the database and can be updated through database operations, allowing the structure to adapt flexibly to changing requirements while maintaining consistency through controlled validation mechanisms.
Solution Approach 2:
The patent separates schema definition from application logic by storing schema information as independent database objects. This allows the schema to be modified, versioned, and validated independently from the applications that use it, resolving the coupling between schema changes and application redesign.
2Adaptability or versatility
If schema changes are performed after application development, then flexibility is improved, but development resources and time increase
Solution Approach 1:
The patent implements schema validation that checks document conformity to the schema at the time of database operations. This preliminary validation ensures that schema changes can be applied and enforced immediately without requiring subsequent application testing and redesign, reducing the time and resources needed for schema upgrades.
3Adaptability or versatility
If no rigid schema is used in non-relational databases, then adaptability is improved, but validation and error control deteriorate
Solution Approach 1:
The patent introduces a schema as an intermediary layer between the flexible document storage and validation requirements. The schema defines validation rules that can be applied to documents in the collection, providing structured error control and data integrity checks while preserving the flexible, schema-less nature of non-relational database storage.
4Reliability
If developers build custom validation logic, then validation capability is improved, but device complexity and coordination difficulty increase
Solution Approach 1:
The patent provides a universal validation mechanism built into the database engine that can validate documents against schemas regardless of the application language or framework being used. This single validation system serves all applications accessing the database, eliminating the need for separate validation logic in each application and reducing overall system complexity.
Data Source
AI summary
A system is provided that includes a document validation within a non-relational database system that is capable of reviewing documents according to one or more validation rules. The document validator may be incorporated within a non-relational database engine and may perform validation operations when one or more database functions are performed.