MySQL Bugs: #65341: OpenOffice crashes using ODBC Connector 5.1.11, but not with 5.1.8

Bug #65341	OpenOffice crashes using ODBC Connector 5.1.11, but not with 5.1.8
Submitted:	16 May 2012 19:13	Modified:	18 May 2012 4:27
Reporter:	Dustin Lindley	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	Connector / ODBC	Severity:	S3 (Non-critical)
Version:	5.1.11	OS:	Windows (XP sp3)
Assigned to:	Bogdan Degtyariov	CPU Architecture:	Any

Description:
We have a MySQL database and were attempting to install our typical frontend (OpenOffice base with MySQL ODBC Connector) on a new machine.  Everything worked fine, we were able to see the tables on the chosen database, but when attempting to view the data in the tables, OpenOffice crashes.  This was using the MySQL ODBC Connector version 5.1.11, and the problem was solved by using version 5.1.8.  I will post a bug report with the OpenOffice people as well, as I was able to use HeidiSQL and a proprietary python program with the 5.1.11.

How to repeat:
Use MySql ODBC connector 5.1.11 and OpenOffice base to connect to a MySql database.  Try to view the data in a table.

I verified the behavior reported with 5.1.11 and 5.1.8 however looks for me duplicate with http://bugs.mysql.com/bug.php?id=65200 please check. Thanks.

Yes, it is the same as http://bugs.mysql.com/bug.php?id=65200.  I am able to display a table with name "allyLongTableName" (17 chars), but it crashes on "eallyLongTableName" (18 chars).  These tables were made in OpenOffice, and it crashed as I made "eallyLongTableName".  However, the original table that I was trying to access only has 13 chars in it's name, so I'm not sure what to make of that.

Dustin, we will re-check bug #65200 and mark this report as duplicate if they are about the same problem.

Cool!  Thanks for the speedy response, and I hope a solution can be found.  For the time being, I'm using 5.1.8.

Cool!  Thanks for the speedy response, and I hope a solution can be found.  For the time being, I'm using 5.1.8.

Dustin,

Please check the bug 65200. I found the reason for the crash and made a patch 
for it. It will be pushed to the source repository after developers review and
approve the patch.

The crash culprit and its fix are explained in the above mentioned bug report.
Marking this report as duplicate because bug 65200 was first in the list.
Thanks.

Looks to be the problem I'm having, although I'm pretty far from an expert on the fine details of how all this stuff works.  Is the fix something that'll show up in later releases, or will this be included in a later build of this release?

In any case, thanks much for the work!  This was my first bug report that actually got solved!