I want to optimize ORDER BY operations on a selection of records using multiple fields using 4D v14+.
In the past using ORDER BY on a selection of records specifying a single field that is indexed, will result in the order by using the index and being very fast. We all know this. It is a given using 4D. But when you do ORDER BY and specifying multiple fields the order by is always slower and required loading all records in the selection and doing a sequential order by. It does not us indexes. This is my understanding of how 4D used to work. I am wondering if that is still the case with 4D v14+? Question: If I create a composite index for a table that contains 2 fields, and you do an ORDER BY on the table using these 2 fields, does the 4D database engine use this composite index and do a fast sort, or does it still load all the records and do a sequential sort? Tim ******************************************** Tim Nevels Innovative Solutions 785-749-3444 [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] **********************************************************************
