EJB QL ResultSet Extensions for Direct Database Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional methods for accessing databases using Enterprise Java Beans require explicit object manipulation to retrieve multiple field values, leading to inefficient and time-consuming processes.
Innovation Solution
Enhancements to the EJB Query Language (EJB QL) allow for the selection and retrieval of ResultSets, bypassing the need for expensive object retrieval and manipulation by directly accessing the database, supporting features like QL Subqueries, Aggregate Functions, and QL Queries Returning ResultSets.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional EJB object manipulation methods are used to retrieve multiple field values, then data can be accessed through standard EJB interfaces, but the process becomes inefficient and time-consuming due to explicit object retrieval and manipulation requirements
Solution Approach 1:
The patent extracts the essential data fields from EJB objects and returns them directly as ResultSets, bypassing the need to retrieve and manipulate complete EJB objects. This extraction approach retrieves only the necessary field values (e.g., employee ID, name, department) without the overhead of object instantiation and method calls, thereby improving productivity and reducing time loss.
Solution Approach 2:
The patent introduces an intermediary mechanism (custom EJB QL query language extensions) that sits between the traditional EJB object model and the database. This intermediary allows direct field value retrieval through ResultSets while maintaining compatibility with standard EJB interfaces, resolving the contradiction by providing an efficient path without abandoning the existing object-oriented architecture.
2Use of energy by moving object
If direct database access is implemented to retrieve multiple fields, then resource efficiency improves, but compatibility with standard EJB interfaces must be maintained
Solution Approach 1:
The patent makes the EJB system multi-functional by enabling two modes of data retrieval: traditional object-based access and direct field value access via ResultSets. The same EJB components can serve both purposes, allowing applications to choose the most efficient approach based on their specific needs while maintaining universal compatibility with standard EJB interfaces.
Solution Approach 2:
The custom EJB QL query language acts as an intermediary that translates high-level field selection requirements into efficient database queries. This intermediary layer maintains adaptability by supporting both traditional EJB object retrieval and new direct field access patterns, ensuring compatibility across different usage scenarios without sacrificing resource efficiency.
3Reliability
If multiple EJB objects are retrieved and manipulated individually to access field values, then standard EJB procedures are followed, but the process becomes complex and time-consuming
Solution Approach 1:
The patent merges multiple individual field retrieval operations into a single consolidated ResultSet. Instead of retrieving multiple EJB objects and calling individual getter methods for each field, the system combines all required field values into one unified ResultSet, reducing operational complexity while maintaining reliable data access through standard EJB query mechanisms.
Solution Approach 2:
The patent extracts field values from EJB objects at the database query level rather than at the application level. By extracting the needed data directly from the database through custom EJB QL queries, the system eliminates the complexity of individual object manipulation while ensuring reliable data retrieval through proven EJB interface adherence.
Data Source
AI summary
A system and method for accessing requested data in a database using result set objects. The invention also provides a set of enhancements to the EJB Query Language (“EJB QL”) for providing result sets using EJB QL and to efficiently access databases using select methods within Enterprise Java Beans. EJBQL language extensions allow for the selection and retrieval of result sets. Since the use of the invention is expressed in terms of object relational constructs defined in an EJB deployment, it allows for the retrieval of data from a database expressed in terms of the relationships defined in that EJB deployment.