Yes, forgot to mention that - it's in the dictionary entry for revExecuteSQL as well.
I think the decision as to whether to use a database versus LC internal storage depends on a lot of factors, including memory and access speed, but also multi-user issues, the application's access requirements, availability of the data to other applications, etc. I've personally never run into either memory or performance issues with SQLite but I'm mainly dealing with tables that contain < 10,000 entries and almost always working on a subset of them. No doubt using LC internal storage would be faster but not to any significant degree for dbs of that size. In my case, I almost always need the relational aspects of a database to handle the data so SQL databases work for me - horses for courses as they say. On Tue, Dec 20, 2011 at 3:44 PM, Bernard Devlin <[email protected]> wrote: > One thing that has not been brought out so far in this discussion is > that when passing data to a SQL statement in Livecode, it is possible > to have your data stored in an array with numbered keys e.g. > myArray[1], myArray[2]... and then to pass that array's name to the > Livecode SQL functions using :1, :2... to pass in the data. > > Search the following page for this line of text: | revExecuteSQL > myID,"insert into mytable values(:1,:2,:1)","myArray" | > > http://docs.runrev.com/Command/revExecuteSQL > -- Pete Molly's Revenge <http://www.mollysrevenge.com> _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
