The paging concept is a good idea, but you must be careful: some modules in the Class::DBI family (such as Class::DBI::Pager) do a full SELECT of your data and then only show the requested page, so you do not save on database processing time. Use of the LIMIT-function (as exists in MySQL) would be really helpful here (as implemented in Class::DBI::Plugin::Pager). Again you must take care: if the amount of data changes between calls to display "next" and "previous" pages, the results may be not what you expect.
CountZero "If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law
| [reply] [d/l] |