Uploaded image for project: 'MariaDB Connector/C'
  1. MariaDB Connector/C
  2. CONC-240

Bulk Insert (Row-wise Binding) inserts wrong data in db when array_size= 1

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 3.0.1
    • Fix Version/s: 3.0.2
    • Component/s: None
    • Labels:
      None
    • Environment:
      Fedora linux
      mariadb-connector-c-3.0.1-beta
      Server version: 10.2.4-MariaDB MariaDB Server

      Description

      Using the example in:
      https://mariadb.com/kb/en/mariadb/bulk-insert-row-wise-binding/

      If I change array_size from 3 to 1 I get the following stored in the db:
      select * from example_db.bulk_example2;

      +----+----------+---------+
      | id | forename | surname |
      +----+----------+---------+
      |  1 |          | Monty   |
      +----+----------+---------+

      I would have expected:

      +----+----------+----------+
      | id | forename | surname  |
      +----+----------+----------+
      |  1 | Monty    | Widenius |
      +----+----------+---------+

      When array_size=3 I get, as expected, the following stored in the db:

      +----+----------+----------+
      | id | forename | surname  |
      +----+----------+----------+
      |  1 | Monty    | Widenius |
      |  2 | David    | Axmark   |
      |  3 | unknown  | N.N.     |
      +----+----------+----------+

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              georg Georg Richter
              Reporter:
              ean Egon Andersen
              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.