detach() is indeed called in the end of every request. what exactly is your requirement? you want to run the query once, upon page entry, and then always reuse the same resultset without doing another query? in that case store the list of ids in your resultset as a property of the page. the model of the listview can then retrieve the subset of this list (based on the current page and number of items needed) and do a select from foo where id in ( subset of id list ) query to retrieve the current window of data.
-igor On Mon, Jun 23, 2008 at 11:25 AM, Jürgen Lind <[EMAIL PROTECTED]> wrote: > Hi, > > I a currently a bit stuck in dealing with a PageableListView and a > detachable > model. I have build my own model that wraps a list of search results that > should > exists as long as the page remains the same, i.e. across all requests that > go > to the same page such as for navigation or sort actions. As soon as the page > is > left, e.g. when the user navigates to the "details" page of a certain > result, > the search result list is cleared. > > However, it appears that the "detach" method is called immediately after the > PageableListView is rendered, i.e. at the end of each request. Is this > observation correct? And how would I deal with a requirement as described > above? > > Cheers, > > J. > > > -- > Dr. Jürgen Lind > iteratec GmbH Fon: +49 (0)89 614551-44 > Inselkammerstrasse 4 Fax: +49 (0)89 614551-10 > 82008 Unterhaching Web: www.iteratec.de > > Sitz und Registergericht der iteratec GmbH: München HRB 113 519 > Geschäftsführer: Klaus Eberhardt, Mark Goerke, Inge Hanschke, Ralf Menzel > > > --------------------------------------------------------------------- > 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]
