On Sat, Aug 18, 2012 at 11:28 AM, Peter Haworth <p...@lcsql.com> wrote:
> You don't HAVE to remove the START/COMMIT, I was pointing out that they are > superfluous. Leave them in if you wish. > OK; I thought that it was up to the db what to do without them. > The semicolon issue has nothing to do with what mySQL requires, it's a > Livecode requirement - see the dictionary. > I'm not seeing that in the 5.5.1 dictionary for revExecuteSQL (or revDataFromQuery, for that matter). Am I looking in the wrong place? And while I'm asking such things, how can Livecode even *have* a requirement here--shouldn't it be just passing the command to the database? > Finally, if you're using revDataFromQuery to do this, I'm surprised it ever > worked. You're not getting data from a query, you're executing SQL > commands so you need to use revExecuteSQL. > Until today, I had been sending single line commands. I'm trying to cut the lag from a remote db by batching those commands I can (there was really no reason for these to be individual queries in the first place, other than that there will only be one or two of them typically, save when opening a new client "file", in which case there will be dozens"). MySQL's own examples are generally multi-line, with the begin/commit syntax. thanks hawk, confused -- The Hawkins Law Firm Richard E. Hawkins, Esq. (702) 508-8462 hawkinslawf...@gmail.com 3025 S. Maryland Parkway Suite A Las Vegas, NV 89109 _______________________________________________ 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
