On Thu, Oct 12, 2017 at 6:57 AM, Arnaud de Montard via 4D_Tech < 4d_tech@lists.4d.com> wrote:
> > It's a solution if the selection is huge (is it?). But sort selection > (I've always found 4d sort is slow), then 2 selection to array, that's 3 > server calls, at end. I'd prefer selection to array (1 call), sort array, > read first and last items in array. > Agreed. I'd want to know that there is any optimization needed past FIRST RECORD and LAST RECORD before diving into anything else. And, past that, you would want to balance the cost of pulling more data over the network in once call with pulling tiny bits of data over the network with multiple calls. I suspect this is getting a bit silly, but another idea is to have an method set to "Execute on server" that does the work and packs the results in an object and returns it. Yeah, that might work. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
