Hi Tom. So the little benchmarking I did originally showed that my method was a little longer, as I still have to iterate once through the array to populate the database. Where it really shines is that you can do complex queries, as well as multiple column sorts before converting back to an array. Also, if you need to make multiple passes at the data, the speed of course exceeds iterating through the array again and again. Finally, since it's in a database, it's persistent through idle, whereas an array would have to be stored in a script local or a property if you needed it across runtime sessions.
Bob S > On Jun 20, 2019, at 21:10 , Tom Glod via use-livecode > <use-livecode@lists.runrev.com> wrote: > > A great question Jacque ....Helpful thread all around. > > I have a tendency to think that any operation i perform to convert an > entire array into something else will take longer than to loop through the > keys. I'm happy to be wrong ,and I imagine it depends on the number of > items in the dataset. But for my particular use at the moment, I find LC > performance to be excellent. > > Bob I'm interested in your library......mostly learning the point at which > it makes sense to do that conversion and what kind of speedups can > occur.....have you done any benchmarks on it? > > Great reminder & idea Monte _______________________________________________ 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
