From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: Kirill Yukhin <kyukhin@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH 1/2] sql: introduce sort order to key_part/key_part_def
Date: Tue, 8 May 2018 19:02:17 +0300 [thread overview]
Message-ID: <f60c71bd-aaa2-f97d-ae97-66534d483b11@tarantool.org> (raw)
In-Reply-To: <83009edbb2f4bc03444630a9239d746792a69c06.1525765048.git.kyukhin@tarantool.org>
Hello. Thanks for contributing! See 2 comments below.
1. I still can grep SQLITE_SO_ASC/DESC in build.c
On 08/05/2018 10:56, Kirill Yukhin wrote:
> Legacy SQL DD structs contained sort_order, defined per
> index column. During integration, those structs are to be
> vanished. So, introduce new field to part entity of Tarantool.
> This field states for sorting order of given part in give index.
> This field is ignored by Tarantool everywhere excpept for
> some of nested queries in SQL.
>
> Patch also replaces usages of SQL's stored sort order w/ this new
> field.
>
> Part of #3235
> ---
> src/box/key_def.cc | 28 ++++++++++++++++++++++------
> src/box/key_def.h | 16 +++++++++++++++-
> src/box/schema.cc | 30 ++++++++++++++++++++----------
> src/box/sql.c | 11 +++++++++--
> src/box/sql/build.c | 47 ++++++++++++++++++++++++++++++++++++-----------
> src/box/sql/expr.c | 9 ++++-----
> src/box/sql/insert.c | 3 ++-
> src/box/sql/parse.y | 10 +++++-----
> src/box/sql/pragma.c | 7 ++++---
> src/box/sql/select.c | 2 +-
> src/box/sql/sqliteInt.h | 20 ++++++++++++--------
> src/box/sql/vdbe.h | 1 +
> src/box/sql/where.c | 11 ++++++-----
> src/box/sql/wherecode.c | 10 ++++++----
> 14 files changed, 143 insertions(+), 62 deletions(-)
>
> diff --git a/src/box/sql/sqliteInt.h b/src/box/sql/sqliteInt.h
> index 8bb45c9..a811932 100644
> --- a/src/box/sql/sqliteInt.h
> +++ b/src/box/sql/sqliteInt.h
> @@ -3540,6 +3534,16 @@ sql_default_coll();
> bool
> space_is_view(Table *);
>
> +/**
> + * Return name of given column collation from index.
2. Irrelevant comment.
next prev parent reply other threads:[~2018-05-08 16:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 7:56 [tarantool-patches] [PATCH 0/2] sql: replace KeyInfo w/ key_def in SQL front-end Kirill Yukhin
2018-05-08 7:56 ` [tarantool-patches] [PATCH 1/2] sql: introduce sort order to key_part/key_part_def Kirill Yukhin
2018-05-08 16:02 ` Vladislav Shpilevoy [this message]
2018-05-10 13:01 ` [tarantool-patches] " Kirill Yukhin
2018-05-08 7:56 ` [tarantool-patches] [PATCH] sql: use collation pointers instead of names Kirill Yukhin
2018-04-17 18:06 ` [tarantool-patches] " Vladislav Shpilevoy
2018-04-18 5:42 ` Kirill Yukhin
2018-05-08 7:59 ` Kirill Yukhin
2018-05-08 7:56 ` [tarantool-patches] [PATCH 2/2] sql: replace KeyInfo with key_def Kirill Yukhin
2018-05-08 16:02 ` [tarantool-patches] " Vladislav Shpilevoy
2018-05-10 12:59 ` Kirill Yukhin
2018-05-11 11:22 ` Vladislav Shpilevoy
2018-05-11 12:56 ` Kirill Yukhin
2018-05-11 19:05 ` Vladislav Shpilevoy
2018-05-14 11:40 ` Kirill Yukhin
-- strict thread matches above, loose matches on Subject: below --
2018-04-13 8:05 [tarantool-patches] [PATCH] sql: use collation pointers instead of names Kirill Yukhin
2018-04-16 13:43 ` [tarantool-patches] " Vladislav Shpilevoy
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=f60c71bd-aaa2-f97d-ae97-66534d483b11@tarantool.org \
--to=v.shpilevoy@tarantool.org \
--cc=kyukhin@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH 1/2] sql: introduce sort order to key_part/key_part_def' \
/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