From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: tarantool-patches@freelists.org, Nikita Pettik <korablev@tarantool.org> Cc: kostja@tarantool.org Subject: [tarantool-patches] Re: [PATCH 5/9] sql: improve type determination for column meta Date: Tue, 16 Apr 2019 17:12:52 +0300 [thread overview] Message-ID: <9edb1536-e63c-d9ab-5130-1f38b822d698@tarantool.org> (raw) In-Reply-To: <c19cef87e6d8e54a527600a0c424346c15c12ce8.1555252410.git.korablev@tarantool.org> On 14/04/2019 18:04, Nikita Pettik wrote: > In most cases we don't assign and store type of node of expression AST > (except for constant literals). To determine type of node we use > sql_expr_type() function, which implements logic of quite simple > recursive tree traversal. Before this patch we set type of node after > code generation in sqlExprCodeTarget() without any traversal. This > approach is way worse even then sql_expr_type(). Why? How is recursive scan of the tree better than simple access to a struct's attribute? I see, that your patch improves type determination precision, but I do not understand how, and what a perf price for that? If you are not sure about the price, we could ask Alexander to run benches on your branch before pushing into the master. > So, to improve accuracy > of type determination, let's always call that method and remove type > assignment in sqlExprCodeTarget(). This patch fixes the issue https://github.com/tarantool/tarantool/issues/4126. > --- > src/box/sql/expr.c | 19 ++++--------------- > src/box/sql/select.c | 2 +- > test/sql/check-clear-ephemeral.result | 2 +- > test/sql/gh-2347-max-int-literals.result | 2 +- > test/sql/gh-3199-no-mem-leaks.result | 18 +++++++++--------- > test/sql/gh-3888-values-blob-assert.result | 2 +- > test/sql/persistency.result | 8 ++++---- > test/sql/transition.result | 4 ++-- > test/sql/types.result | 10 +++++----- > 9 files changed, 28 insertions(+), 39 deletions(-) >
next prev parent reply other threads:[~2019-04-16 14:12 UTC|newest] Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-04-14 15:03 [tarantool-patches] [PATCH 0/9] Introduce type BOOLEAN in SQL Nikita Pettik 2019-04-14 15:03 ` [tarantool-patches] [PATCH 1/9] sql: refactor mem_apply_numeric_type() Nikita Pettik 2019-04-14 15:04 ` [tarantool-patches] [PATCH 2/9] sql: disallow text values participate in sum() aggregate Nikita Pettik 2019-04-16 14:12 ` [tarantool-patches] " Vladislav Shpilevoy 2019-04-18 17:54 ` n.pettik 2019-04-22 18:02 ` Vladislav Shpilevoy 2019-04-23 19:58 ` n.pettik 2019-04-14 15:04 ` [tarantool-patches] [PATCH 3/9] sql: use msgpack types instead of custom ones Nikita Pettik 2019-04-16 14:12 ` [tarantool-patches] " Vladislav Shpilevoy 2019-04-18 17:54 ` n.pettik 2019-04-22 18:02 ` Vladislav Shpilevoy 2019-04-23 19:58 ` n.pettik 2019-04-14 15:04 ` [tarantool-patches] [PATCH 4/9] sql: introduce type boolean Nikita Pettik 2019-04-16 14:12 ` [tarantool-patches] " Vladislav Shpilevoy 2019-04-18 17:54 ` n.pettik 2019-04-22 18:02 ` Vladislav Shpilevoy 2019-04-23 19:58 ` n.pettik 2019-04-23 21:06 ` Vladislav Shpilevoy 2019-04-14 15:04 ` [tarantool-patches] [PATCH 5/9] sql: improve type determination for column meta Nikita Pettik 2019-04-16 14:12 ` Vladislav Shpilevoy [this message] 2019-04-18 17:54 ` [tarantool-patches] " n.pettik 2019-04-22 18:02 ` Vladislav Shpilevoy 2019-04-23 19:58 ` n.pettik 2019-04-14 15:04 ` [tarantool-patches] [PATCH 6/9] sql: make comparison predicate return boolean Nikita Pettik 2019-04-16 14:12 ` [tarantool-patches] " Vladislav Shpilevoy 2019-04-18 17:54 ` n.pettik 2019-04-14 15:04 ` [tarantool-patches] [PATCH 7/9] sql: make predicates accept and " Nikita Pettik 2019-04-16 14:12 ` [tarantool-patches] " Vladislav Shpilevoy 2019-04-18 17:55 ` n.pettik 2019-04-14 15:04 ` [tarantool-patches] [PATCH 9/9] sql: make <search condition> accept only boolean Nikita Pettik 2019-04-16 14:12 ` [tarantool-patches] " Vladislav Shpilevoy 2019-04-18 17:55 ` n.pettik 2019-04-22 18:02 ` Vladislav Shpilevoy 2019-04-23 19:59 ` n.pettik 2019-04-23 21:06 ` Vladislav Shpilevoy 2019-04-23 22:01 ` n.pettik [not found] ` <b2a84f129c2343d3da3311469cbb7b20488a21c2.1555252410.git.korablev@tarantool.org> 2019-04-16 14:12 ` [tarantool-patches] Re: [PATCH 8/9] sql: make LIKE predicate return boolean result Vladislav Shpilevoy 2019-04-18 17:55 ` n.pettik 2019-04-22 18:02 ` Vladislav Shpilevoy 2019-04-23 19:58 ` n.pettik 2019-04-24 10:28 ` [tarantool-patches] Re: [PATCH 0/9] Introduce type BOOLEAN in SQL Vladislav Shpilevoy 2019-04-25 8:46 ` 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=9edb1536-e63c-d9ab-5130-1f38b822d698@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=korablev@tarantool.org \ --cc=kostja@tarantool.org \ --cc=tarantool-patches@freelists.org \ --subject='[tarantool-patches] Re: [PATCH 5/9] sql: improve type determination for column meta' \ /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