Custom Data Type Creation and Reuse in Database Software

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database software applications restrict users to default properties of predefined data types, making it difficult for average users to modify or combine data types for reuse as a single data type.

Innovation Solution

A database software application allows users to select fields or groups of fields from a database table, generate custom data types by saving them with user-defined properties, and reuse these custom data types in the database, enabling users to create and reuse custom data types.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If users are restricted to using default properties of predefined data types, then the system maintains simplicity and stability, but user flexibility and customization capability deteriorate

Engineering Contradiction:
Improveuser flexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments data types into predefined data types (provided by the system) and custom data types (created by users). This segmentation allows users to work with simple predefined types when needed while enabling creation of customized types when flexibility is required, resolving the contradiction between simplicity and adaptability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal data type system where both predefined and custom data types can coexist and be used interchangeably in database operations. Custom data types inherit the stability of predefined types while adding user-defined flexibility, making the system universally applicable to both simple and complex requirements.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If users cannot easily combine data types, then the predefined data types remain simple and manageable, but the ability to create composite data structures deteriorates

Engineering Contradiction:
Improvedata type combinabilityVSAvoidease of creation
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent enables merging of multiple predefined data types into a single custom data type. Users can select multiple fields with different predefined data types and combine them into one custom data type that preserves the properties of all component types, thus achieving data type combinability while maintaining ease of creation through the graphical interface.

Inventive Principle:
Principle #5Merging (Combining)

3Productivity

If users cannot save and reuse custom data types, then the system remains simple with no customizations, but productivity and efficiency deteriorate due to repetitive work

Engineering Contradiction:
Improvedatabase operation efficiencyVSAvoiddata type management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent allows users to perform preliminary actions by creating custom data types that can be saved and reused multiple times. Once a custom data type is created and saved, it can be automatically applied to multiple fields or tables, eliminating repetitive manual configuration and significantly improving productivity while the system manages the complexity through automated templates.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9152656B2Database data type creation and reuse
Publication Date: 2015.10.06 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9152656B2 patent drawing
  • US9152656B2 patent drawing
  • US9152656B2 patent drawing

AI summary

Embodiments are provided for creating and reusing custom data types in a database. A selection of a field or group of fields may be received from a database table in the database by a database software application executing on a computer system. Each selected field may include a set of field properties. The application may further receive a user input to initiate saving the selected field or group of fields as a custom data type. In response to receiving the input, the application may be configured to generate a dialog for receiving custom data type information for the selected field or group of fields and save the selected field or group of fields as a custom data type. The custom data type may then be reused by the application in the database.