[
https://issues.apache.org/jira/browse/WICKET-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619904#action_12619904
]
Igor Vaynberg commented on WICKET-1766:
---------------------------------------
well, there you go. you have tied visibility to rowcount yourself...
if you really do not want the double query and are ok with inconsistent data
then you can cache the size yourself in your dataprovider and clear it in
dataprovider.detach().
by default, i think the framework should work as it does now and avoid any
chance of inconsistency - leave the optimizations up to the developer.
shall we close this issue?
> Method size() of a data provider is invoked twice.
> --------------------------------------------------
>
> Key: WICKET-1766
> URL: https://issues.apache.org/jira/browse/WICKET-1766
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.4
> Environment: Ubuntu
> Reporter: Rik van der Kleij
> Assignee: Igor Vaynberg
> Priority: Minor
>
> Method size() of a data provider is invoked twice during one request. This
> happens when navigating to a next or latest page in a data table. During
> debugging I noticed that the onDetach() of AbstractPageableView is invoked an
> extra time. Implementations of size() normally query the database so it will
> slow down the performance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
