Uploaded image for project: 'MariaDB Connector/C++'
  1. MariaDB Connector/C++
  2. CONCPP-143

Possible issues in getImportedKeys, getExportedKeys and getCrossReference with 12.1 server

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 1.0.5, 1.1.6
    • 1.1.7, 1.0.6
    • General
    • None

    Description

      MariaDB 12.1 introduced a change to constraint naming behavior through MDEV-28933. This modification affects metadata queries that rely on joins between INFORMATION_SCHEMA.KEY_COLUMN_USAGE and INFORMATION_SCHEMA.REFERENTIAL_CONSTRAINTS tables.

      Previously, joins could be performed using only the three columns: CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, and CONSTRAINT_NAME. However, due to this change, queries must now include TABLE_NAME as an additional join condition to ensure accurate results.
      This breaking change specifically impacts the following metadata operations:

      getExportedKeys()
      getImportedKeys()
      getCrossReference()

      Attachments

        Issue Links

          relates to

          New Feature - A new feature of the product, which has yet to be developed. MDEV-28933 Per-table unique FOREIGN KEY constraint names

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. CONJ-1279 metadata table name addition for 12.1

          • Major - Major loss of function.
          • Closed

          Activity

            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.