Database Intended Usage Metadata for Column Value Treatment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database systems lack a centralized and efficient method to indicate the intended usage of data in columns, leading to inconsistencies and limitations in treating values differently based on their intended use.
Innovation Solution
The introduction of Intended-Usage (IU) labels and IU-bundles, which allow developers to associate specific intended uses with columns as metadata, supplementing the underlying primitive datatypes without replacing them. This enables the database server to provide special treatment to values based on their intended usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If user-defined data types or SQL domains are created to ensure special treatment of column values, then values in such columns can be treated differently, but the complexity of defining and maintaining these data types increases significantly
Solution Approach 1:
The patent introduces an intermediary layer between the primitive datatype and the application logic. Instead of requiring complex user-defined data types, the system uses a standardized annotation mechanism (e.g., comments, metadata attributes) that serves as a mediator to convey intended usage information to the database server. This intermediary approach allows special treatment without the complexity of full user-defined types.
Solution Approach 2:
The patent changes the parameter representation from complex user-defined data type definitions to simple metadata annotations or comments associated with columns. This parameter change allows the database server to recognize intended usage through lightweight metadata rather than requiring comprehensive type definitions, thereby reducing complexity while maintaining reliability.
2Adaptability or versatility
If primitive types such as NUMBER or VARCHAR are used to store diverse data, then storage flexibility is improved, but the ability to differentiate intended usage between columns is lost
Solution Approach 1:
The patent implements a nested structure where metadata annotations are embedded within or alongside the primitive datatype definitions. The primitive types (NUMBER, VARCHAR) maintain their storage flexibility while being nested with additional layers of intended usage information through comments or metadata attributes, allowing both versatility and information retention.
Solution Approach 2:
The patent adds another dimension to the data representation by introducing a metadata layer that coexists with the primitive datatype. This dimensional addition allows the system to maintain storage flexibility through primitive types while simultaneously preserving intended usage information through the additional metadata dimension, effectively solving the information loss problem.
3Device complexity
If datatype information is used to determine column treatment, then data storage is simplified, but columns with the same datatype cannot be differentiated by intended usage
Solution Approach 1:
The patent segments the column metadata into two distinct parts: the primitive datatype (for storage simplicity) and the intended usage annotation (for differentiation). This segmentation allows the database server to maintain simple storage based on primitive types while simultaneously enabling differentiation of column usage through separate metadata segments, resolving the contradiction between simplicity and adaptability.
Data Source
AI summary
Disclosed herein are techniques for storing, within a database system, metadata that indicates an intended usage (IU). Once created, an IU may be assigned to a column to (a) indicate how the column is intended to be used, and (b) affect how the database server behaves when database operations involve values from the column. The IU assigned to a column supplements, but does not replace, the datatype definition for the column. Each IU may have an IU-bundle. The IU-bundle of an IU indicates how the database server behaves with respect to any column that is assigned the IU. For example, the IU-bundle may indicate constraints that the database server must validate during operations on values from columns assigned to the IU. Techniques are also described for implementing multi-column IUs and flexible IUs.