Page 3 of 3
Posted: Wed 16 Feb 2005 08:52
by Ikar
CommandTimeout parameter specifies how much time to wait for a result of the query execution and doesn't influence on break of inactive connection. These connections are broken by the server. You can read details about it in MySQL Reference Manual.
Posted: Tue 22 Feb 2005 12:15
by swept
I have the same problem. Before I connected to MySQL with BDEODBC and everything was fine. But when I've converted my project to MyDAC, I get this error very often. In some cases the error doesn't appear every time and there are situations when it appears always. For example, there is a query where about 25-30 tables joined each to other, if the select command doesn't contain "straight_join" then MySQL optimizer thinks slow even if all tables in select are empty. But using MyODBC I didn't get "lost connection". Why?
P.S. Sorry for bad english...
Posted: Tue 22 Feb 2005 13:43
by Ikar
Please describe the situation more detailed:
1. What is the exact MyDAC version that you use?
2. Do you use compression (MyConnection.Options.Compress)?
3. How much time does it take to execute the query?
4. Does it help increasing CommandTimeout?
5. Does it help setting MyConnection.Options.Direct := False?
Posted: Tue 22 Feb 2005 14:06
by Guest
1. 3.50 (latest)
2. No compression
3. 3-10 seconds
4. i'm at short vacation now, will try tomorrow
5. Direct = True
Posted: Tue 22 Feb 2005 15:44
by swept
I'll try to create a sample project with this error at the end of this week.
Posted: Fri 25 Feb 2005 16:14
by Ikar
Please try latest MyDAC build (3.50.0.17)
Posted: Fri 11 Mar 2005 09:26
by Guest
Where I should send a test project?
Posted: Fri 11 Mar 2005 16:04
by Ikar
At first, check that you use MyDAC 3.50.0.17. Then check a value of server variable max_allowed_packet. This value must be rather larger than length of the query and its parameters.
If it doesn't help please send your request to mydac support email address.