Hi, If your queries are so expensive you can just keep its results as a member in your component. Make a new query each time a filter changes, and let your dataProvider just iterate over the cached list.
Note that your Data gets serialized with your page though. Sven > > On 19.11.2018 at 12:00, <Sandor Feher> wrote: > > > Hi Sven, Sorry, I did not notice your answer so far. Okay. Let's try to see > things from different angle :) Yes I use spring. I tried to reduce the number > of unnecessary queries. To achieve this I try to catch if my table filtered > or a new item added or a dropdownchoice changed and so on. It works more or > less but there is no method to catch an ajax table refresh for example > (Catching it in detach() method is bad practice you made me sure) Here is a > simple DataProvider I use. The question is that which point should I reload > data using customBo? At size() or Iterator ? What is the best practice for > this ? -- Sent from: > http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html > --------------------------------------------------------------------- To > unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional > commands, e-mail: users-h...@wicket.apache.org >
