[mailto:michael.ocleir...@rivulet.ca]
Verzonden: dinsdag 7 september 2010 20:43
Aan: users@wicket.apache.org
Onderwerp: Re: DB lookup time-out within DataTable Iterator
Hi Frank ,
Are you sure that your dao is setting max results on the underlying
query? The provider.iterator(...) should only be returning
Hi guys!
Breaking my head on the following, hopefully someone might be able to
give me a hint?
In a page which serves a view on a log database with quite a lot of
rows, I am using a DataTable to show the rows. The data for the table is
being served by a SortableDataProvider which looks a bit
Hi Frank,
Just an idea... If you do the filtering via AJAX you could use the
same AJAX request to:
1- display a modal window in case you get the timeout error: just
place the ModalWindow on your page do
modalWindow.addOrReplace(new
MyErrorMessagePanel(modalWindow.getContentId())); and use
Hi Frank ,
Are you sure that your dao is setting max results on the underlying
query? The provider.iterator(...) should only be returning the current
page values and typically the page size would be small like 25 to 100.
Also it depends on your backend database since I know that some
It could be returning only 25 rows, but the criteria itself is what
makes the query slow. In that case, I'd recommend looking at your
indexes. Sometimes indexing doesn't help very much, though.
On Tue, Sep 7, 2010 at 2:43 PM, Michael O'Cleirigh
michael.ocleir...@rivulet.ca wrote:
Hi Frank ,
