I do not think this is a mySQL issue. Livecode currently can only send one statement per query to *any* sql server, at least that is what I have come to understand. But I do not think issuing many queries from livecode is the bottleneck, but rather the ability of the SQL server to respond. When I use memory databases, the response time is nearly nil. A single mySQL query over a LAN is not even noticeable. I make maybe 15 or so queries every time I select a new customer in my Forms Generator app, and it isn't the queries that slow things down, it's the populating of the datagrids and fields that take time.
Now on Windows, I think I do experience some delays with queries, but I think that is just Windows networking security overhead. Bob S > On Mar 10, 2022, at 11:37 , doc hawk via use-livecode > <use-livecode@lists.runrev.com> wrote: > > I dropped mysql after the first run with my software—I don’t know if mysql > could have handled it at the time, but LiveCode could only send a single > command per transaction (afaik, this is still the case). And with several > hundred transactions to start a session . . . (there were also issues about > lack of actual rollback). > > I switched to postgresql, which can trivially connect remotely. > Unfortunately, even though the option is there in the command, and Postgres > supports it, livecode still can’t do an encrypted connection to a postgres > server. > > If I were going to continue, I suppose I would do it through an https > connection to the server, possibly encrypting before sending and letting the > server decrypt. _______________________________________________ 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
