Bug #31165 Renaming ODBC name creates new entry
Submitted: 24 Sep 2007 6:21 Modified: 10 Jan 2008 8:46
Reporter: Jared S (Silver Quality Contributor) Email Updates:
Status: Closed Impact on me:
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:5.1 OS:Microsoft Windows (Vista)
Assigned to: Jess Balint CPU Architecture:Any
Tags: ODBC, qc, renaming

[24 Sep 2007 6:21] Jared S

Renaming an ODBC name (Data Source Name) creates a new registry entry, but fails to delete old, thus leaving 2 entries in Administrative Tools\Data Sources (ODBC).

How to repeat:
1. Create new System DSN
2. Rename new system DSN
[24 Sep 2007 6:22] Jared S
ODBC rename bug

Attachment: bug.jpg (image/pjpeg, text), 38.19 KiB.

[24 Sep 2007 11:12] MySQL Verification Team
Thank you for the bug report.
[3 Jan 2008 22:23] Jess Balint

Attachment: bug31165.diff (application/octet-stream, text), 961 bytes.

[3 Jan 2008 22:26] Jess Balint
Will not be fixed in Connector/ODBC 3.51
[4 Jan 2008 18:37] Jim Winstead
The fix for this has been committed, and will be in 3.51.23.
[4 Jan 2008 19:11] Jess Balint
The fix for the native Windows GUI has been committed, and will be in 5.1.2.
[10 Jan 2008 8:46] MC Brown
A note has been added to the 3.51.23 and 5.1.2 changelogs: 

Renaming an existing DSN entry would create a new entry with the
new name without deleting the old entry.