Hi Kevin, Yes personally I wouldn't depend on fetching an entire resultset, just in case it is huge. So yes I would alter Isis to cater for paging "where possible"
Like you say some SQL servers may not support paging. I dont know how big a problem this would be in practice, I'd be inclined to ignore it for now / flag it for a future solution such as faking via primary key etc. Best Regards Mike Burton Myco Systems Ltd 01753 893390 17 Criss Grove, Gerrards Cross, BUCKS, SL9 9HG Registered in England No 1832705 NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. On 23 Mar 2012, at 17:21, Kevin Meyer - KMZ wrote: > Hi Mike, > > Indeed - But paging is not currently supported by the Isis ObjectStore > interface.. It is something that has troubled me in the past, and I've > considered adding versions of the "allInstances" and "allMatches" > methods that include paging - but there's a whole different problem - > getting paging to work across all the supported SQL servers. And > that's a problem for isis-dev@iao. > > But does this mean that you *would not* encourage an existing user > domain problem (that uses the Isis objectstores) to rely on fetching all > instances, as the object store currently stands? That you recommend > altering the Isis framework? > > Regards, > Kevin > > > > > On 23 Mar 2012 at 16:04, Mike Burton wrote: > >> Hi Kevin, >> >> I have tended to use the paging mechanisms of HQL and JBoss Seam's >> Application Framework, so maybe use a similar approach? I think they >> have some kind of Proxy to fetch "a pageful" of rows. >> >> Best Regards >> >> Mike Burton >> >
