LiveCode Forums.

Anyone got any Ideas to try on this one? I time out at 21 seconds every time.

I have these set on the server.

set global max_allowed_packet=1048576000;
set global wait_timeout=3600;
set global interactive_timeout=3600;

The same Query from mySQL Workbench does not time out, it finishes at 23.73 seconds. so the server isn't set to time out at 21 seconds?

anything else to try?

Thank you for trying, either it didn't work or I didn't put it in the right spot.

Dictionary tells us the default is 10 seconds, not close to 21, however I tried putting it in my script on my button just before the
maybe that's the wrong place and that's my problem but it didn't help, also tried 60 seconds, still same result at 21 seconds

Did you try with revQueryDatabase?
For example:

I did try that to put the data into a datagrid, unless that's not quite the same thing?

Also have done some more testing. After I get the error in livecode telling me I lost my connection, looking at the server my connection on that side is still there so the server it seems to me is not closing the connection and it must be livecode?

if I run my query in a loop on a few different jobs 3 small job for instance and then the big job that is taking 21+ second, the 3 jobs give results and the last one fails.
if I turn it around and run the long one first then all 4 fail.
the error given for the next 3 after the long one fails is revdberr,MySQL server has gone away.

Well I'm trying a new approach on this because I cant seen to figure out the 21 second livecode just decides to close the connection.

I've added "INTO OUTFILE 'C://Temp//@JobNum.csv';" and changed it up to revExecuteSQL instead, however this also waits for confirmation from the server, so again its failing.

Is there a way to just send 3 or 4 or 10 query's to the server and not care about a return at all, I know it worked or failed by looking for the data in the export file.

DavJans wrote:Well I'm trying a new approach on this because I cant seen to figure out the 21 second livecode just decides to close the connection.

I've added "INTO OUTFILE 'C://Temp//@JobNum.csv';" and changed it up to revExecuteSQL instead, however this also waits for confirmation from the server, so again its failing.

Is there a way to just send 3 or 4 or 10 query's to the server and not care about a return at all, I know it worked or failed by looking for the data in the export file.

I would use this SQL syntax:

Hi,

just hope your tables are not MyISAM - no support for transactions ...

The major deficiency of MyISAM is the absence of transactions support. Also, foreign keys are not supported.

Have fun!

InnoDB. So that's not a problem.

I have gotten a result that will work for us, I didn't figure out the problem yet though. I ended up connecting to the db inside the repeat loop instead of before. This way if any query is long enough that I lose connection it doesn't matter. It wont help me pull data into my livecode app, but MySQL will at least dump the data to a file that we can use in excel. Getting data into excel is the end goal anyway.

Create a stored routine in the database and run that instead. All the processing will happend in the DB instead of Livecode

I have similar problems when I try to run queries from MYSQL through livecode using "revExecuteSQL" and "revDataFromQuery". I thought about running the a stored routine as mentioned by zaxos before, but I wasn't sure how to get the information back to livecode once it has run on the database side. I didn't see much on how it worked on my initial search, but my thought process was that livecode sends the command to execute the routine and then it doesn't matter if the connection is lost, the database runs the routine on its end, but I need to pull the information back to print to the programs screen. I'm a bit new to the stored routine/procedure process, so please correct me if I'm wrong.

Hi,

I have a rather long winded query on a MySQL database that runs each night and stores its data in a temp table, for faster access. The way I do it could be what you need.

The actions starts from Livecode. I send these Statements to the db: (if this fails, the table is in use! Try later ...)
and then where "ax_p_MakeSalesHist" is a stored procedure.

The procedure "ax_p_MakeSalesHist" on the server is like the usual: The next day, I just access myTable.

Times ago I had a query that had to yield "immediate" results, but still took about 2 minutes (on the server). I just added a UID row to the CREATE TABLE statement (using an argument), and polled every 5 seconds with a: until the result wasn't empty anymore, and showed a spinning beach ball meanwhile ;-)

Have fun!