[ODBC-96] Lost connection to MySQL server error when truncate table query is executed Created: 2017-05-15  Updated: 2017-05-21  Resolved: 2017-05-21

Status: Closed
Project: MariaDB Connector/ODBC
Component/s: None
Affects Version/s: 2.0.13
Fix Version/s: 3.0.1, 2.0.15

Type: Bug Priority: Major
Reporter: kriti suwalka Assignee: Lawrin Novitsky
Resolution: Duplicate Votes: 0
Labels: None
Environment:

Windows

Issue Links:
Duplicate
duplicates ODBC-68 [ma-2.0.13][5.6.10]MySQL server has g... Closed

 Description   

We are getting "Lost connection to MySQL server error" if truncate table query is executed with 2.0.13 version. However if we roll back to old version of driver(2.0.11), issue is not seen.
It seems to be regression between 2.011 and 2.0.13 driver version.

 Comments   
Comment by Lawrin Novitsky [ 2017-05-16 ]

Hello,
Similar issue was reported in the comment to ODBC-68.
And in my answer there I said, that it should be separate issue, unless it has the same conditions to be met in order to repeat, as ODBC-68 does. i.e. repeatable only when run in a VM against remote server.
TRUNCATE TABLE works for me on WIndows, so there must be something else.
Or, again, if it's only repeatable on Windows 64-bit and 32-bit, but only run in a VM, then most probably this is a duplicate of ODBC-68
p.s. and btw 2.0.14 is out for some time already

Comment by kriti suwalka [ 2017-05-16 ]

We have never tested ODBC-68 with 2.0.11 so we don't know if that's regression or not. Whereas this issue seems to be regression between 2.0.11 & 2.013 that is why I have raised separate JIRA for it. If you feel both are similar then you can close this JIRA as duplicate. We have tested it with 2.0.14 as well and observed same behavior.

Comment by Lawrin Novitsky [ 2017-05-21 ]

Yeah, I feel that is rather a duplicate of ODBC-68

Generated at Thu Feb 08 03:26:12 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.