MySQL Bugs: #6364: myODBC connector - Can´t save port information on the configuration form.

Bug #6364	myODBC connector - Can´t save port information on the configuration form.
Submitted:	1 Nov 2004 14:51	Modified:	5 Feb 2007 15:04
Reporter:	Ricardo Bueno	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	3.51.10	OS:	Windows (Windows 2000)
Assigned to:	Peter Harvey	CPU Architecture:	Any

Description:
MySQL version: 4.1.7 installing and running fine on localhost, port 3307.

In myODBC 3.51.10 configuration form, Connect Options, Port:
I´ve tried to change the default port number to 3307 (where my server is running). But after typing a new port number (3307) and clicking Ok, the information is not saved on windows register. When you return to the configuration form, the field is empty.

How to repeat:
Run a 4.1.7 mysql server on a diferent port number (as 3307).
Create a new myODBC data source and try to set the diferent port number on Connect Options Tab.
I think you wont be able to!

Suggested fix:
I changed the windows register manually putting a new sequence named 'PORT' with the port number as its value and my client application connected normally.
It seems that this is the problems: the configuration form is not saving the port information on windows register.

Thank you for the bug report.

Seen from multiple customers on our end - even if port is set in registry, using the ODBC data source control panel to edit the DSN, and selecting OK will clear out the port setting. This was known working in 3.51.06.

Hi,

Thank you for the bug report.

The bug can i reproduce, the changes in port didn`t save under the DSN-Name.
I am working on a workround.

Regards
Harun

The same problem occurs on WinXP SP2.  This is especially problematic because of an SP2 bug that does not allow connection to loopback addresses other than 127.0.0.1 without a Microsoft patch (so, you can't just change the address if you are, say, running a local MySQL server on port 3306 and actually want to connect to port 3307 where SSH port forwarding to another server is happening).  However, do note that the configuration screen says that the port setting is "The TCP/IP port to use if server is not localhost."  So, this might be a feature.  That said, for the reasons I have given, it would be much handier if the port was saved even for localhost.

I encountered this bug too and though it would be useful to post the registry key you have to change to fix the port in the configuration.

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\DSNname]
"Driver"="C:\\WINDOWS\\system32\\myodbc3.dll"
"DATABASE"="database name"
"PASSWORD"="password "
"SERVER"="server name"
"USER"="username"
"PORT"="3369" <--- change to whatever port you´re going to use.

Hi,

Bug still present in 3.51.12 !
Is it going to be fixed ?

Jerome

Seems to be working in 3.51.12. Which type of DSN fails? I checked user and system ones.