openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srinivasa (JIRA)" <>
Subject [jira] Updated: (OPENJPA-175) Eager selects by PagingResultObjectProvider may not use the FetchBatchSize
Date Wed, 21 Mar 2007 22:58:32 GMT


Srinivasa updated OPENJPA-175:

1 - Yes, was planning to do it as a separate JIRA given that it directly does not concern
the issue raised here, however I will include it here since we are introducing the in-clause
limit in the DBDictionary for this fix.
2 - Looks fine to me, except for the minor issue that in the (size <= batch * 2) case we
will not be adhering to the FetchBatchSize for pageSize in that the first in-clause query
will be for lesser than the FetchBatchSize number of entries, however we will still endup
running the same number of in-clause queries - 2.

> Eager selects by PagingResultObjectProvider may not use the FetchBatchSize
> --------------------------------------------------------------------------
>                 Key: OPENJPA-175
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 0.9.0, 0.9.6
>            Reporter: Srinivasa
>         Attachments: OPENJPA-175-patch.txt, OPENJPA-175-patch.txt
> The PagingResultObjectProvider during initialization does checks to determine the appropriate
pageSize. While this logic caps the size to 50 and addresses determining an appropriate page
size, it doesn't always conform to the set batch size. For example with the size being 1000
and FetchBatchSize set to say 500, the page size is determined to be 50 resulting in eager
selects happening in batches of 50 when the user expects it to be in batches of 500. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message