File: explain.test.lua

package info (click to toggle)
tarantool 2.6.0-1.4
  • links: PTS, VCS
  • area: main
  • in suites: sid, trixie
  • size: 85,412 kB
  • sloc: ansic: 513,775; cpp: 69,493; sh: 25,650; python: 19,190; perl: 14,973; makefile: 4,178; yacc: 1,329; sql: 1,074; pascal: 620; ruby: 190; awk: 18; lisp: 7
file content (43 lines) | stat: -rwxr-xr-x 1,076 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
#!/usr/bin/env tarantool
test = require("sqltester")
test:plan(3)

-- gh-3231: make sure that there is no redundant OP_Goto at the
-- start of VDBE program. In other words OP_Init jumps exactly to
-- the next opcode (i.e. opcode with address 1).
--
test:do_execsql_test(
    "explain-1.0",
    [[
        CREATE TABLE t1(id INTEGER PRIMARY KEY, a INT);
        INSERT INTO t1 VALUES(1, 2), (3, 4), (5, 6);
        SELECT * FROM t1;
    ]], {
        -- <explain-1.0>
        1, 2, 3, 4, 5, 6
        -- </explain-1.0>
    })

test:do_test(
    "explain-1.1",
    function()
        opcodes = test:execsql("EXPLAIN SELECT * FROM t1;")
        return opcodes[1]
    end,
        -- <explain-1.1>
        0, 'Init', 0, 1, 0, '', '00', 'Start at 1'
        -- </explain-1.1>
    )

test:do_test(
    "explain-1.2",
    function()
        opcodes = test:execsql("EXPLAIN SELECT a + 1 FROM t1 WHERE id = 4 OR id = 5;")
        return opcodes[1]
    end,
        -- <explain-1.2>
        0, 'Init', 0, 1, 0, '', '00', 'Start at 1'
        -- </explain-1.2>
    )

test:finish_test()