Bug #109862 | MySQL for Visual Studio 1.2.10 | ||
---|---|---|---|
Submitted: | 31 Jan 2023 13:36 | Modified: | 7 Feb 2023 11:31 |
Reporter: | Tim Reed | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | Connector / NET | Severity: | S1 (Critical) |
Version: | 8.0.32 | OS: | Windows (11 pro) |
Assigned to: | CPU Architecture: | x86 | |
Tags: | MySQL for Visual Studio 1.2.10, mysql.data.dll 8.0.24, utf8mb3 |
[31 Jan 2023 13:36]
Tim Reed
[1 Feb 2023 12:30]
MySQL Verification Team
Hello Tim Reed, Thank you for the bug report. I tried to reproduce your issue on windows 10 with Connector/NET 8.0.32 and followed exact steps but I am not seeing any issues at my end. Related to Bug #107259. Regards, Ashwini Patil
[1 Feb 2023 13:17]
Tim Reed
On the new connection on server explorer, try to expand the list of tables.
[2 Feb 2023 14:02]
Tim Reed
You refer to Bug #107259, I think there is some overlap in that discussion between the using .NET Connector in code and MYSQL for Visual Studio, However there is mention the that thread of the same issue as me ([8 Nov 2022 7:20] David Shoemaker, [6 Dec 2022 17:48] Franz Roscher, for example) MYSQL for Visual Studio is an extension for Visual Studio that enables the Server Explorer to connect to MYSQL. This Extension has been built with mysql.data.dll version 8.0.24 which, when used with MYSQL server 8.0.32 returns the error about utf8mb3 as 8.0.24 does not have the overloaded "GetCharacterSet" method. I have installed as above on other machines to test and all return the same result so i cannot understand why you are not getting the same issue. To be clear the connection can be made (if you manually input the database name) but if you try to drop list the tables you get the error.
[7 Feb 2023 11:31]
Tim Reed
Hi, any chance of an update on this? I pretty sure it can be repeated, i have done so on 4 different installs/PCs. I can post proof and pictures if you want. Please re-investigate this issue i am sure MYSQL for Visual studio 1 .2.10 will not work with the latest MYSQL server (8.0.32)
[16 May 2023 13:57]
JL B. Schneider-Electric
I have reproduced this bug several times on VS2019 and VS2017 and have not yet found a solution. ;-(