Bug #105259 | Not able to connect to MySQL hosted over AZURE or AWS using isql command. | ||
---|---|---|---|
Submitted: | 19 Oct 2021 7:12 | Modified: | 17 May 2022 21:17 |
Reporter: | Akash More | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / C++ | Severity: | S3 (Non-critical) |
Version: | 8.0.26 | OS: | Linux (Linux PSLinuxmysql03 4.18.0-193.47.1.el8_2.x86_64) |
Assigned to: | CPU Architecture: | x86 (x86_64 x86_64 x86_64 GNU/Linux) | |
Tags: | AWS Aurora, Azure, isql, socket |
[19 Oct 2021 7:12]
Akash More
[25 Oct 2021 12:12]
MySQL Verification Team
Hello Akash, Thank you for the bug report. Specifying SERVER that is not localhost and SOCKET at the same time is a wrong configuration. The ODBC driver prefers SOCKET file connection if the corresponding option is specified. After discussing internally with the developer we concluded that this looks like more of a documentation improvement request. To avoid ambiguities in the future it should be documented. Hence verifying as a doc bug. Thank you! Regards, Ashwini Patil
[17 May 2022 21:17]
Philip Olson
Posted by developer: Sorry for the late response, this bug was lost over time... partially due to it being a C/ODBC bug listed against C/C++. The socket documentation was clarified; only define socket if server is localhost.