That's what I do when I have an indeterminate number of keys, or if I am writing generic code that handles data from dissimilar tables in a similar way. Do what you want, but best practice (with good reason) seems to still be to use parameterized queries except where you cannot.
On Fri, May 20, 2016 at 2:25 PM, Dr. Hawkins <doch...@gmail.com> wrote: > On Wed, May 18, 2016 at 7:17 PM, Mike Kerner <mikeker...@roadrunner.com> > wrote: > > > Why not just use parameterized queries? > > > Is this practical when using a compound query (in a BEGIN/END with dozens > to hundreds of commands)? > > It would seem that I would have to make an "interesting" loop to create a > huge array, and and code the keys back into my statements . . . > > > -- > Dr. Richard E. Hawkins, Esq. > (702) 508-8462 > _______________________________________________ > 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 > -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." _______________________________________________ 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
