> yeah i sincerely believe issuing a row count() is an expensive, especially > when the row count doesn't change at all
Like it is said in the other thread, you should then look at caching the count in either the data provider or the, if the data provider calls a service to get the count, in the service. If you do the latter, you'll cache one long for your whole application, so that won't be a memory hog. Eelco ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
