Database Interface Generator for Complex SQL Constructs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database systems lack the ability to efficiently map complex constructs such as taxonomy, families, qualifiers, relationships, non-field attributes, and multi-valued fields, leading to inefficient data storage and retrieval, especially when dealing with large data sets, as they rely on standard SQL structures that do not support advanced constructs necessary for rapid access and manipulation.

Innovation Solution

A database interface generator that maps complex constructs and semantics to a standardized interface, hiding internal complexities while enabling efficient internal storage and speed, by utilizing extended SQL database features like taxonomy, families, qualifiers, and multi-valued fields, which allows for indirect lookups and rapid data access without altering the main table structure, and supports multilingual and multi-audience data management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If standard SQL structures are used for database storage, then device complexity is reduced and schema translation is simplified, but data retrieval efficiency and access speed deteriorate when dealing with complex constructs like taxonomy, families, and multi-valued fields

Engineering Contradiction:
Improvedatabase structure complexityVSAvoiddata retrieval efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent introduces an intermediary layer between the complex internal database structure and external interfaces. This mediator translates complex internal constructs (taxonomy, families, qualifiers) into standardized external representations, allowing the database to maintain efficient internal storage while providing simple standardized access points to external systems without exposing internal complexity

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The database structure is segmented into distinct components: main data tables, lookup tables for taxonomy and families, and interface layers for different access methods. This segmentation allows complex data to be stored efficiently in normalized forms while providing multiple access paths through standardized interfaces, resolving the contradiction between structural simplicity and retrieval efficiency

Inventive Principle:
Principle #1Segmentation

2Ease of manufacture

If family identifiers are added to main data tables using standard SQL layout, then schema translation remains trivial, but manual maintenance complexity increases when records need to be reclassified

Engineering Contradiction:
Improveschema translation easeVSAvoidfamily reclassification ease
Core Design Contradiction:
Ease of manufactureVSEase of operation

Solution Approach 1:

A separate family lookup table serves as an intermediary between the main data table and family classification. This mediator table stores family definitions and relationships independently, allowing family reclassification by updating the lookup table rather than manually altering main records, thus maintaining schema translation simplicity while greatly improving operational ease

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Family classifications and taxonomies are pre-defined in lookup tables before data entry. This preliminary setup allows records to be automatically assigned to families based on their attributes without requiring manual reclassification later, as the family structure is already established and can be modified independently in the lookup tables

Inventive Principle:
Principle #10Preliminary action

3Ease of manufacture

If direct translation process is used to iterate through tables and fields, then XSD schema generation is simplified, but the system cannot handle complex constructs like multi-valued fields and indirect lookups

Engineering Contradiction:
ImproveXSD generation easeVSAvoidcomplex construct support
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The system introduces an intermediary translation layer that processes complex database constructs before generating XSD schemas. This mediator analyzes complex types (multi-valued fields, indirect lookups, taxonomy relationships) and converts them into appropriate XSD representations, enabling the system to handle sophisticated data structures while maintaining straightforward schema generation through automated translation

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The database interface generator is designed with universal capabilities to handle multiple data construct types through a single standardized process. By incorporating specialized handlers for various construct types (multi-valued fields, lookup tables, taxonomy hierarchies), the system provides unified XSD generation functionality that adapts to different complex structures without requiring separate processing paths for each construct type

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

Data Source

PatentUS7917549B2Database interface generator
Publication Date: 2011.03.29 SAP SE
  • US7917549B2 patent drawing
  • US7917549B2 patent drawing
  • US7917549B2 patent drawing

AI summary

Enables a database generator interface configured to map complex constructs and semantics so internal complexities are hidden while providing efficient internal storage and speed. Extracts and analyzes complex relationships in database and exposes schema as XSD to allow for external interfacing. Presents a list of tables and fields that exist in database and accepts user input to determine which tables and fields to create an interface for. Lookup fields are listed which allow for user input for specifying which fields to create XSD enumeration lists for. The generated XSD file may be saved and utilized by other mapping tools to allow for interfacing with other databases. Mapping the schema of a extended SQL database allows for users with limited understanding of the internals of the extended SQL database to connect the database to other systems using commonly available tools. May be coupled with web services to provide universal access.