Bug #34477 Need to expose socket (= named pipe name) option in Windows GUI

• Submitted: 12 Feb 2008 2:03
• Modified: 24 May 2010 13:10
• Reporter: Jim Winstead
• Status: Closed
• Category: Connector / ODBC
• Severity: S4 (Feature request)
• Version: 5.1
• OS: Windows
• Assigned to: Lawrenty Novitsky
• CPU Architecture: Any
• Tags: named pipe, setup

[12 Feb 2008 2:03] Jim Winstead

Description:
On Windows, the SOCKET parameter to the DSN is used as the named pipe name to connect to. We forgot to expose this in the Windows setup GUI.

How to repeat:
Set up a DSN on Windows -- notice lack of "named pipe" name option.

Suggested fix:
Make sure it is clear that this is used as the named pipe name, and only used if the 'Force use of named pipes' option is selected (perhaps put that checkbox on the same tab as the field for named pipe name).

[12 Feb 2008 5:50] Tonci Grgin

Hi Jim and thanks for your feature request.

[19 Apr 2010 13:20] Lawrenty Novitsky

the patch

Attachment: bug34477.diff (text/x-diff), 14.16 KiB.

[19 Apr 2010 13:41] Lawrenty Novitsky

Patch has been pushed to the working_tree as rev#892

Patch adds missing field and removes "force using named pipes" checkbox. Added tcp/ip or named pipe radiogroup selector instead. if named pipe selected, default value "MySQL" is set(if user selects back tcp/ip and hasn't changed pipe's name, that default name won't be stored).

[21 May 2010 7:09] Lawrenty Novitsky

pushed to the trunk

[24 May 2010 13:10] Tony Bedford

An entry has been added to the 5.1.7 changelog:

On Windows, the SOCKET parameter to the DSN was used as the named pipe name to connect to. This was not exposed in the Windows setup GUI.