Model-Driven Database Query Interface Generation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Traditional approaches for building database query web interfaces are time-consuming, impractical for rich user interfaces, and lack scalability and maintenance efficiency as applications evolve, especially with growing data and attribute complexity.

Innovation Solution

A model-driven system generates web-based database query components that allow dynamic addition of new query criteria, separating data and user interface concerns using an MVC architecture, enabling adaptation to model changes without altering the query user interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If traditional approaches are used to build database query web interfaces by manually creating forms one-by-one, then the user interface can be customized, but the development time and maintenance cost increase significantly

Engineering Contradiction:

Improveease of interface creationVSAvoiddevelopment time

Core Design Contradiction:

Ease of manufactureVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-defining the user interface template structure before the actual query execution. The system prepares a standardized query interface template that automatically adapts to different database schemas, eliminating the need for manual form creation for each query type. This template preparation happens in advance, allowing rapid deployment of query interfaces without time-consuming manual customization.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by replicating a standardized query interface template across different database schemas. Instead of manually creating unique forms for each database structure, the system copies the same template structure and dynamically populates it with schema-specific fields and parameters. This copying approach maintains interface consistency while adapting to different data structures, significantly reducing development time.

Inventive Principle:

Principle #26Copying

2Adaptability or versatility

If traditional manual form building is used, then the interface structure is flexible, but scalability and adaptability to evolving applications deteriorate

Engineering Contradiction:

Improveinterface adaptabilityVSAvoidinterface complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the query interface into modular components: a standardized template structure, dynamic field generation based on schema, and parameter configuration. This segmentation allows the interface to be flexible in adapting to different schemas while maintaining a simple, consistent structure. The template is segmented from the data model, enabling independent evolution of each without affecting the other.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements dynamics by making the interface automatically adapt to changing database schemas. The query interface template dynamically generates fields and parameters based on the current schema definition, allowing the interface to evolve with the application without manual redesign. This dynamic adaptation maintains simplicity while providing versatility across different data structures.

Inventive Principle:

Principle #15Dynamics

3Quantity of substance

If the number of records and attributes grows in the database, then the data capacity increases, but the difficulty of maintaining and updating queries increases

Engineering Contradiction:

Improvedata capacityVSAvoidmaintenance ease

Core Design Contradiction:

Quantity of substanceVSEase of manufacture

Solution Approach 1:

The patent applies self-service by enabling the query interface to automatically generate and update itself based on database schema changes. When the database schema evolves to accommodate growing data capacity, the system automatically adjusts the query interface parameters and fields without requiring manual maintenance. The interface serves itself by dynamically adapting to schema changes, eliminating maintenance overhead as data capacity increases.

Inventive Principle:

Principle #25Self-service

4Ease of operation

If complex trend analysis and fine control of attributes are required, then the query capability improves, but the maintenance cost increases significantly

Engineering Contradiction:

Improvequery control capabilityVSAvoidmaintenance cost

Core Design Contradiction:

Ease of operationVSEase of manufacture

Solution Approach 1:

The patent applies universality by creating a single query interface template that handles multiple query types and attribute combinations. The template is designed to universally accommodate any database schema and query requirement through dynamic parameter generation. This universal template provides complex trend analysis and fine control capabilities without requiring separate maintained interfaces for each query type, significantly reducing maintenance cost while improving operational capability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS7970777B2Model-driven database query

Publication Date: 2011.06.28 ORACLE INT CORP

AI summary

A system receives a model for a database to be queried and determines a first component-type and a first data-type for a first search criterion based on the model. The system generates at least one search criterion component that corresponds to the first search criterion and renders a query component that comprises the search criterion component.