XML Date-Time Type Mapping in Database Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database systems face inefficiencies in representing XML date-time types, as they either waste resources supporting unused options or fail to meet user requirements, due to a one-size-fits-all approach to database date-time types.
Innovation Solution
The system allows for tailored database representations of XML date-time types by using date-time annotations in XML schemas, which specify database types and properties, enabling precise mapping and optimized storage and query performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a general all-purpose database date-time type is used to represent XML date-time types, then user requirements for various precision levels and time zone options are supported, but database system resources are wasted to support features that are not used
Solution Approach 1:
The patent applies local quality by allowing different precision levels and time zone support to be configured locally for each XML schema or element rather than uniformly across the entire database system. This enables the database to allocate resources according to the actual requirements of each specific XML date-time type representation, avoiding waste on unused features while maintaining adaptability where needed.
Solution Approach 2:
The patent implements dynamics by making the database representation of XML date-time types configurable and adaptable based on actual usage patterns. The system can dynamically adjust the level of precision and time zone support according to the specific XML schemas being stored, transitioning from a static all-purpose approach to a dynamic, demand-driven resource allocation model.
2Adaptability or versatility
If a database date-time type with high precision and time zone support is used, then full range of XML date-time type options are supported, but storage space increases
Solution Approach 1:
The patent applies local quality by enabling time zone support and high precision to be selectively enabled only for those XML date-time elements that actually require these features, as determined by the XML schema definition. This allows the database to maintain adaptability for elements that need it while avoiding unnecessary storage overhead for elements that do not.
3Quantity of substance
If a database date-time type without time zone support is used, then storage space is reduced, but user requirements for time zone information are not met
Solution Approach 1:
The patent resolves this contradiction by allowing the database representation to be locally adapted to match the actual requirements of each XML schema. Time zone support is enabled only where needed in the XML data structure, ensuring both storage efficiency and adaptability to user requirements are achieved simultaneously.
Data Source
AI summary
A database server registers an XML schema and determines a database representation for the XML schema and mapping information, determining what database types should be used to represent an XML schema and/or how instances of the XML schema are stored by a database system. The mapping information indicates the mapping between the constructs declared in the XML schema and the constructs included in the appropriate database representation. The XML schema may contain annotations that describe one or more properties of a database representation of an XML date-time type. Based on the annotations, the database determines an appropriate database representation and generates mapping information mapping the declaration of the XML date-time type of the XML schema to the constructs of the database representation.