Dynamic Parameterized Linking for Database Query Views

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database management systems require manual entry of query parameters for viewing related records across multiple tables, leading to static and inefficient querying processes.

Innovation Solution

A database query viewer that allows parameterized linking and viewing of related tables and queries, enabling dynamic changes and automatic updates across linked query panes, with features like configurable pane layouts, automatic wrapping, and XML file saving for easy sharing and transmission.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual entry of query parameters is used for viewing related records across multiple tables, then each query can be executed independently, but the querying process becomes static and inefficient requiring substantial user effort

Engineering Contradiction:
Improvequerying efficiencyVSAvoiduser effort
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The system dynamically links multiple query panes together so that when a record is selected in one pane, the other linked panes automatically update to show related records. This dynamic behavior eliminates the need for manual parameter re-entry and transforms the static querying process into an interactive, automated experience.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system introduces an intermediary mechanism that automatically transfers selection information between linked query panes. When a user selects a record in one pane, the intermediary automatically passes the relevant parameters to other linked panes, which then execute their queries with the new parameters without user intervention.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple independent query windows are opened to view related records, then each query can be customized independently, but the system complexity increases and dynamic responsiveness is lost

Engineering Contradiction:
Improvequery customizationVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system merges multiple independent query windows into a unified workspace where queries are visually linked through graphical connections. This combining approach maintains the independence and customization capability of each query while adding dynamic linking functionality, reducing the need for separate manual configurations.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The query pane system provides multi-functionality by enabling each pane to operate both as an independent query window and as a dynamically linked component. Users can customize each query independently while also establishing relationships between panes, allowing the same interface to serve multiple purposes without increasing complexity.

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

3Ease of operation

If query parameters are manually changed in each window to view different record sets, then precise control over each query is maintained, but time is lost and automation is reduced

Engineering Contradiction:
Improvequery controlVSAvoidparameter re-entry time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system implements feedback mechanisms where selection actions in one query pane automatically trigger corresponding parameter updates in linked panes. This feedback loop eliminates the need for manual parameter re-entry while maintaining precise query control, as the system automatically adjusts parameters based on user selections in the parent pane.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary actions by pre-establishing linkages between query panes and pre-configuring parameter relationships. When a user selects a record, the system has already prepared the linked panes to receive and process the parameter changes, eliminating the need for manual re-entry and reducing time loss.

Inventive Principle:
Principle #10Preliminary action

4Device complexity

If static query relationships are used across multiple tables, then system simplicity is maintained, but dynamic responsiveness and automated updates are lost

Engineering Contradiction:
Improvesystem simplicityVSAvoiddynamic querying capability
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The system transitions from static to dynamic query relationships by implementing automatic update mechanisms. When a record is selected in one pane, the system dynamically updates linked panes to reflect the new selection, providing automated responsiveness without significantly increasing system complexity.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system introduces an intermediary layer that manages the dynamic relationships between query panes. This intermediary handles the automatic parameter passing and query updates, allowing dynamic behavior to be implemented while keeping the underlying system architecture relatively simple and maintainable.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8073836B2System for viewing databases
Publication Date: 2011.12.06 EPICOR SOFTWARE CORP
  • US8073836B2 patent drawing
  • US8073836B2 patent drawing
  • US8073836B2 patent drawing

AI summary

A system and method allows for dynamic, parameterized linking of database views or tables. The database tables are related in a parent-dependent relationship, with dependent tables being linked to parent tables through a parameter. When a new record in the parent table is scrolled to, dependent tables automatically run queries and return records with matching parameters. The parameters include field values. Several table views may be combined in a single database table set. Multiple dependent tables may be linked to an individual parent table in a parallel manner. Dependent tables may also be cascaded through intermediate parent tables, each table in the cascade acting as a dependent to its parent and acting as a parent table to its dependent table(s). Database table sets may be saved and may be transmitted, for example via email.