You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2017/10/13 09:31:00 UTC

[jira] [Updated] (TAP5-2589) Improve Grid implementation for "slow" data sources

     [ https://issues.apache.org/jira/browse/TAP5-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade updated TAP5-2589:
---------------------------------
    Fix Version/s: 5.5.0

> Improve Grid implementation for "slow" data sources
> ---------------------------------------------------
>
>                 Key: TAP5-2589
>                 URL: https://issues.apache.org/jira/browse/TAP5-2589
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>            Reporter: Jochen Kemnade
>             Fix For: 5.5.0
>
>
> When using a Grid that's backed by a data source for which performing a count is expensive, performance is quite bad.
> There are some places where Grid (and subcomponents) call {{getAvailableRows()}} to determine whether the data source is empty or has (at least) a specific number of results. We should provide (and use) more specific and efficient methods in {{GridDataSource}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)