ibatis-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Butler (JIRA)" <ibatis-...@incubator.apache.org>
Subject [jira] Closed: (IBATIS-308) Optimize result set fetches for stored procs
Date Tue, 20 Jun 2006 01:21:31 GMT
     [ http://issues.apache.org/jira/browse/IBATIS-308?page=all ]
Jeff Butler closed IBATIS-308:

    Fix Version: 2.2.0
     Resolution: Fixed

Fixed in SVN.

> Optimize result set fetches for stored procs
> --------------------------------------------
>          Key: IBATIS-308
>          URL: http://issues.apache.org/jira/browse/IBATIS-308
>      Project: iBatis for Java
>         Type: Improvement

>   Components: SQL Maps
>     Versions: 2.0.8, 2.0.9, 2.1.0, 2.0.9b, 2.1.5, 2.1.6, 2.1.7
>  Environment: Applicable to any
>     Reporter: Amit Kushwaha
>     Assignee: Jeff Butler
>      Fix For: 2.2.0

> Executing queries contained in stored procedures, optimize result set fetches if the
fetch size on the Statement(BaseStatement) is specified. This will improve performance by
getting multiple records out from the database per round trip as specified by  the fetch size.
Some drivers have a default fetch value, for example, Oracle set's the fetch size to 10 by
default. And overriding the default fetch size if useful in cases when the SQL query executed
returns a large number of rows.
> At the moment, its possible to set the fetch size on the BaseStatement. And it takes
effect while executing the query using a PreparedStatement but not on a CallableStatement.
So in SqlExecutor, in executeQueryProcedure, we should set the fetch size on the CallableStatement,
if a fetch size is specified on the BaseStatement as is done in the executeQuery method. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message