Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-13927

CONNECT engine table_type=JDBC escaping backslash character on UPDATE

Details

    Description

      CONNECT with JDBC is trying to escape the backslash character when doing an UPDATE on a connect table.

      So when I update a row and set the value to
      here is my \ backslash character

      it returns from a query as
      here is my
      baclslash character

      It appears CONNECT in 10.1.27 for UPDATE statements is trying to escape characters in strings that it doesn't need to escape; previous bug reports about double quote char and single quote char. It seems CONNECT should not escape ANY characters in a string except the single quote char itself, which is escaped per the SQL standard by doubling up the single quote not using a backslash.

      Attachments

        Issue Links

          Activity

            rdyas Robert Dyas added a comment -

            Yet more issues... it appears that WHERE clause strings are also escaped incorrectly just like UPDATE strings. Same issues with
            and \" and \' rather than '' (that is two single quotes) being used.

            rdyas Robert Dyas added a comment - Yet more issues... it appears that WHERE clause strings are also escaped incorrectly just like UPDATE strings. Same issues with and \" and \' rather than '' (that is two single quotes) being used.

            Duplicated. Was fixed as MDEV-13621

            bertrandop Olivier Bertrand added a comment - Duplicated. Was fixed as MDEV-13621
            rdyas Robert Dyas added a comment -

            Hi Olivier... does that mean that it was not fixed in 10.1.27 due to a build problem again?
            Is that also why the pooling does not work in 10.1.27? (pooling worked great in 10.1.26... in 10.1.27 it seems the connections are never returned to the pool, so the pool runs out after 8 or 10 connections and just hangs... would be great to put a 30 second timeout on that...).

            rdyas Robert Dyas added a comment - Hi Olivier... does that mean that it was not fixed in 10.1.27 due to a build problem again? Is that also why the pooling does not work in 10.1.27? (pooling worked great in 10.1.26... in 10.1.27 it seems the connections are never returned to the pool, so the pool runs out after 8 or 10 connections and just hangs... would be great to put a 30 second timeout on that...).

            Perhaps; however it is fixed in 10.1.28.
            Pooling is a regression bug that is not fixed yet.

            bertrandop Olivier Bertrand added a comment - Perhaps; however it is fixed in 10.1.28. Pooling is a regression bug that is not fixed yet.
            rdyas Robert Dyas added a comment -

            Olivier... The backslash issue was resolved in another ticket as related to the JDBC driver escaping method (for which there is a work around... not yet tested, so you can close this ticket).

            Was the pooling regression fixed in 10.1.28?

            rdyas Robert Dyas added a comment - Olivier... The backslash issue was resolved in another ticket as related to the JDBC driver escaping method (for which there is a work around... not yet tested, so you can close this ticket). Was the pooling regression fixed in 10.1.28?
            bertrandop Olivier Bertrand added a comment - - edited

            The pooling regression bug was what you described in one of your comment (connection not released from the pool when closing). It will be fixed in 10.1.29.
            BTW with MariaDB 10.2.10 you can begin test the MONGO table type.

            bertrandop Olivier Bertrand added a comment - - edited The pooling regression bug was what you described in one of your comment (connection not released from the pool when closing). It will be fixed in 10.1.29. BTW with MariaDB 10.2.10 you can begin test the MONGO table type.

            People

              bertrandop Olivier Bertrand
              rdyas Robert Dyas
              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.