• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

tarantool / tarantool / 7864

Build:
Build:
LAST BUILD BRANCH: skaplun/bump-luajit-master
DEFAULT BRANCH: master
Ran 10 May 2017 09:22PM UTC
Jobs 1
Files 290
Run time 37s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

pending completion
7864

push

travis-ci

kostja
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.

36677 of 66151 relevant lines covered (55.44%)

514466.57 hits per line

Jobs
ID Job ID Ran Files Coverage
4 7864.4 (TARGET=coverage) 10 May 2017 09:22PM UTC 0
55.44
Travis Job 7864.4
Source Files on build 7864
Detailed source file information is not available for this build.
  • Back to Repo
  • Travis Build #7864
  • 3189d4f6 on github
  • Prev Build on 1.8 (#7863)
  • Next Build on 1.8 (#7866)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc