16,022,896 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Visual Basic questions
View Javascript questions
View .NET questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by Member 15022970 (Top 3 by date)
Member 15022970
25-Jul-24 9:25am
View
Yes, I agree with you. But the error message also appears when opening the connection to MariaDB from a certain version onwards. So the code at the beginning of the post is correct because it produces the error even without SELECT commands and just through the OPEN command alone.
Member 15022970
25-Jul-24 9:14am
View
That's exactly the problem, that the error occurs when opening the connection and not when issuing a SQL select command. I solved the problem today by installing a NuGet MySqlConnector from Bradley Grainger in Visual Studio. After that, opening the connection and all subsequent commands worked perfectly.
Member 15022970
25-Jul-24 4:53am
View
Your statement is incorrect. This error is thrown when an attempt is made to open the connection. An SQL query is not even involved here. The MySQL connector is probably faulty and is therefore the cause of the problem.