Table merging may have a bug

[xllora]

This is not the expected result. It seems like the merge table is a bad merge.

Welcome to BadWolf vCli (0.4.2-dev)
Using driver "VOLATILE". Type quit; to exit

Session started at 2016-05-17 12:46:28.098374381 -0700 PDT

bql> create graph ?family;
[OK]
bql> load /tmp/family.txt ?family;
Successfully processed 6 lines from file "/tmp/family.txt".
Triples loaded into graphs:
    - ?family
bql> select ?grandparent from ?family where {?s "parent of"@[] /person<Amy Schumer> . ?grandparent "parent of"@[] ?s};
?grandparent
/person<Gavin Belson>
/person<Gavin Belson>
/person<Mary Belson>
/person<Mary Belson>

[OK]
bql> 

The data used to run this command in /tmp/family.txt is

/person<Gavin Belson>  "born in"@[]    /city<Springfield>
/person<Gavin Belson>  "parent of"@[]  /person<Peter Belson>
/person<Gavin Belson>  "parent of"@[]  /person<Mary Belson>
/person<Mary Belson>   "parent of"@[]  /person<Amy Schumer>
/person<Mary Belson>   "parent of"@[]  /person<Joe Schumer

[xllora]

Tested with a different driver (https://github.com/xllora/bwdrivers) to discard a bug on the volatile in memory driver. Same results were obtained. This narrows down the problem to the table merging.

[xllora]

The bug is in planner.addSpecifiedData. It is missing all the possible specification combinations, hence having partially flawed logic. Will write a few test to config it now that I know where it is.