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

Char fields type returned by SQLColums in case of unicode connection

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 3.0.6, 2.0.18
    • 3.1.0
    • General
    • None

    Description

      For character fields, not matter if application uses Unicode or ANSI part of the API, SQLColumns will return SQL_(LONG)(VAR)char sql type, and not SQL_W(LONG)(VAR)CHAR. The same is true for SQLProcedureColumns

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. ODBC-187 Default string data types used for Unicode connection

          • Major - Major loss of function.
          • Open

          Activity

            Ascending order - Click to sort in descending order
            Lawrin Lawrin Novitsky added a comment -

            odbc-3.0 commit 768b94f

            Lawrin Lawrin Novitsky added a comment - odbc-3.0 commit 768b94f
            Lawrin Lawrin Novitsky added a comment -

            This fix requires other changes, and probably it is better to do that (or give up on this idea) in new developed version.
            The commit moved into develop branch, in 3.0 I'll revert the changes in some way

            Lawrin Lawrin Novitsky added a comment - This fix requires other changes, and probably it is better to do that (or give up on this idea) in new developed version. The commit moved into develop branch, in 3.0 I'll revert the changes in some way

            People

              Lawrin Lawrin Novitsky
              Lawrin Lawrin Novitsky
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.