US20030163460A1 - Systems and methods for dynamic querying - Google Patents
Systems and methods for dynamic querying Download PDFInfo
- Publication number
- US20030163460A1 US20030163460A1 US10/341,107 US34110703A US2003163460A1 US 20030163460 A1 US20030163460 A1 US 20030163460A1 US 34110703 A US34110703 A US 34110703A US 2003163460 A1 US2003163460 A1 US 2003163460A1
- Authority
- US
- United States
- Prior art keywords
- query
- settings
- generating
- finder
- generate
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
- Y10S707/99933—Query processing, i.e. searching
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99944—Object-oriented database structure
Definitions
- the present invention relates to executing queries against a database.
- the Enterprise JavaBean (EJB) specification published by Sun Microsystems, Inc. of Palo Alto, Calif., describes ways in which a user can execute queries against a database, as well as ways in which a user can communicate queries to an EJB container.
- EJB 2.0 specification forces users to hard-code finder queries into a deployment descriptor for an EJB.
- a user develops a query before deploying the EJB. Once the EJB is deployed, the user is able to execute the query.
- a problem exists with this approach however, in that it is necessary to redeploy the EJB every time the user wishes to run a new query.
- Systems and methods in accordance with one embodiment of the present invention can allow a user to dynamically generate a query to be executed against a database.
- a properties object can be generated that holds settings for the query, which can be specified by a user at runtime.
- the user or application can invoke an appropriate finder method.
- the server receiving the call from the finder method can extract the user-specified settings from the properties object and parse the finder method in order to generate a query statement.
- the server can then execute the query statement on the database and return the appropriate results.
- the generating of the properties object and the query statement can happen at runtime.
- FIG. 1 is a diagram of a system in accordance with one embodiment of the present invention.
- FIG. 2 is a flowchart showing the steps of a method that can be used with the system of FIG. 1.
- Systems and methods in accordance with one embodiment of the present invention can allow a user to define a query programmatically rather than defining the query statically.
- Static queries are defined, for example, by hard-coding the static query into the deployment descriptor for an EJB.
- Programmatic queries, or “dynamic queries”, allow users to construct and execute queries in their application code. This can provide several benefits over static queries which utilize static finder methods.
- One such benefit is the ability to create and execute new queries without having to update and redeploy an EJB.
- each query is read and parsed in order to generate the SQL to be sent to the database.
- Finder methods can be utilized in executing the query, which can be defined in the home interface of an entity bean.
- An example of a finder method is findByPrimaryKey( ), which can accept an instance of a primary key and return an instance of that entity type (or throw an exception).
- Additional finder methods can be defined in local home or remote home interfaces, with each finder method being associated with a query in the deployment descriptor. With dynamic queries, however, the query and corresponding SQL can be generated at runtime.
- Another benefit is that the size of an EJB deployment descriptor is reduced. Since the finder queries can be created dynamically, they do not have to be statically defined in the deployment descriptor. For some applications this approach may be a little slower, but the added flexibility will outweigh the slight hit in performance for many users.
- One system and method for implementing dynamic queries utilizes the generation of a class such as an ejbHome class.
- a class such as an ejbHome class.
- Such a class can be used to implement an extra interface with a method that can execute the query.
- an object such as a Java properties object 104 can be generated that can be populated with the settings for the finder method 106 , such as a container-managed or bean-managed finder method.
- the finder method 106 can then be invoked on the query home of the appropriate EJB 108 , which can be stored on a server 110 or EJB container in communication with, and capable of executing SQL queries against, a database 112 .
- the properties object 104 can be inspected and the user settings extracted.
- the finder method 106 can be parsed and the SQL query statement generated that is to be sent to the database 112 .
- the query is executed and, depending on the user settings, the use of the results can be determined.
- One possible result of such a query is a collection of EJBs.
- Another possible result is a number of values or fields on certain EJBs that match the query.
- a method that can be used in accordance with the system of FIG. 1 is shown in the flowchart of FIG. 2.
- a properties object is generated that contains user-specified settings for the query or the finder method, as can be implemented through a user interface of an ejbHome class 200 .
- the appropriate finder method is invoked when the user or application wishes to execute the query 202 .
- the settings are extracted from the properties object and the finder method is parsed in order to generate the appropriate SQL query statement, although other database or data source querying language statements may be generated by the method 204 .
- the SQL query statement is then executed against the database 206 .
- One embodiment can be implemented through a simple API.
- users can add an element to their deployment descriptor, such as:
- the enable-dynamic-queries element can be a sub-element of a descriptor such as entity-descriptor.
- the value of enable-dynamic-queries can be either “true” or “false” in this embodiment.
- Invoking a dynamic query when dynamic queries have not been enabled can result in an exception being thrown, such as java.rmi. AccessException or javax.ejb.AccessLocalException, depending on whether it was invoked from a Remote or Local interface.
- a generated implementation class such as HomeImpl that can be used for all EJB 2.0 Container-Managed Persistence (CMP) beans, can implement a new interface such as QueryHome.
- a QueryHome interface can declare a single method, such as: public Object executeQuery(String query, Properties props) throws FinderException, RemoteException;
- QueryLocalHome There can also be a local version of QueryHome which may be referred to as QueryLocalHome.
- the only difference between the interfaces can be the “throws” clause of the executeQuery method.
- the QueryLocalHome iinterface can declare a single method: public Object executeQuery(String query, Properties props) throws FinderException, EJBException;
- All options that can currently be specified for a static finder can be set in a Properties object passed to the executeQuery method.
- the Properties key for all valid options can be defined in a DynamicQuery interface.
- a list of some valid entries is as follows: Property: Value: Description: GROUP_NAME String The name of the field-group whose fields are to be loaded into the cache upon execution of the query. Note that in order for this to work, a finders- load-bean or equivalent option may need to be enabled for the EJB.
- MAX_ELEMENTS int The max-elements attribute is used to specify the maximum number of elements that should be returned by a multi-valued query. This option can be similar to the maxRows feature of JDBC.
- INCLUDE_UPDATES boolean The include-updates tag is used to specify that updates made during the current transaction must be reflected in the result of a query.
- SQL_SELECT_DISTINCT boolean Used to control whether the generated SQL ‘SELECT’ will contain a ‘DISTINCT’ qualifier. Use of the DISTINCT qualifier will cause the RDBMS to return unique rows.
- RETURN_TYPE String Indicates the return type of the executeQuery method. Legal values include Collection, CursoredCollection, and ResultSet. The default value is java.util.Collection.
- NEW_TRANSACTION boolean Indicates whether a new transaction should be started for the execution of the DynamicQuery
- ISOLATION_LEVEL String Indicates the isolation level to be used if a new transaction is started
- RESULT_TYPE_MAPPING String Indicates whether EJBObjects or EJBLocalObjects should be returned. The legal values are Local and Remote. If the query was executed on QueryHome, EJBObjects will always be returned. If the query was executed on QueryLocalHome, EJBLocalObjects will be returned by default. A result-type-mapping of Remote can be specified in this case if EJBObjects are desired.
- dynamic queries execute nearly as fast as static queries.
- Dynamic queries can invariably be somewhat slower since the queries can require parsing at runtime, whereas static queries are parsed during deployment.
- the speed of dynamic queries can be increased, such as by extending them to take query parameters and caching the parsed query String.
Abstract
A user can generate queries dynamically at runtime without having to redeploy the appropriate EJB or hard-code the query into the user application. A properties object can be generated to accept the query settings from the user. These settings can be extracted at runtime when the appropriate finder method is invoked, such that the desired query statement, such as a SQL statement, can be generated and executed against the database.
This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.
Description
- This application claims priority to U.S. Provisional Patent Application No. 60/349,432, filed Jan. 18, 2002, entitled “SYSTEMS AND METHODS FOR DYNAMIC QUERYING,” which is hereby incorporated herein by reference.
- A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document of the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
- The present invention relates to executing queries against a database.
- The Enterprise JavaBean (EJB) specification, published by Sun Microsystems, Inc. of Palo Alto, Calif., describes ways in which a user can execute queries against a database, as well as ways in which a user can communicate queries to an EJB container. Presently, the EJB 2.0 specification forces users to hard-code finder queries into a deployment descriptor for an EJB. A user develops a query before deploying the EJB. Once the EJB is deployed, the user is able to execute the query. A problem exists with this approach, however, in that it is necessary to redeploy the EJB every time the user wishes to run a new query.
- Systems and methods in accordance with one embodiment of the present invention can allow a user to dynamically generate a query to be executed against a database. A properties object can be generated that holds settings for the query, which can be specified by a user at runtime. When the query is to be executed, the user or application can invoke an appropriate finder method. The server receiving the call from the finder method can extract the user-specified settings from the properties object and parse the finder method in order to generate a query statement. The server can then execute the query statement on the database and return the appropriate results. The generating of the properties object and the query statement can happen at runtime.
- Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.
- FIG. 1 is a diagram of a system in accordance with one embodiment of the present invention.
- FIG. 2 is a flowchart showing the steps of a method that can be used with the system of FIG. 1.
- Systems and methods in accordance with one embodiment of the present invention can allow a user to define a query programmatically rather than defining the query statically. Static queries are defined, for example, by hard-coding the static query into the deployment descriptor for an EJB. Programmatic queries, or “dynamic queries”, allow users to construct and execute queries in their application code. This can provide several benefits over static queries which utilize static finder methods.
- One such benefit is the ability to create and execute new queries without having to update and redeploy an EJB. When deploying an EJB with static queries, each query is read and parsed in order to generate the SQL to be sent to the database. Finder methods can be utilized in executing the query, which can be defined in the home interface of an entity bean. An example of a finder method is findByPrimaryKey( ), which can accept an instance of a primary key and return an instance of that entity type (or throw an exception). Additional finder methods can be defined in local home or remote home interfaces, with each finder method being associated with a query in the deployment descriptor. With dynamic queries, however, the query and corresponding SQL can be generated at runtime.
- Another benefit is that the size of an EJB deployment descriptor is reduced. Since the finder queries can be created dynamically, they do not have to be statically defined in the deployment descriptor. For some applications this approach may be a little slower, but the added flexibility will outweigh the slight hit in performance for many users.
- One system and method for implementing dynamic queries utilizes the generation of a class such as an ejbHome class. Such a class can be used to implement an extra interface with a method that can execute the query. As shown in FIG. 1, when a
user 100 wants to execute a query against adatabase 112 at runtime, an object such as a Javaproperties object 104 can be generated that can be populated with the settings for thefinder method 106, such as a container-managed or bean-managed finder method. Thefinder method 106 can then be invoked on the query home of the appropriate EJB 108, which can be stored on aserver 110 or EJB container in communication with, and capable of executing SQL queries against, adatabase 112. Once the call makes it into theserver 110, theproperties object 104 can be inspected and the user settings extracted. Thefinder method 106 can be parsed and the SQL query statement generated that is to be sent to thedatabase 112. The query is executed and, depending on the user settings, the use of the results can be determined. One possible result of such a query is a collection of EJBs. Another possible result is a number of values or fields on certain EJBs that match the query. - A method that can be used in accordance with the system of FIG. 1 is shown in the flowchart of FIG. 2. In the method, a properties object is generated that contains user-specified settings for the query or the finder method, as can be implemented through a user interface of an ejbHome
class 200. The appropriate finder method is invoked when the user or application wishes to execute thequery 202. The settings are extracted from the properties object and the finder method is parsed in order to generate the appropriate SQL query statement, although other database or data source querying language statements may be generated by themethod 204. The SQL query statement is then executed against thedatabase 206. - One embodiment can be implemented through a simple API. To enable the use of dynamic queries, users can add an element to their deployment descriptor, such as:
- <!ELEMENT enable-dynamic-queries (#PCDATA)>
- The enable-dynamic-queries element can be a sub-element of a descriptor such as entity-descriptor. The value of enable-dynamic-queries can be either “true” or “false” in this embodiment. Invoking a dynamic query when dynamic queries have not been enabled can result in an exception being thrown, such as java.rmi. AccessException or javax.ejb.AccessLocalException, depending on whether it was invoked from a Remote or Local interface.
- A generated implementation class, such as HomeImpl that can be used for all EJB 2.0 Container-Managed Persistence (CMP) beans, can implement a new interface such as QueryHome. A QueryHome interface can declare a single method, such as:
public Object executeQuery(String query, Properties props) throws FinderException, RemoteException; - There can also be a local version of QueryHome which may be referred to as QueryLocalHome. The only difference between the interfaces can be the “throws” clause of the executeQuery method. The QueryLocalHome iinterface can declare a single method:
public Object executeQuery(String query, Properties props) throws FinderException, EJBException; - The application code can make use of this interface as follows:
InitialContext ic = new InitialContext(); FooHome fh = (FooHome)ic.lookup(“fooHome”)’ QueryHome qh = (QueryHome)fh; String query = “SELECT OBJECT(e) FROM EmployeeBean e WHERE e.name = ‘rob’ ”; Properties props = new Properties(); props.setProperty(DynamicQuery.MAX_ELEMENTS, “10”); Collection results = (Collection)qh.executeQuery(query, props); - All options that can currently be specified for a static finder can be set in a Properties object passed to the executeQuery method. The Properties key for all valid options can be defined in a DynamicQuery interface. A list of some valid entries is as follows:
Property: Value: Description: GROUP_NAME String The name of the field-group whose fields are to be loaded into the cache upon execution of the query. Note that in order for this to work, a finders- load-bean or equivalent option may need to be enabled for the EJB. MAX_ELEMENTS int The max-elements attribute is used to specify the maximum number of elements that should be returned by a multi-valued query. This option can be similar to the maxRows feature of JDBC. INCLUDE_UPDATES boolean The include-updates tag is used to specify that updates made during the current transaction must be reflected in the result of a query. SQL_SELECT_DISTINCT boolean Used to control whether the generated SQL ‘SELECT’ will contain a ‘DISTINCT’ qualifier. Use of the DISTINCT qualifier will cause the RDBMS to return unique rows. RETURN_TYPE String Indicates the return type of the executeQuery method. Legal values include Collection, CursoredCollection, and ResultSet. The default value is java.util.Collection. NEW_TRANSACTION boolean Indicates whether a new transaction should be started for the execution of the DynamicQuery ISOLATION_LEVEL String Indicates the isolation level to be used if a new transaction is started RESULT_TYPE_MAPPING String Indicates whether EJBObjects or EJBLocalObjects should be returned. The legal values are Local and Remote. If the query was executed on QueryHome, EJBObjects will always be returned. If the query was executed on QueryLocalHome, EJBLocalObjects will be returned by default. A result-type-mapping of Remote can be specified in this case if EJBObjects are desired. - Ideally, dynamic queries execute nearly as fast as static queries. Dynamic queries can invariably be somewhat slower since the queries can require parsing at runtime, whereas static queries are parsed during deployment. The speed of dynamic queries can be increased, such as by extending them to take query parameters and caching the parsed query String.
- The foregoing description of preferred embodiments of the present invention has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations will be apparent to one of ordinary skill in the relevant arts. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, thereby enabling others skilled in the art to understand the invention for various embodiments and with various modifications that are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the claims and their equivalence.
Claims (16)
1. A system for dynamically generating a query to be executed on a database, comprising:
a properties object adapted to contain settings for a query as specified by a user;
a finder method for initiating the query; and
a server capable of querying the database, the server capable of receiving a call from the finder method and reading the settings from the properties object in order to generate the appropriate SQL query statements to be sent to the database.
2. A system according to claim 1 , further comprising:
a user interface adapted to allow a user to specify the settings in the property object.
3. A system according to claim 1 , further comprising:
a client containing the properties object and the finder method.
4. A system according to claim 1 , further comprising:
a bean associated with the database upon which the finder method can be invoked.
5. A system according to claim 1 , further comprising:
an element in a deployment descriptor for enabling dynamic querying.
6. A method for dynamically generating a query to be executed against a database, comprising:
generating a properties object containing settings for a query;
invoking a finder method;
extracting the settings from the properties object and parsing the finder method in order to generate a query statement; and
executing the query statement on the database.
7. A method according to claim 6 , wherein:
generating a properties object occurs at runtime.
8. A method according to claim 6 , wherein:
extracting the settings from the properties object and parsing the finder method in order to generate a SQL query statement occurs at runtime.
9. A method according to claim 6 , further comprising:
enabling dynamic querying by setting an element in a deployment descriptor.
10. A method according to claim 6 , further comprising:
allowing the user to specify the settings for the query at runtime.
11. A method for generating dynamic queries, comprising:
specifying settings to be used in generating the query using a user interface;
generating a properties object to hold the settings;
invoking a finder method; and
parsing the finder method and reading the settings from the property object in order to generate the query.
12. A system for generating dynamic queries, comprising:
means for generating a properties object to hold settings to be used in generating a query;
means for invoking a finder method; and
means for parsing the finder method and reading the settings from the property object in order to generate the query.
13. A computer-readable medium, comprising:
means for generating a properties object to hold settings to be used in generating a query;
means for invoking a finder method; and
means for parsing the finder method and reading the settings from the property object in order to generate the query.
14. A computer program product for execution by a server computer for generating dynamic queries, comprising:
computer code for generating a properties object to hold settings to be used in generating a query;
computer code for invoking a finder method; and
computer code for parsing the finder method and reading the settings from the property object in order to generate the query.
15. A computer system comprising:
a processor;
object code executed by said processor, said object code configured to:
generate a properties object to hold settings to be used in generating a query;
invoke a finder method; and
parse the finder method and reading the settings from the property object in order to generate the query.
16. A computer data signal embodied in a transmission medium, comprising:
a code segment including instructions to generate a properties object to hold settings to be used in generating a query;
a code segment including instructions to invoke a finder method; and
a code segment including instructions to parse the finder method and reading the settings from the property object in order to generate the query.
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/341,107 US20030163460A1 (en) | 2002-01-18 | 2003-01-13 | Systems and methods for dynamic querying |
PCT/US2003/001211 WO2003062987A1 (en) | 2002-01-18 | 2003-01-15 | Systems and methods for dynamic querying |
US11/393,044 US7587417B2 (en) | 2002-01-18 | 2006-03-30 | Systems and methods for dynamic querying |
US11/393,052 US7454438B2 (en) | 2002-01-18 | 2006-03-30 | System and methods for dynamic querying |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US34943202P | 2002-01-18 | 2002-01-18 | |
US10/341,107 US20030163460A1 (en) | 2002-01-18 | 2003-01-13 | Systems and methods for dynamic querying |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/393,044 Division US7587417B2 (en) | 2002-01-18 | 2006-03-30 | Systems and methods for dynamic querying |
US11/393,052 Division US7454438B2 (en) | 2002-01-18 | 2006-03-30 | System and methods for dynamic querying |
Publications (1)
Publication Number | Publication Date |
---|---|
US20030163460A1 true US20030163460A1 (en) | 2003-08-28 |
Family
ID=27616681
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/341,107 Abandoned US20030163460A1 (en) | 2002-01-18 | 2003-01-13 | Systems and methods for dynamic querying |
US11/393,044 Expired - Lifetime US7587417B2 (en) | 2002-01-18 | 2006-03-30 | Systems and methods for dynamic querying |
US11/393,052 Expired - Lifetime US7454438B2 (en) | 2002-01-18 | 2006-03-30 | System and methods for dynamic querying |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/393,044 Expired - Lifetime US7587417B2 (en) | 2002-01-18 | 2006-03-30 | Systems and methods for dynamic querying |
US11/393,052 Expired - Lifetime US7454438B2 (en) | 2002-01-18 | 2006-03-30 | System and methods for dynamic querying |
Country Status (2)
Country | Link |
---|---|
US (3) | US20030163460A1 (en) |
WO (1) | WO2003062987A1 (en) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020091702A1 (en) * | 2000-11-16 | 2002-07-11 | Ward Mullins | Dynamic object-driven database manipulation and mapping system |
US20040220956A1 (en) * | 2003-04-30 | 2004-11-04 | Dillon Software Services, Llc | Software framework that facilitates design and implementation of database applications |
US20050050040A1 (en) * | 2003-08-29 | 2005-03-03 | Dietmar Theobald | Database access statement parser |
US20050187958A1 (en) * | 2004-02-24 | 2005-08-25 | Oracle International Corporation | Sending control information with database statement |
US20050262072A1 (en) * | 2004-05-21 | 2005-11-24 | Bea Systems, Inc. | System and method for batch operation of CMP beans |
US20060004831A1 (en) * | 2004-06-07 | 2006-01-05 | Dirk Debertin | System and method for a query language mapping architecture |
US20060053087A1 (en) * | 2004-06-08 | 2006-03-09 | Pavlov Vladimir K | System and method for deploying enterprise components using deployment descriptors |
US20060173835A1 (en) * | 2002-01-18 | 2006-08-03 | Bea System, Inc. | System and methods for dynamic querying |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2015199532A2 (en) | 2014-06-26 | 2015-12-30 | Mimos Berhad | A method for managing key performance indicator queries in a database |
Citations (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5499371A (en) * | 1993-07-21 | 1996-03-12 | Persistence Software, Inc. | Method and apparatus for automatic generation of object oriented code for mapping relational data to objects |
US6199195B1 (en) * | 1999-07-08 | 2001-03-06 | Science Application International Corporation | Automatically generated objects within extensible object frameworks and links to enterprise resources |
US6266666B1 (en) * | 1997-09-08 | 2001-07-24 | Sybase, Inc. | Component transaction server for developing and deploying transaction- intensive business applications |
US6308179B1 (en) * | 1998-08-31 | 2001-10-23 | Xerox Corporation | User level controlled mechanism inter-positioned in a read/write path of a property-based document management system |
US6442541B1 (en) * | 1998-07-03 | 2002-08-27 | International Business Machines Corporation | Universal database adapters |
US6466933B1 (en) * | 1999-09-21 | 2002-10-15 | International Business Machines Corporation | Delayed delivery of query results or other data from a federated server to a federated client until such information is needed |
US6505200B1 (en) * | 2000-07-06 | 2003-01-07 | International Business Machines Corporation | Application-independent data synchronization technique |
US6694328B1 (en) * | 2000-01-13 | 2004-02-17 | International Business Machines Corporation | Method for creating queries on version objects |
US6748373B2 (en) * | 2002-05-01 | 2004-06-08 | Bea Systems, Inc. | System and method for adaptively optimizing queries |
US6760719B1 (en) * | 1999-09-24 | 2004-07-06 | Unisys Corp. | Method and apparatus for high speed parallel accessing and execution of methods across multiple heterogeneous data sources |
US6760812B1 (en) * | 2000-10-05 | 2004-07-06 | International Business Machines Corporation | System and method for coordinating state between networked caches |
US6823329B2 (en) * | 2002-04-02 | 2004-11-23 | Sybase, Inc. | Database system providing methodology for acceleration of queries involving functional expressions against columns having enumerated storage |
US6836889B1 (en) * | 1999-08-20 | 2004-12-28 | International Business Machines Corporation | Code wrapping to simplify access to and use of enterprise JAVA beans |
US6971085B1 (en) * | 2000-08-31 | 2005-11-29 | International Business Machines Corporation | Object oriented structured query language (OOSQL) support for enterprise java beans |
US6985912B2 (en) * | 2002-07-22 | 2006-01-10 | Thought, Inc. | Dynamic object-driven database manipulation and mapping system having a simple global interface and an optional multiple user need only caching system with disable and notify features |
US6996565B2 (en) * | 2001-09-06 | 2006-02-07 | Initiate Systems, Inc. | System and method for dynamically mapping dynamic multi-sourced persisted EJBs |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6539396B1 (en) | 1999-08-31 | 2003-03-25 | Accenture Llp | Multi-object identifier system and method for information service pattern environment |
US6640244B1 (en) | 1999-08-31 | 2003-10-28 | Accenture Llp | Request batcher in a transaction services patterns environment |
US6571282B1 (en) | 1999-08-31 | 2003-05-27 | Accenture Llp | Block-based communication in a communication services patterns environment |
US6999956B2 (en) | 2000-11-16 | 2006-02-14 | Ward Mullins | Dynamic object-driven database manipulation and mapping system |
CA2327167C (en) * | 2000-11-30 | 2007-10-16 | Ibm Canada Limited-Ibm Canada Limitee | Method and system for composing a query for a database and traversing the database |
US6687702B2 (en) | 2001-06-15 | 2004-02-03 | Sybass, Inc. | Methodology providing high-speed shared memory access between database middle tier and database server |
US20030163460A1 (en) | 2002-01-18 | 2003-08-28 | Matthew Shinn | Systems and methods for dynamic querying |
US7089230B2 (en) * | 2002-06-07 | 2006-08-08 | International Business Machines Corporation | Method for efficient processing of multi-state attributes |
US7707544B2 (en) * | 2002-12-05 | 2010-04-27 | Bea Systems, Inc. | System and method for generating and reusing software application code with source definition files |
-
2003
- 2003-01-13 US US10/341,107 patent/US20030163460A1/en not_active Abandoned
- 2003-01-15 WO PCT/US2003/001211 patent/WO2003062987A1/en not_active Application Discontinuation
-
2006
- 2006-03-30 US US11/393,044 patent/US7587417B2/en not_active Expired - Lifetime
- 2006-03-30 US US11/393,052 patent/US7454438B2/en not_active Expired - Lifetime
Patent Citations (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5499371A (en) * | 1993-07-21 | 1996-03-12 | Persistence Software, Inc. | Method and apparatus for automatic generation of object oriented code for mapping relational data to objects |
US6266666B1 (en) * | 1997-09-08 | 2001-07-24 | Sybase, Inc. | Component transaction server for developing and deploying transaction- intensive business applications |
US6442541B1 (en) * | 1998-07-03 | 2002-08-27 | International Business Machines Corporation | Universal database adapters |
US6308179B1 (en) * | 1998-08-31 | 2001-10-23 | Xerox Corporation | User level controlled mechanism inter-positioned in a read/write path of a property-based document management system |
US6199195B1 (en) * | 1999-07-08 | 2001-03-06 | Science Application International Corporation | Automatically generated objects within extensible object frameworks and links to enterprise resources |
US6836889B1 (en) * | 1999-08-20 | 2004-12-28 | International Business Machines Corporation | Code wrapping to simplify access to and use of enterprise JAVA beans |
US6466933B1 (en) * | 1999-09-21 | 2002-10-15 | International Business Machines Corporation | Delayed delivery of query results or other data from a federated server to a federated client until such information is needed |
US6760719B1 (en) * | 1999-09-24 | 2004-07-06 | Unisys Corp. | Method and apparatus for high speed parallel accessing and execution of methods across multiple heterogeneous data sources |
US6694328B1 (en) * | 2000-01-13 | 2004-02-17 | International Business Machines Corporation | Method for creating queries on version objects |
US6505200B1 (en) * | 2000-07-06 | 2003-01-07 | International Business Machines Corporation | Application-independent data synchronization technique |
US6971085B1 (en) * | 2000-08-31 | 2005-11-29 | International Business Machines Corporation | Object oriented structured query language (OOSQL) support for enterprise java beans |
US6760812B1 (en) * | 2000-10-05 | 2004-07-06 | International Business Machines Corporation | System and method for coordinating state between networked caches |
US6996565B2 (en) * | 2001-09-06 | 2006-02-07 | Initiate Systems, Inc. | System and method for dynamically mapping dynamic multi-sourced persisted EJBs |
US6823329B2 (en) * | 2002-04-02 | 2004-11-23 | Sybase, Inc. | Database system providing methodology for acceleration of queries involving functional expressions against columns having enumerated storage |
US6748373B2 (en) * | 2002-05-01 | 2004-06-08 | Bea Systems, Inc. | System and method for adaptively optimizing queries |
US6985912B2 (en) * | 2002-07-22 | 2006-01-10 | Thought, Inc. | Dynamic object-driven database manipulation and mapping system having a simple global interface and an optional multiple user need only caching system with disable and notify features |
Cited By (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6999956B2 (en) * | 2000-11-16 | 2006-02-14 | Ward Mullins | Dynamic object-driven database manipulation and mapping system |
US20020091702A1 (en) * | 2000-11-16 | 2002-07-11 | Ward Mullins | Dynamic object-driven database manipulation and mapping system |
US7454438B2 (en) | 2002-01-18 | 2008-11-18 | Bea Systems, Inc. | System and methods for dynamic querying |
US20060173835A1 (en) * | 2002-01-18 | 2006-08-03 | Bea System, Inc. | System and methods for dynamic querying |
US7587417B2 (en) | 2002-01-18 | 2009-09-08 | Bea Systems, Inc. | Systems and methods for dynamic querying |
US20060173832A1 (en) * | 2002-01-18 | 2006-08-03 | Bea Systems, Inc. | Systems and methods for dynamic querying |
US20080249972A1 (en) * | 2003-04-30 | 2008-10-09 | Dillon David M | Software framework that facilitates design and implementation of database applications |
US7412455B2 (en) | 2003-04-30 | 2008-08-12 | Dillon David M | Software framework that facilitates design and implementation of database applications |
US20040220956A1 (en) * | 2003-04-30 | 2004-11-04 | Dillon Software Services, Llc | Software framework that facilitates design and implementation of database applications |
US9009195B2 (en) * | 2003-04-30 | 2015-04-14 | Rpx Corporation | Software framework that facilitates design and implementation of database applications |
US20050050040A1 (en) * | 2003-08-29 | 2005-03-03 | Dietmar Theobald | Database access statement parser |
US7496569B2 (en) * | 2003-08-29 | 2009-02-24 | Sap Ag | Database access statement parser |
US20050187958A1 (en) * | 2004-02-24 | 2005-08-25 | Oracle International Corporation | Sending control information with database statement |
US8825702B2 (en) * | 2004-02-24 | 2014-09-02 | Oracle International Corporation | Sending control information with database statement |
US7529759B2 (en) * | 2004-05-21 | 2009-05-05 | Bea Systems, Inc. | System and method for batch operation of CMP beans |
US20050262072A1 (en) * | 2004-05-21 | 2005-11-24 | Bea Systems, Inc. | System and method for batch operation of CMP beans |
US20060004831A1 (en) * | 2004-06-07 | 2006-01-05 | Dirk Debertin | System and method for a query language mapping architecture |
US7631303B2 (en) * | 2004-06-07 | 2009-12-08 | Sap Aktiengesellschaft | System and method for a query language mapping architecture |
US20060053087A1 (en) * | 2004-06-08 | 2006-03-09 | Pavlov Vladimir K | System and method for deploying enterprise components using deployment descriptors |
Also Published As
Publication number | Publication date |
---|---|
US20060173835A1 (en) | 2006-08-03 |
US7454438B2 (en) | 2008-11-18 |
WO2003062987A1 (en) | 2003-07-31 |
US20060173832A1 (en) | 2006-08-03 |
US7587417B2 (en) | 2009-09-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7587417B2 (en) | Systems and methods for dynamic querying | |
US6032151A (en) | Database system employing polymorphic entry and entry matching | |
US6567809B2 (en) | Disabling and reloading enterprise java beans using database trigger programs | |
US7433917B2 (en) | Method and apparatus for using Java dynamic proxies to interface to generic, bean-like management entities | |
US6370686B1 (en) | Method for categorizing and installing selected software components | |
US8775470B2 (en) | Method for implementing fine-grained access control using access restrictions | |
US5627979A (en) | System and method for providing a graphical user interface for mapping and accessing objects in data stores | |
US5930795A (en) | Supporting dynamic tables in SQL query compilers | |
US7080361B2 (en) | Process for generating enterprise java bean components from an SQL database | |
US7055132B2 (en) | System and method for associating properties with objects | |
US7310647B2 (en) | Column masking of tables | |
US8019735B2 (en) | Systems and methods for query caching | |
US8453109B2 (en) | Framework for code generators | |
EP1040434A1 (en) | Methods and apparatus for efficiently splitting query execution across client and server in an object-relational mapping | |
US6598093B1 (en) | Method and apparatus for a core application programming interface | |
US7548901B2 (en) | System and method for delayed fetching of designated members of a user defined type | |
US6938050B2 (en) | Content management system and methodology employing a tree-based table hierarchy which accomodates opening a dynamically variable number of cursors therefor | |
US20060015483A1 (en) | SQL query enhancement technique | |
US7133875B1 (en) | Method and apparatus for redefining a group of related objects in a relational database system | |
US7702691B2 (en) | Systems and methods for EJB finders using SQL | |
US20060015471A1 (en) | System, Method, and Computer Program Product of Building A Native XML Object Database | |
US7447675B2 (en) | Systems and methods for cursored collections | |
US20050160091A1 (en) | Macro-based dynamic discovery of data shape | |
US6985911B2 (en) | Mechanism for invocation of user-defined routines in a multi-threaded database environment | |
Girling et al. | The Property Repository |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: BEA SYSTEMS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SHINN, MATTHEW;WHITE, SETH;WOOLLEN, ROB;REEL/FRAME:014029/0714 Effective date: 20030423 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |