I am having a problem with designing pagination of big results from a database query. It is not a problem of the code but rather of the design.
and here is the problem: I hesitate between using 2 different methods for paginating (show only one page of results) of a large db-query (via Torque).
1. just use count(*) in the query with the given criteria, this results in total row number so I can easily calculate Offset and Limit for the Criteria to get a specified page
*pros*: easy and simple. works in my current project
*cons*: performance - doubling queries, some queries might contain searches....
2. use LargeSelect
*pros*: elegant, nice with searches... can store multiple pages in user.Temp. less queries to database
*cons*: having ~200-300 sessions at the time... I hope would be fine as well.
another problem is: returned rows correspond e.g. to messages in a discussion list. LargeSelect caches the results.... some users however simply click "refresh" to see if there is sth. new.... so a solution would be to set a timeout for LargeSelect to invalidate it.
generally: is it worth to use LargeSelect? what do you use?
thanx and regards - michal f. www.fotoforum.pl
BTW: I am putting my site, a multi-user photo gallery (www.fotoforum.pl), in the Turbine framework... it is php now :-(
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
