Hi Dan, > Hi Kevin, First off, I think we should distinguish between results > that are rendered in the UI, vs those that are only ever returned to > a domain object.
Yes, I am looking at the latter - internal collections used by the domain, and not for rendering to the UI. Just to confirm - it is your opinion that it is OK for the SQL OS to return "all" (or at least the limit imposed by "isis.persistor.sql.maxinstances")? I was wondering about memory usage and the like, but perhaps with no real justification? Yes, sure - let me create a JIRA ticket for extending the general OS API to support paging. This also has issues - a custom Paging module will be needed, and chosen at runtime, to build the associated paging syntax into the SQL query. But that's a discussion for isis-dev@iao. Regards, Kevin On 24 Mar 2012 at 14:29, Dan Haywood wrote: > > You have the latter case, and my feeling is that the SQL OS shouldn't > really limit the rows. But since the SQL OS can't really "tell" how it is > being called, it probably implies that it should always return all the > rows, and then (for the former case) that the viewer layer should take > responsibility for paging. It is a presentation concern, after all. >
