Result +1 >= bug still here
Result +1 >= bug still here
I downloaded the 5.0.20 version which corrects the return length bug, but still MYDac says Result + 1 >= MaxDestBytes.
Whats wrong? Maybe its not MYSQL bug after all? Maybe you have to fix sth?
Whats wrong? Maybe its not MYSQL bug after all? Maybe you have to fix sth?
> I downloaded the 5.0.20 version
Please let us know where did you download MySQL Server 5.0.20. We can't find this version on the http://dev.mysql.com/downloads/mysql/5.0.html.
> Maybe you have to fix sth?
We will try to avoid this bug for all MySQL server versions in the nearest build.
Please let us know where did you download MySQL Server 5.0.20. We can't find this version on the http://dev.mysql.com/downloads/mysql/5.0.html.
> Maybe you have to fix sth?
We will try to avoid this bug for all MySQL server versions in the nearest build.
Pick a mirror here:
http://dev.mysql.com/get/Downloads/MySQ ... /from/pick
its the full version, ZIP, of the 37mb
Please fix it asap. I just cant release my software without this fix. Other softwares such as Navicat, MySQLFront, PhpAdmin works well with this function. Only MyDAC fails.
http://dev.mysql.com/get/Downloads/MySQ ... /from/pick
its the full version, ZIP, of the 37mb
Please fix it asap. I just cant release my software without this fix. Other softwares such as Navicat, MySQLFront, PhpAdmin works well with this function. Only MyDAC fails.
What does it means? This is the 5.0.20 and this is the changelog:
http://dev.mysql.com/doc/refman/5.0/en/news-5-0-20.html
and the bug fixed:
The FORMAT() function returned an incorrect result when the client's character_set_connection value was utf8. (Bug #16678)
The 5.0.21 is the under-release version.
If you are registered member of MySQL you will would have seen the announcement in the mailing list.
In anycase there are ways to fix the bug even in the old 5.0.19 as other software(s) bypass this error.
http://dev.mysql.com/doc/refman/5.0/en/news-5-0-20.html
and the bug fixed:
The FORMAT() function returned an incorrect result when the client's character_set_connection value was utf8. (Bug #16678)
The 5.0.21 is the under-release version.
If you are registered member of MySQL you will would have seen the announcement in the mailing list.
In anycase there are ways to fix the bug even in the old 5.0.19 as other software(s) bypass this error.
We have tested MySQL server 5.0.20. The error you have reported is present in this release of MySQL server too. Please pay attention on "Changes in release 5.0.20":
We have found the way to avoid this server bug. This fix will be included in the next MyDAC build.
As we can see after our test, in the new server release FORMAT() function works fine but not DATE_FORMAT().The FORMAT() function returned an incorrect result when the client's character_set_connection value was utf8. (Bug #16678)
We have found the way to avoid this server bug. This fix will be included in the next MyDAC build.
The new build of MyDAC will be available in the nearest few days. Please watch for announcements at the forum http://crlab.com/forums/viewforum.php?f=7.