Tarantool development patches archive
 help / color / mirror / Atom feed
From: Kirill Yukhin <kyukhin@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH v9] sql: add index_def to struct Index
Date: Wed, 4 Jul 2018 13:46:11 +0300	[thread overview]
Message-ID: <20180704104611.uwgbg4bayrvzuuzg@tarantool.org> (raw)
In-Reply-To: <2d4908aa-0243-8dc3-e109-707cb482b7f6@tarantool.org>

Hello,
On 03 июл 14:37, Ivan Koptelov wrote:
> In previous patch versions I didn't fix one test, which prints all error
> codes.
> At failed, because I added new error code. Now the test is fixed.
> > > Now every sqlite struct Index is created with tnt struct
> > > index_def inside. This allows us to use tnt index_def
> > > in work with sqlite indexes in the same manner as with
> > > tnt index and is a step to remove sqlite Index with
> > > tnt index.
> > > Fields coll_array, coll_id_array, aiColumn, sort_order
> > > and zName are removed from Index. All usages of this
> > > fields changed to usage of corresponding index_def
> > > fields.
> > > index_is_unique(), sql_index_collation() and
> > > index_column_count() are removed with calls of
> > > index_def corresponding fields.
> > > 
> > > Closes: #3369
> > > 
> > > ---
> > > Branch:
> > > https://github.com/tarantool/tarantool/tree/sb/gh-3369-use-index-def-in-select-and-where
> > > 
> > > Issue:https://github.com/tarantool/tarantool/issues/3369
I've checked the patch into 2.0 branch.

--
Regards, Kirill Yukhin

  parent reply	other threads:[~2018-07-04 10:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-13  7:30 [tarantool-patches] Re: [PATCH v3] " Ivan Koptelov
2018-06-18 18:45 ` Kirill Shcherbatov
2018-06-21 12:57   ` [tarantool-patches] Re: [PATCH v4] " Ivan Koptelov
2018-06-22  8:46     ` Kirill Shcherbatov
2018-06-27 17:46       ` [tarantool-patches] Re: [PATCH v5] " Ivan Koptelov
2018-06-27 17:57         ` Kirill Shcherbatov
2018-06-28 18:49           ` Vladislav Shpilevoy
2018-06-29 13:49             ` [tarantool-patches] Re: [PATCH v6] " Ivan Koptelov
2018-06-29 20:46               ` Vladislav Shpilevoy
     [not found]                 ` <146c3bd4-e9e6-f943-5a42-c6db966d1c9c@tarantool.org>
2018-07-03  9:00                   ` [tarantool-patches] Re: [PATCH v8] " Ivan Koptelov
2018-07-03  9:46                 ` [tarantool-patches] Re: [PATCH v8.5] " Ivan Koptelov
2018-07-03 12:13                   ` Vladislav Shpilevoy
2018-07-03 11:37                 ` [tarantool-patches] Re: [PATCH v9] " Ivan Koptelov
2018-07-03 23:54                   ` n.pettik
2018-07-04  0:08                     ` Vladislav Shpilevoy
2018-07-04  9:17                       ` n.pettik
2018-07-04 15:55                     ` [tarantool-patches] Re: [PATCH v11] " Ivan Koptelov
2018-07-04 19:28                       ` n.pettik
2018-07-05 14:50                         ` Ivan Koptelov
2018-07-06  0:51                           ` n.pettik
2018-07-08 14:17                             ` [tarantool-patches] Re: [PATCH v2] " Ivan Koptelov
2018-07-04 10:46                   ` Kirill Yukhin [this message]
2018-07-04 12:10                     ` [tarantool-patches] Re: [PATCH v9] " 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=20180704104611.uwgbg4bayrvzuuzg@tarantool.org \
    --to=kyukhin@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='[tarantool-patches] Re: [PATCH v9] sql: add index_def to struct Index' \
    /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