Uploaded image for project: 'MariaDB Connector/ODBC'
  1. MariaDB Connector/ODBC
  2. ODBC-385

Wrong documentation for named pipes

    XMLWordPrintable

Details

    Description

      To use the ODBC driver with named pipes on Windows I looked into the documentation and didn't get it to work.
      https://mariadb.com/kb/en/about-mariadb-connector-odbc/

      There are three sentences about named pipes:

      Parameter Description
      NAMEDPIPE boolean value(non-zero value is treated as TRUE) determining whether Server is treated as a named pipe name, or as domain name/IP address. Using of NAMEDPIPE is equivalent of setting/resetting of 13th bit(counting from 0, 8192) OPTIONS bit. It has effect on Windows only.
      SOCKET full socket name, if it is specified, server name is disregarded. It has effect on Linux only.
      SERVER name or IP of the MariaDB database server. Aliases: SERVERNAME

      So my connection string should be (ADO):

      Driver={MariaDB ODBC 3.1 Driver};NAMEDPIPE=1;SERVER=MyPipeName;USER=user;PASSWORD=password
      

      But this doesn't work. Instead you always get this error:

      [ma-3.1.17]Can't open named pipe to host: MyPipeName  pipe: MySQL (53)
      

      The working connection string uses SOCKET instead of SERVER on Windows:

      Driver={MariaDB ODBC 3.1 Driver};NAMEDPIPE=1;SOCKET=MyPipeName;USER=user;PASSWORD=password
      

      This works fine. But the documentation explicitely says that "Server is treated as a named pipe name". Also the documentation for "Socket" says "It has effect on Linux only."
      Both sentences are wrong.

      It would be nice if you could fix the documentation.

      Attachments

        Issue Links

          Activity

            People

              Lawrin Lawrin Novitsky
              DaGaMx David Gausmann
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.