tarantool / tarantool / 7864 / 4

Ran 10 May 2017 09:22PM UTC

Files 290

Run time 34s

Badge

Embed ▾

Committed 10 May 2017 07:41PM UTC coverage: 55.444% (+0.1%) from 55.319%

Job # TARGET=coverage

Build Type

push

travis-ci

Committed by

kostja

Commit Message

Fix SELECT vdbe to match tarantool data layout

Data layout in Tarantool is very different from SQLite's.
Consider the following DDL statements:

CREATE TABLE foo (a, b PRIMARY KEY, c)
CREATE INDEX fI  ON foo(a)
INSERT INTO  foo VALUES (
  (1, "one", "junk1")
  (2, "two", "junk2")
)

In SQLite, two BTrees are created:

foo / primary key! other fields / -
 one!1|junk1
 two!2|junk2

fI / index key! primary key / -
 1!one
 2!two

In Tarantool, data is stored with the field order matching
the DDL -
 1|one|junk1
 2|two|junk2

Each index yields data in the same very format.

The following changes were made:

 * fix field number in Column-s at VDBE generation time;
 * fix IdxLE/IdxLT/IdxGE/IdxGT for index keys spanning non-adjacent
   tuple fields in an arbitrary order;
 * tell optimizer that every index can provide every column in order to
   eliminate lookups into the primary index.

Coverage Stats

36677 of 66151 relevant lines covered (55.44%)

514466.57 hits per line

tarantool / tarantool / 7864 / 4

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 7864.4 (TARGET=coverage)

tarantool / tarantool / 7864 / 4

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 7864.4 (TARGET=coverage)

README BADGES
x