Using equal queries is efficient *if* the columns are indexed. If you use LIKE, I do not believe that the indexes are used, unless you employ some kind of full text search indexing. Only certain databases support that.
Bob S > On Aug 23, 2017, at 12:07 , Sannyasin Brahmanathaswami via use-livecode > <use-livecode@lists.runrev.com> wrote: > > At least for theme and genre these are direct "hits" because there is an > "equals" look up against these two enum values; but the searchString look up > will still need to use %like% for "blues" is in "title, subtitle and > description" . I have to check my sql query hand book aka "the internets" to > see if there is an efficient way to write that query. > > So then it comes down to whether doing a query semi-complex query that looks > at 50,000 records and uses %like% against 3 columns is faster than iterating > loops on a 1000 key array already in memory. > > I can't wait to use the new tools for watching processes to see where bottle > necks arise… _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
