Bug #8161 port setting neither retained nor honored
Submitted: 27 Jan 2005 13:04 Modified: 27 Jan 2005 13:17
Reporter: Kyle Morris Email Updates:
Status: Duplicate Impact on me:
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:3.51.10 OS:Microsoft Windows (Windows)
Assigned to: CPU Architecture:Any

[27 Jan 2005 13:04] Kyle Morris
The port setting (for using a port other than 3306) does not appear to be retained when you save settings.  If you manually edit the registry to add the port setting it will appear in the port edit box for the data source but it doesn't appear to be used when you try to connect (still uses port 3306).

Falling back to 3.51.09 resolves this issue.

How to repeat:
1) Create a new ODBC data source and enter a value for the port other than 3306.  Save the data source.  When you edit the data source again the 'Port' value is blank.
2) Manually add a registry key like 


to specify the port for data source 'LocalDataSource' and then edit the data source in the  ODBC Data Source Administrator.  The value 53306 will show up in the edit box but it does not appear to be used by the driver to connect.
[27 Jan 2005 13:17] MySQL Verification Team
Duplicate for #6364