You're better off asking this question on the [EMAIL PROTECTED] mailing list. Here's a quick answer:
The display tag library is just that - a tag library, meant for viewing and iterating lists. As far as dealing with your backend data, that's up to (as far as it's concerned). If you want to limit and such, you can probably trap the request parameters in your Action and adjust your query accordingly to retrieve the proper dataset. HTH, Matt -----Original Message----- From: Michael Muller [mailto:[EMAIL PROTECTED] Sent: Friday, September 26, 2003 3:53 PM To: Struts Users Mailing List Subject: display tags and large result sets I'd love to use this package, but I often deal with large result sets returned from a database. I'm afraid that I wouldn't be able to support many users if I kept sucking the whole table into memory. I deal with this manually by using MySQL's LIMIT and OFFEST syntax. Clicking on column headers changes the ORDER BY of the query. I gave the docs a quick look and didn't see anything that looked like it would support something like this. Did I miss anything? How hard would it be to enhance the tag to support this? -- Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
