Hlello again, it seems I've run across another problem. I have a result page that shows the results of various queries entered by a user. The results page contains two displaytag tables each of which is paginated and has sorting enabled on all columns. Everything works flawlessly (short of my earlier problem about having column totals and pagination) on all result sets <10,000 +-, however, one result set in particular can range from 20,000 - 100,000. Unfortunately I'm not able to mock up examples right now for the whole range of potential sizes but at 85,000 records, the pagination and sorting barely work if at all. 9 out of 10 times the sorting does nothing - it refreshes the page but adds not request parameters and does not sort the column; pagination also works unreliably, it will refresh the page but will not actually display the selected page.
I'm not sure if this is just a limitation of displaytag when dealing with a somewhat obscenely sized result set or whether there is something I'm missing here. The result page is a redirect from a form, so the data is not being pulled from the database again on each sort/page select. So is this just a limitation of displaytag or is there something I'm missing/a way of tackling this problem? Thanks much, insight appreciated. -- View this message in context: http://www.nabble.com/Displaytag-column-sorting-and-large-result-sets-tf3262747.html#a9068808 Sent from the DisplayTag - General mailing list archive at Nabble.com. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ displaytag-user mailing list displaytag-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/displaytag-user
