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

AliSQL: [Feature] Issue#8: SELECT FOR UPDATE WAIT

Details

    • Task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.3.0
    • OTHER
    • None

    Description

      Summary:
      --------
      The feature provides a way to set lock wait timeout for some statement.
       
      Usage:
      ------
      1.select ... for update [wait [n]|no_wait]
      2.select ... lock in share mode [wait [n]|no_wait]
      3.lock table ... [wait [n]|no_wait]
       
      no_wait: the query not wait for locks, instead of return immeditly, and print
      "ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction;"
       
      wait [n]: n is wait time in second, after wait n seconds for locks,
      return and print errors;
      

      https://github.com/alibaba/AliSQL/commit/d7764b5565e3f36e8e49d8bb2238da1a8459e94f

      Attachments

        Issue Links

          Activity

            svoj Sergey Vojtovich added a comment - monty , please review patch for this task: http://lists.askmonty.org/pipermail/commits/2017-February/010625.html plinux , FYI

            Patch is in bb-10.3-alisql, to be merged to 10.3 later.

            svoj Sergey Vojtovich added a comment - Patch is in bb-10.3-alisql, to be merged to 10.3 later.

            Final implementation has NOWAIT instead of NO_WAIT. The comments indicate it's intentional.

            elenst Elena Stepanova added a comment - Final implementation has NOWAIT instead of NO_WAIT . The comments indicate it's intentional.

            People

              svoj Sergey Vojtovich
              svoj Sergey Vojtovich
              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.