Ditto what Mike said:
" On mysql.. can't you prebuild your multi-command transaction in a variable"
I periodically do this kind of thing. assuming the transaction is exactly the
same… one way is to build a single SQL query from your data.
Assume you need something like this, getting and SQL
The shell function can do this. I don't know if there could be a limit
to the length of the shell command though.
put shortfilepath("C:\Program Files\MySQL\MySQL Server
5.6\bin\mysql.exe") into myFilePath
-- the following line contains 2 insert commands
On Fri, Dec 29, 2017 at 5:05 PM, Mike Bonner via use-livecode
> On mysql.. can't you prebuild your multi-command transaction in a variable
> (with a beginning and ending to the transaction) and then use revexecutesql
> with a single call for the one big
Thanks to all.
As i wrote already, i am updating now one row after the other using a repeat
loop. MySQL is running on the same server as Livecode Server is. So it takes
only one seconds or so to update all 2276 records.
> Am 30.12.2017 um 02:05 schrieb Mike Bonner via use-livecode
On mysql.. can't you prebuild your multi-command transaction in a variable
(with a beginning and ending to the transaction) and then use revexecutesql
with a single call for the one big transaction?
On Fri, Dec 29, 2017 at 5:59 PM, Dr. Hawkins via use-livecode <
On Fri, Dec 29, 2017 at 12:53 PM, Matthias Rebbe via use-livecode
> Executing the 2000 update commands in one take using revexecuteSQL
> or should i execute one update command after each other within a repeat loop?
Unless something has changed, you can't
Thanks Rick for sharing your thoughts.
I am just updating only one field in each record and i am not locking the
The complete update when doing one after one in a repeat loop does not take
more than 1 second.
So i think i will go that way.
Are there going to be users on your system at the time of the update?
Are you locking the record or records before your update, and then
You should do a test with the repeat loop to see how long the process takes.
If it is depriving your users of the database for too