Difference between revisions of "Using the Query Tool"
Line 2: | Line 2: | ||
Another benefit of the query tool is that it allows you to use JDBC prepared statements, which is more efficient because the query can be reused for different parameters, rather than a different query being passed to your database each time, which is the case with the delegator. (See [http://www.onjava.com/pub/a/onjava/excerpt/oraclejdbc_19/index.html this article about JDBC performance tuning].) | Another benefit of the query tool is that it allows you to use JDBC prepared statements, which is more efficient because the query can be reused for different parameters, rather than a different query being passed to your database each time, which is the case with the delegator. (See [http://www.onjava.com/pub/a/onjava/excerpt/oraclejdbc_19/index.html this article about JDBC performance tuning].) | ||
+ | |||
+ | This feature is in the opentaps 1.0 trunk. For older versions of opentaps, this [http://sourceforge.net/tracker/index.php?func=detail&aid=1986968&group_id=145855&atid=948961 patch] is available. | ||
== How It Works == | == How It Works == |
Revision as of 18:45, 12 June 2008
A common problem with the ofbiz entity engine and delegator is that it could be difficult to construct complex queries. To solve this problem, we created an opentaps query tool, which works with the ofbiz delegator but allows you to write your queries in familiar SQL. The query tool could then return the results of your query as a ResultSet, a List of Maps, a List of entity engine GenericValues, or the entity engine's EntityListIterator.
Another benefit of the query tool is that it allows you to use JDBC prepared statements, which is more efficient because the query can be reused for different parameters, rather than a different query being passed to your database each time, which is the case with the delegator. (See this article about JDBC performance tuning.)
This feature is in the opentaps 1.0 trunk. For older versions of opentaps, this patch is available.
How It Works
To use the query tool, create a QueryFactory from the delegator:
import org.opentaps.common.query.*; QueryFactory qf = new QueryFactory(delegator);
Then, use your QueryFactory to create either a Query. The syntax should be similar to Hibernate querying:
Query q = qf.createQuery("SELECT * FROM STATUS_ITEM WHERE STATUS_ID LIKE 'INVOICE%'");
You can then run your query in the following ways:
// run the query and get result set q.executeQuery(); ResultSet rs = q.getResultSet(); // run the query and get it back as a List of Maps or the first value as a Map List list1 = q.list(); Map map1 = q.firstResult(); // run the query and get an EntityListIterator. Specify the entity name and optionally a list of fields EntityListIterator eli1 = q.entityListIterator("StatusItem"); EntityListIterator eli2 = q.entityListIterator("StatusItem", UtilMisc.toMap("statusId", "statusTypeId", "description")); // run the query and get a List of GenericValues. Specify the entity name and optionally a list of fields List list3 = q.entitiesList("StatusItem"); List list4 = q.entitiesList("StatusItem", UtilMisc.toList("statusId", "statusTypeId", "description"));
You can also add prepared queries, get the statement, and run it:
Query q2 = qf.createQuery("SELECT * FROM STATUS_ITEM WHERE STATUS_ID LIKE ? AND STATUS_TYPE_ID LIKE ?"); PreparedStatement ps = q2.getStatement(); ps.setString(1, "%APPROVE%"); ps.setString(2, "INVOICE%"); List list5 = q2.list();
Technical Notes
When the Query is first instantiated, a PreparedStatement is instantiated, and on the first call to a method which would cause the query to be executed, such as .list(), the PreparedStatement is called, a ResultSet is obtained, converted to a List, and then closed. Subsequent calls to .list() only return the previously stored list and does not cause another query to be run. If you need to run the query again, call .clearQueryResults();
Converting the query results to GenericValues/GenericEntities requires the use of the ofbiz entity engine's EntityListIterator. If you use the .entityListIterator(..) method, the EntityListIterator will be returned to you, and it will handle the closing of the connection with its own .close() method. If you use the .entitiesList(..) methods, the EntityListIterator and the ResultSet will be automatically closed.
The ResultSet is automatically closed on finalize().
The Query and QueryFactory throw a QueryException. If GenericValues/GenericEntities are involved, they also will throw the GenericEntityException.