From: "n.pettik" <korablev@tarantool.org> To: tarantool-patches@freelists.org Cc: Kirill Yukhin <kyukhin@tarantool.org> Subject: [tarantool-patches] Re: [PATCH] sql: refactor SQL cursor to remove write ones Date: Thu, 4 Oct 2018 13:45:45 +0300 [thread overview] Message-ID: <036AB308-449D-4789-9F78-432CB93DF902@tarantool.org> (raw) In-Reply-To: <20181004071637.jncwrcmp62r7zucn@tarantool.org> > Hello Nikita! > Thanks for review. All nits applied. > Updated patch in the bottom. Branch force-pushed. IDK whether it is outlined in our review policy or not, but it is quite hard to review each time the whole patch again. So, it would be nice if you attached intermediate diff (i.e. diff between two versions of patch) in order to review only parts which have changed. Or, inline diff for each comment/remark. >>>> Finally, now I think about renaming CursorOpen to IteratorOpen: in fact after your >>>> patch cursor has turned almost in wrapper around index iterator. Such naming >>>> would underline the fact that ‘cursor’ is used only for read iterations over the space. >>> Yes, sure. Renamed. >> >> You forgot to update name of opcode in commit message. >> Also, you deleted not all mentions of OP_Cursor(Re)Open - just grep it Still, I can grep OP_OpenWrite. Eliminate it completely pls. Consider code style fixes: diff --git a/src/box/sql/select.c b/src/box/sql/select.c index 929d3c814..353b0af9f 100644 --- a/src/box/sql/select.c +++ b/src/box/sql/select.c @@ -86,7 +86,7 @@ struct SortCtx { ExprList *pOrderBy; /* The ORDER BY (or GROUP BY clause) */ int nOBSat; /* Number of ORDER BY terms satisfied by indices */ int iECursor; /* Cursor number for the sorter */ - /* Register, containing pointer to ephemeral space. */ + /** Register, containing pointer to ephemeral space. */ int reg_eph; int regReturn; /* Register holding block-output return address */ int labelBkOut; /* Start label for the block-output subroutine */ @@ -1005,7 +1005,8 @@ selectInnerLoop(Parse * pParse, /* The parser context */ regPrev = pParse->nMem + 1; pParse->nMem += nResultCol; - /* Actually, for DISTINCT handling + /* + * Actually, for DISTINCT handling * two op-codes were emitted here: * OpenTEphemeral & IteratorOpen. * So, we need to Noop one and @@ -1061,7 +1062,7 @@ selectInnerLoop(Parse * pParse, /* The parser context */ } case WHERE_DISTINCT_UNIQUE:{ - /** + /* * To handle DISTINCT two op-codes are * emitted: OpenTEphemeral & IteratorOpen. * addrTnct is address of first insn in Except for these nits, patch LGTM.
next prev parent reply other threads:[~2018-10-04 10:45 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-10-01 10:31 [tarantool-patches] " Kirill Yukhin 2018-10-02 11:56 ` [tarantool-patches] " n.pettik 2018-10-03 9:57 ` Kirill Yukhin 2018-10-04 2:21 ` n.pettik 2018-10-04 7:16 ` Kirill Yukhin 2018-10-04 10:45 ` n.pettik [this message] 2018-10-04 11:48 ` Kirill Yukhin 2018-10-04 12:00 ` Kirill Yukhin 2018-10-05 4:39 ` Kirill Yukhin
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=036AB308-449D-4789-9F78-432CB93DF902@tarantool.org \ --to=korablev@tarantool.org \ --cc=kyukhin@tarantool.org \ --cc=tarantool-patches@freelists.org \ --subject='[tarantool-patches] Re: [PATCH] sql: refactor SQL cursor to remove write ones' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox