Database Operation Translation via Intermediary Layer

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing technologies face challenges in efficiently transforming operations of a computer program for execution at a database, particularly due to differences in languages used by various databases, which can lead to incomplete or inefficient processing of computational loads.

Innovation Solution

A method and system that utilize a translation file to translate operations specified in the language of the computer program into the language of the database, allowing for the 'pushing down' of computational loads to the database, thereby optimizing resource usage and enabling execution on diverse database languages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If computational operations are pushed down to the database for execution, then processing efficiency is improved and resource usage is optimized, but compatibility issues arise when databases use different languages with varying capabilities

Engineering Contradiction:

Improveprocessing efficiencyVSAvoidlanguage compatibility

Core Design Contradiction:

ProductivityVSAdaptability or versatility

Solution Approach 1:

A translation layer is introduced as an intermediary between the program operations and database operations. This translation layer maps program operations to database-specific operations, enabling compatibility across different database languages while maintaining the ability to push down computational operations for efficient execution.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system dynamically adjusts the translation strategy based on the target database's language capabilities and supported operations. By changing the translation parameters according to the specific database being accessed, the system optimizes both compatibility and execution efficiency for each database instance.

Inventive Principle:

Principle #35Parameter changes

2Ease of manufacture

If a fixed translation approach is used for database operations, then implementation simplicity is maintained, but the system cannot adapt to additional or updated database languages without modifying the underlying program

Engineering Contradiction:

Improveimplementation simplicityVSAvoidlanguage extensibility

Core Design Contradiction:

Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The translation layer is designed to be dynamic rather than static. It can load and adapt to different database language specifications at runtime, allowing new database languages to be supported by simply updating the translation configurations without modifying the core program logic.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The translation layer serves multiple functions: it translates operations for different database languages, negotiates capability support, and adapts to various database implementations. This universal approach allows a single program to work with multiple database systems while maintaining implementation simplicity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If all operations are executed by the data processing system, then language compatibility is maintained, but computing resources are used inefficiently and processing speed decreases

Engineering Contradiction:

Improvelanguage compatibilityVSAvoidprocessing speed

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

Operations are segmented into two categories: those that can be pushed down to the database for efficient execution and those that must remain at the data processing system. This segmentation allows the system to leverage database execution power for compatible operations while maintaining compatibility for operations that require centralized processing.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system applies partial push-down of operations rather than attempting to push down all operations. By selectively pushing down only those operations that are both efficient and compatible with the target database, the system achieves improved processing speed without sacrificing language compatibility.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentEP4208779B1Transforming operations of a computer program for execution at a database

Publication Date: 2025.04.16 AB INITIO TECHNOLOGY LLC

Figure 1
Figure 2A
Figure 2B

AI summary

A method includes executing a program that specifies operations and accessing a translation file that includes instructions for translating the language of the program into a language of a database. The translation file specifies operations in the language of the program that are supported by the database and the semantic meaning of the supported operations in the language of the database. Operations of the program that are unsupported by the database are processed by the program. Operations of the program that are supported by the database are determined from the translation file, and a portion of the program representing the supported operations is translated, using the translation file, into the language of the database and transmitted to the database. Data resulting from execution, within the database, of the translated portion of the program representing the operations that are supported by the database is received by the program.