error ##4000, Unknow Theread ID ...HELP, some Exceptions

[eduardosic]

##4000 ID de Thread 744 unknow
##4000 ID de Thread 781 unknow

im my aplications, using myDAC 4.30 Delphi 7 and mySQL 4.1.17
the exception is raised some times,

what is this?

[eduardosic]

##4000 ID de Thread 744 unknow
##4000 ID de Thread 781 unknow

im my aplications, using myDAC 4.30 Delphi 7 and mySQL 4.1.17
the exception is raised some times,

what is this?

The problem with "Unknow Theread Id continue" inversion 4.30, how Core lab are
answer the question?

[Ikar]

Thank you for information.
We reproduced your problem and fixed it. This fix will be included in the next MyDAC build.

[Benjamin]

Hi,

I have this same problem with MyDAC version 4.30 for Delphi 2005 when ater some time of inactivity. Do you know when the version with this fix will be available?

Thanks a lot in advance...

[eduardosic]

Thank you for information.
We reproduced your problem and fixed it. This fix will be included in the next MyDAC build.

Thank's Ikar, I go to wait new build of version 4.30, how much this new build will be available?

[Ikar]

Usually we publish new builds once in a month. But if many users are confronted with critical problem we can shorten this time.

As FetchAll=False mode has many limitations (please see MyDAC help for details) this mode is not much popular.

If you have MyDAC Pro version we can send you patch by email.

[eduardosic]

Usually we publish new builds once in a month. But if many users are confronted with critical problem we can shorten this time.

As FetchAll=False mode has many limitations (please see MyDAC help for details) this mode is not much popular.

If you have MyDAC Pro version we can send you patch by email.

I have the version "MyDAC Standard single license ", I go upgrade to MyDAC Professional when have more money.

I only use the FetchAll=False way, because thus the searches of my applicatory one are much more fast leaving the satisfied customer.

please publishes a build correcting this problem of Unknow thereadId,
my custumers are insane with this error all hour appearing.

thanks.

[Ikar]

As temporary solution, you can call DataSet.Last before closing query. It allows to avoid wrong behavior on closing datasets.

[eduardosic]

As temporary solution, you can call DataSet.Last before closing query. It allows to avoid wrong behavior on closing datasets.

Ikar, very thanks for this solution, but calling DataSet.Last all data are retrivied for the client, the process is slow with big queries.

but the problem Unknow TheredID do not occurs with
myDAC 4.30 and mySQL 5.0.

i upgrade the mySQL server to version 5.0 and the problem is solve.

thanks for help.
myDAC with FetchAll =False is very very Fast.

[Ikar]

> calling DataSet.Last all data are changed for the client, the
> process is slow with big queries.

This is old MyDAC 4.0 behavior caused by MySQL server protocol limitations.

[GEswin]

Do you query full tables or use myTables to perform searches ?? I think you could speed up a lot if you just query the table for that what you're searching for.

[eduardosic]

Do you query full tables or use myTables to perform searches ?? I think you could speed up a lot if you just query the table for that what you're searching for.

in my Application i use TmyQuery with property fetcheAll = False,
in SQL parameter the script:
select name, Cod, end From Clients where name like 'eduardo%'

this query with fetchall = false and a table with 200.000 row is opened with 00 seconds and 016 milisecondes... but 25 rows is imediatle retrivied from database, on scroll others rows is retrivied. call DataSet.Last; the aplication call all rows from the table... its very slow..

if the property fetcheAll = true the query is opened in 07 secondes and 256 milisecondes... very slow. what all table is retrivied to client.

i go make a simple program to ilustrate the situation. and send to [email protected].

thanks... the important are the Unknow theread Id not ocurrs with myDAC 4.30 and mySQL 5.0.

[Ikar]

As a temporary solution to avoid Unknown ID Thread error we suggest to call Last method before closing Dataset. When you call the Last method, you force to get all the data from the server as it was implicitly implemented in version 4.00. Therefore there aren't any significant differences in performance between versions 4.00 and 4.30 with using Last method.

[eduardosic]

As a temporary solution to avoid Unknown ID Thread error we suggest to call Last method before closing Dataset. When you call the Last method, you force to get all the data from the server as it was implicitly implemented in version 4.00. Therefore there aren't any significant differences in performance between versions 4.00 and 4.30 with using Last method.

ok, its sugetion is very good, but in mydac 4.30 version 4.00 and the DataSet.last delays to be executed in a table with 200.000 rows, as the problem is not present between mydac 4,30 and mySQL 5,0, I update the version of mySQL in my customers. I go to wait new build of myDac 4.30.