On 24 March 2012 14:47, Kevin Meyer - KMZ <[email protected]> wrote: > > 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")? >
Yes, it's ok. > > I was wondering about memory usage and the like, but perhaps with > no real justification? > I wouldn't worry about it. If the domain object really needs to process all the objects, then that's what it needs to do. > > 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. > OK > > 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. > > > > >
