Distinct values is a function that scans data and creates a count of the entries. It may or may not use an index.
Selection to array loads records, copies the field data in to arrays, and transmits the data. If you're asking "If I'm doing S2A on indexed fields, why can't it grab the data from the index and arrange it as if the data were to have come from records?" My thought on that question "Well, that *is* an intriguing question but it doesn't work that way." What makes it interesting is that one would assume that index entries are more efficiently located than records so it could be faster. -- Douglas von Roeder 949-336-2902 On Fri, Aug 12, 2016 at 2:12 PM, Richard Wright < [email protected]> wrote: > > > Date: Fri, 12 Aug 2016 12:39:15 -0400 > > From: Chip Scheide <[email protected]> > > > > > > I would expect: > > ... > > > > Regardless of an index, Selection to Array has to copy all the data > > from the field(s) specified, for the selection, into an array. > > Why can’t it use the index if I’m selecting nothing but fields that are > indexed? Distinct Values obviously does this. > > ------------------------------------------------ > Richard Wright > DataDomain > [email protected] > ------------------------------------------------ > > ********************************************************************** > 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:[email protected] > ********************************************************************** > ********************************************************************** 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:[email protected] **********************************************************************
