Just updated from 4711 to 4714 and can't connect to MySQL anymore, HeidiSQL freeze on connect, back to 4711 is OK (haven't tested 4712 or 4713).
Win7 64Bits
8.3.4714 freeze on MySQL connect
r4714 adds a message box to the table editor in a specific case - that can't be the cause here. r4712 and r4713 modified language stuff in the installer - which also sounds totally irrelevant here. Can you reproduce that freeze multiple times or was it a one-time glitch, probably from the update check or so which does something over the internet?
OK found the problem it come from libmysql.dll version.
I do have 64Bits 5.5.29 version date 05/03/2013 in heidisql directory, it worked until today among all HeidiSQL portable versions auto-updates.
Your new 4714 is not compatible with this version anymore.
I think you changed also some libmysql headers/struc/api calls in this version.
Used the libmysql64.dll from your SVN, now it's OK.
May be you should add some version compatibility detection of libmysql ? or include libmysql download during HeidiSQL update if you have newer version ?
I do have 64Bits 5.5.29 version date 05/03/2013 in heidisql directory, it worked until today among all HeidiSQL portable versions auto-updates.
Your new 4714 is not compatible with this version anymore.
I think you changed also some libmysql headers/struc/api calls in this version.
Used the libmysql64.dll from your SVN, now it's OK.
May be you should add some version compatibility detection of libmysql ? or include libmysql download during HeidiSQL update if you have newer version ?
That sounds as if you mixed up 32 bit and 64 bit files manually. As said, there were only irrelevant changes in recent commits. The auto updater downloads the 32 bit update if you're running the 32bit version, same for 64bit. There are no libmysql calls changes in recent commits.
I have not mixed 32 and 64, I use 64bits heidisql and 64bits libmysql.dll
the fact is that until 4713 it worked fine, now with 4714 it don't work, I used same libmysql.dll version for months so there must be something else in your code or libmysql includes that changed between 4713 and 4714, using "your" libmysql.dll solved the problem that's ok but something else changed between 4713 and 4714.
the fact is that until 4713 it worked fine, now with 4714 it don't work, I used same libmysql.dll version for months so there must be something else in your code or libmysql includes that changed between 4713 and 4714, using "your" libmysql.dll solved the problem that's ok but something else changed between 4713 and 4714.
You could have just believe me, I am not telling rubbish. Or look at the changelog, as said: http://code.google.com/p/heidisql/source/detail?r=4714
Please login to leave a reply, or register at first.