Tarantool development patches archive
 help / color / mirror / Atom feed
From: Kirill Shcherbatov <kshcherbatov@tarantool.org>
To: tarantool-patches@freelists.org
Cc: korablev@tarantool.org, Kirill Shcherbatov <kshcherbatov@tarantool.org>
Subject: [tarantool-patches] [PATCH v2 0/4] sql: get rid off sqlite3NestedParse
Date: Tue, 10 Jul 2018 20:08:07 +0300	[thread overview]
Message-ID: <cover.1531242355.git.kshcherbatov@tarantool.org> (raw)

As we are going to implement parser as separate library,
we should get rid off sqlite3NestedParse calls.   
Last usages in statistics update could be trivially rewrited
to do not start parsing. We manually build AST structures 
simmilar to parser did and manually call sql_table_delete_from. 
Finilly, I've removed all sqlite3NestedParse mentionings.
Also slightly refactored OP_Open{Write,Read} opcodes and 
vdbe_emit_open_cursor function to use index_id instead of tnum.

Branch: http://github.com/tarantool/tarantool/tree/kshch/gh-3496-no-nested-parse
Issue: https://github.com/tarantool/tarantool/issues/3496

Kirill Shcherbatov (3):
  sql: get rid off sqlite3NestedParse in clean stats
  sql: remove usless sqlite3NestedParse function
  sql: refactor vdbe_emit_open_cursor calls

Vladislav Shpilevoy (1):
  sql: remove OP_LoadPtr

 src/box/sql/analyze.c   | 110 +++++++++++---------------
 src/box/sql/build.c     | 202 ++++++++++++++++++------------------------------
 src/box/sql/delete.c    |  32 ++------
 src/box/sql/expr.c      |   5 +-
 src/box/sql/fkey.c      |   3 +-
 src/box/sql/insert.c    | 120 ++++++++++++++--------------
 src/box/sql/parse.y     |  12 +--
 src/box/sql/pragma.c    |  36 +++++----
 src/box/sql/select.c    |   4 +-
 src/box/sql/sqliteInt.h |  39 +++++-----
 src/box/sql/tokenize.c  |   2 +-
 src/box/sql/trigger.c   |  45 ++++-------
 src/box/sql/update.c    |  15 ++--
 src/box/sql/vdbe.c      |  73 +++--------------
 src/box/sql/where.c     |  10 ++-
 15 files changed, 272 insertions(+), 436 deletions(-)

-- 
2.7.4

             reply	other threads:[~2018-07-10 17:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10 17:08 Kirill Shcherbatov [this message]
2018-07-10 17:08 ` [tarantool-patches] [PATCH v2 1/4] sql: get rid off sqlite3NestedParse in clean stats Kirill Shcherbatov
2018-07-10 17:52   ` [tarantool-patches] " n.pettik
2018-07-11  7:22     ` Kirill Shcherbatov
2018-07-11 12:19       ` n.pettik
2018-07-11 12:23         ` Kirill Shcherbatov
2018-07-11 13:16           ` n.pettik
2018-07-10 17:08 ` [tarantool-patches] [PATCH v2 2/4] sql: remove usless sqlite3NestedParse function Kirill Shcherbatov
2018-07-10 18:22   ` [tarantool-patches] " n.pettik
2018-07-11  7:22     ` Kirill Shcherbatov
2018-07-10 17:08 ` [tarantool-patches] [PATCH v2 3/4] sql: refactor vdbe_emit_open_cursor calls Kirill Shcherbatov
2018-07-10 18:22   ` [tarantool-patches] " n.pettik
2018-07-11  7:22     ` Kirill Shcherbatov
2018-07-10 17:08 ` [tarantool-patches] [PATCH v2 4/4] sql: remove OP_LoadPtr Kirill Shcherbatov
2018-07-10 18:34   ` [tarantool-patches] " n.pettik
2018-07-10 20:23     ` Vladislav Shpilevoy
2018-07-10 20:34       ` n.pettik
2018-07-11 13:45 ` [tarantool-patches] Re: [PATCH v2 0/4] sql: get rid off sqlite3NestedParse 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=cover.1531242355.git.kshcherbatov@tarantool.org \
    --to=kshcherbatov@tarantool.org \
    --cc=korablev@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='Re: [tarantool-patches] [PATCH v2 0/4] sql: get rid off sqlite3NestedParse' \
    /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