MySQL Bugs: #9494: MyODBC uses default (localhost) setting even when server is set

Bug #9494	MyODBC uses default (localhost) setting even when server is set
Submitted:	30 Mar 2005 16:59	Modified:	9 Apr 2008 8:20
Reporter:	Derek Giromini	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	3.51	OS:	Windows (Windows XP)
Assigned to:		CPU Architecture:	Any

Description:
I am running a program on a FreeBSD box that uses the Easysoft ODBC-ODBC Bridge Client and MyODBC running on a Windows XP box to connecto to a MySQL instance on another FreeBSD box.

For a while, I was able to connect to the MySQL DB successfully, but suddenly I could not. It seemed as though MyODBC was completely disregarding the "server" setting -- instead defaulting to localhost, where I was not running an instance of MySQL. I even added a second DSN for another FreeBSD box running MySQL, and the same behavior occurred.

Reinstalling MyODBC fixed the problem. Logging off did not fix it, but I did not attempt to reboot my Windows XP box.

How to repeat:
I do not know how to repeat the behavior. I had not changed the DSN settings since before I started testing with the Easysoft Bridge.

Suggested fix:
It appears MyODBC simply ignores the "server" setting after a certain period of time, so ensure that that setting isn't somehow lost.

I wasn't able to repeat running Connector/ODBC 3.51.11-1 on XP and the server
on Slackware 10.1.

I haven't been able to repeat it myself yet. I'm taking notes of my steps as I re-test. If it does repeat, it might take a while to do so.

I closed this bug because this won't occur anymore by using MyODBC 3.51.24, Windows XP and FreeBSD 7.0.