what exactly loads twice? dataview only makes two queries: one for the size of the dataset and one for the window of data it is going to render.
-igor On Mon, Oct 6, 2008 at 1:07 AM, jensiator <[EMAIL PROTECTED]> wrote: > > Hello > Im working on a Pageable dataview using SortableDataProvider and I have > trouble to find out how It should be done regarding memory use versus > database requests. I've looked on the repeaters live action and read the > model chapter in "wicket in action". > > 1. If I dont use the loadabledetachableModel I need to implement > Serializable in my modelobject corrensponding to a row in the dataview. > Wicket wants to serialize the modelobject to the session. What will/might > happen to the webapplication memory if I choose this approach? How long will > the data be stored in the session? > > 2. All the examples I have seen regarding the loadable approach seems to be > calling the db a little to much. When implementing the SortableDataProvider > iterator method, all examples call the db for the data to be shown in the > current page. Then the model extending LoadableDetachableModel will load (in > load method) the Models data again from some kind of identifier. It seems to > be that were loading all data twice. Is this how it should be done? > > Jens Alenius > -- > View this message in context: > http://www.nabble.com/Serializing-model.-DetachedModel-or-not-tp19833559p19833559.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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]
