-
Konstantin Osipov authored
Allow disjunctions in SELECT WHERE clause and LIMIT clause in SELECT, to be able to cover the problem reported in Bug#729758. Fix a bug with prepare_gdb arguments (remove an extra space in -e option). Add a simple test for Bug#729758. The following bugs were reported in the process: Bug#729789 "Zero limit is treated the same as no limit" Bug#730593 "Bad data if incomplete tuple" Bug#730613 "SELECT with a disjunction on multiple keys returns matching tuples twice"
Konstantin Osipov authoredAllow disjunctions in SELECT WHERE clause and LIMIT clause in SELECT, to be able to cover the problem reported in Bug#729758. Fix a bug with prepare_gdb arguments (remove an extra space in -e option). Add a simple test for Bug#729758. The following bugs were reported in the process: Bug#729789 "Zero limit is treated the same as no limit" Bug#730593 "Bad data if incomplete tuple" Bug#730613 "SELECT with a disjunction on multiple keys returns matching tuples twice"
tarantool.cfg 561 B
slab_alloc_arena = 0.1
pid_file = "box.pid"
# Use -a not -a to work correctly on FreeBSD
#
logger="tee -a tarantool.log"
primary_port = 33013
secondary_port = 33014
admin_port = 33015
rows_per_wal = 50
namespace[0].enabled = 1
namespace[0].index[0].type = "HASH"
namespace[0].index[0].unique = 1
namespace[0].index[0].key_field[0].fieldno = 0
namespace[0].index[0].key_field[0].type = "STR"
namespace[0].index[1].type = "TREE"
namespace[0].index[1].unique = 0
namespace[0].index[1].key_field[0].fieldno = 1
namespace[0].index[1].key_field[0].type = "STR"