Brian I have been unable to get the new wdmysql.exe to run correctly as far as I can see. I updated to build 75 (used full then latest zip) and started up OK. The wdmysql.exe starts but the icon in the system tray will not respond at all and I cann view what the program is doing. For now I have put back the old mysql.exe from build 57 which I was running and all is back to normal.
Now a very important question here, will the new version of wdmysql.exe run on a Windows 2000 system? I still run W2K and had no intention of buying a new Windows license just to run WD as my other systems run Linux now.
If anyone else uses MySQL and W2K can they confirm whether or not they can get the new wdmysql.exe to run? Also can someone please confirm if they can get a new wdmysql.exe window to open showing its activity?
Stuart
Edit: I just looked at my MySQL table for the time I was trying to get the new code working and nothing was added for some 10-15 minutes while I was doing his, all back to normal when I started up the old one.
Brian I tried this version this morning and it starts up and says it has connected to the correct table name OK but then does not respond at all and has a busy mouse pointer. If I click the X to close I get the Not Responding pop-up and have to click End Now to close it. There are no messages in the error log part of the window.
Brian I now have the query log activated in MySQL and I think I have found the problem.
In the old wdmysql.exe you issue a select * from wx_data1 limit 10 but in the new version you issue the select without the limit 10 parameter and this tries to read in the whole database which in my case is 1.6gb of data and takes a long time for the query to complete, hence the hang. I suggest you modify the initial select to be the same as the old version and just read in the first 10 entries.
Well that’s sorted the startup problem nicely, however when it tries to write the first set of data it gives an error message saying that the data is too long for station_id. Now my station_id field is set as VARCHAR(10) and the old version writes Broadstair into this field with no problem at all, but the new version does not, true my station ID is more than 10 characters but the old version truncates it to 10 chars OK.
Thanks again Brian, I’ll give it a go. Your quick response is very much appreciated. I understand about the re-write, I suspect there are not a large number of MySQL users in the WD world so I guess we might find the odd bug as we start using it on existing setups, after all you cannot test everything.
Stuart
Edit: It is running now and updating fine. I’ll keep an eye on it for the next couple of hours but I see no reason for there to be any problems. Thanks again…
Hi Stuart,
I’m still struckling in getting wdmysql up and running without any luck. I’m using version 10 of wdmysql.exe. I have browsed the entire forum and I’m getting somewhat confused. I have seen in earlier issues, reference to custommysqlout.txt and custommysqlin.txt. Since you appear to have the latest version working, could you confirm whether these files should still be present with the latest wdmysql.exe? Are there any other external files which should have been generated once you “create table”? I’m completely in the blind as to what sql statement WD generates once the table has been created. Hope you can throw some light on this issue to facilitate further fault finding.
Rgds
Dick