Still is being disputed unfortunately :( https://issues.apache.org/jira/browse/WICKET-1784
For those who believe in the 1-query approach, ergo the DTO pattern, writing an alternative to the Wicket data provision using a DTO approach isn't a terrible hardship ... just annoying to be sprung with on day one of using Wicket. But pain is experienced later when encountering the Wicket data provision and paging mechanism coupling. The paging mechanism is far less joy to replace ... IReallyHateDataProvider Hoover, William wrote: > > I think the idea behind this is that size will be called first. If the > size is zero there is no need to proceed with the call to get the items. > I don't necessarily agree with this approach because a lot of service > calls can capture the data in one call (even down to the database level- > some support getting the size/results in one call), but the last time I > brought this issue up it was disputed. > -- View this message in context: http://www.nabble.com/Is-there-any-other-way--DataProviders-must-hit-the-Db-twice-for-%28possible%29-large-datasets-tp20701684p20708929.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]
