Uploaded image for project: 'MariaDB Connector/J'
  1. MariaDB Connector/J
  2. CONJ-1109

Regression in clearBatch() for parameterized statements

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 3.0.3, 3.2.0
    • 3.3.1
    • batch
    • None

    Description

      3.2.0 MariaDB Connector/J (the same noticed with 3.0.3) shows regression in using clearBatch() for parameterized statements. This worked fine in 2.7.2. I'm attaching Java app to reproduce and results using both versions.

      //

      {4, XB4} missing - correct
      Driver version: 2.7
      Driver name: MariaDB Connector/J
      Driver version name: 2.7.2
      Database product name: MariaDB
      Database product version name: 10.5.5-MariaDB
      Database product version number: 10.5
      JDBC version number: 4.2

      Table created
      Commit the batch
      Roll back
      Commit the batch
      ===========
      1, XB1
      2, XB2
      3, XB3
      5, XB5
      ===========
      Table dropped

      // {4, XB4}

      present - incorrect
      Driver version: 3.2
      Driver name: MariaDB Connector/J
      Driver version name: 3.2.0
      Database product name: MariaDB
      Database product version name: 10.5.5-MariaDB
      Database product version number: 10.5
      JDBC version number: 4.2

      Table created
      Commit the batch
      Roll back
      Commit the batch
      ===========
      1, XB1
      2, XB2
      3, XB3
      4, XB4
      5, XB5
      ===========
      Table dropped

      Attachments

        Activity

          People

            diego dupin Diego Dupin
            michalwojtowicz Michał Wójtowicz
            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.