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

Using /*client prepare*/ prefix to force client side prepared statement

Details

    • Task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 3.2.0
    • Other
    • None

    Description

      When option `useServerPrepStmts` is set, every prepared statement will use server side prepared statement. There is some specific command where user might prefer to use server side prepared statement.

      Goal here is that commands prefixed with

      /*client prepare*/
      

      will use client side prepared statement when `useServerPrepStmts` is enable.

      Attachments

        Activity

          wlad Vladislav Vaintroub added a comment - - edited

          while not very important, I think "text" is not an ideal marker for that. There is client-side or server-side prepared statements, it is what meant here. , while "text" vs "binary" is just encoding of the result set row, nothing else.

          So , I think /* client prepare / and / server prepare / or anything that emphasize client-side vs server-side is better than / text / or / binary / . Even / c */ is

          wlad Vladislav Vaintroub added a comment - - edited while not very important, I think "text" is not an ideal marker for that. There is client-side or server-side prepared statements, it is what meant here. , while "text" vs "binary" is just encoding of the result set row, nothing else. So , I think /* client prepare / and / server prepare / or anything that emphasize client-side vs server-side is better than / text / or / binary / . Even / c */ is
          diego dupin Diego Dupin added a comment - good remark. changed with https://github.com/mariadb-corporation/mariadb-connector-j/commit/ad61d55e9c4c7c923ada10813bc7963a66897f29

          People

            diego dupin Diego Dupin
            diego dupin Diego Dupin
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.