Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sqlitelogictest algebra.rangejoin undefined #6610

Closed
monetdb-team opened this issue Nov 30, 2020 · 0 comments
Closed

Sqlitelogictest algebra.rangejoin undefined #6610

monetdb-team opened this issue Nov 30, 2020 · 0 comments
Labels

Comments

@monetdb-team
Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2018-06-10 10:32:53 +0200
From: @PedroTadim
To: SQL devs <>
Version: 11.29.7 (Mar2018-SP1)
CC: @njnes

Last updated: 2018-08-31 13:23:10 +0200

Comment 26479

Date: 2018-06-10 10:32:53 +0200
From: @PedroTadim

User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36
Build Identifier:

Running the query bellow, results in an undefined MAL function call. I guess it's another exp_convert is missing :)

Reproducible: Always

Steps to Reproduce:

  1. CREATE TABLE tab1(col0 INTEGER, col1 INTEGER, col2 INTEGER);
  2. CREATE TABLE tab2(col0 INTEGER, col1 INTEGER, col2 INTEGER);
  3. INSERT INTO tab1 VALUES (64,10,57), (3,26,54), (80,13,96);
  4. INSERT INTO tab2 VALUES (7,31,27), (79,17,38), (78,59,26);
  5. SELECT DISTINCT * FROM tab2, tab1 AS cor0 CROSS JOIN tab1 WHERE cor0.col1 NOT BETWEEN tab2.col0 AND ( NULL );

Actual Results:

ERROR = !'algebra.rangejoin' undefined in: algebra.rangejoin(X_23:bat[:int], X_38:bat[:int], X_53:int, nil:BAT, nil:BAT, true:bit, true:bit, nil:lng);

Expected Results:

PostgreSQL gets this results, however our behavior with BETWEEN NULL is different.

col0 | col1 | col2 | col0 | col1 | col2 | col0 | col1 | col2
------+------+------+------+------+------+------+------+------
78 | 59 | 26 | 3 | 26 | 54 | 3 | 26 | 54
78 | 59 | 26 | 3 | 26 | 54 | 64 | 10 | 57
78 | 59 | 26 | 3 | 26 | 54 | 80 | 13 | 96
78 | 59 | 26 | 64 | 10 | 57 | 3 | 26 | 54
78 | 59 | 26 | 64 | 10 | 57 | 64 | 10 | 57
78 | 59 | 26 | 64 | 10 | 57 | 80 | 13 | 96
78 | 59 | 26 | 80 | 13 | 96 | 3 | 26 | 54
78 | 59 | 26 | 80 | 13 | 96 | 64 | 10 | 57
78 | 59 | 26 | 80 | 13 | 96 | 80 | 13 | 96
79 | 17 | 38 | 3 | 26 | 54 | 3 | 26 | 54
79 | 17 | 38 | 3 | 26 | 54 | 64 | 10 | 57
79 | 17 | 38 | 3 | 26 | 54 | 80 | 13 | 96
79 | 17 | 38 | 64 | 10 | 57 | 3 | 26 | 54
79 | 17 | 38 | 64 | 10 | 57 | 64 | 10 | 57
79 | 17 | 38 | 64 | 10 | 57 | 80 | 13 | 96
79 | 17 | 38 | 80 | 13 | 96 | 3 | 26 | 54
79 | 17 | 38 | 80 | 13 | 96 | 64 | 10 | 57
79 | 17 | 38 | 80 | 13 | 96 | 80 | 13 | 96

The following two queries give the same error as well:

  1. CREATE TABLE tab0(col0 INTEGER, col1 INTEGER, col2 INTEGER);
  2. INSERT INTO tab0 VALUES (89,91,82), (35,97,1), (24,86,33);
  3. SELECT ALL * FROM tab1, tab2, tab2 AS cor0 WHERE + tab2.col2 BETWEEN ( tab1.col0 ) AND NULL;
  4. SELECT * FROM tab0, tab2 AS cor0 WHERE ( - tab0.col0 ) BETWEEN ( cor0.col2 ) AND ( NULL );

The sqlite output is empty for these two queries, but again our behavior with BETWEEN NULL is different.

Comment 26480

Date: 2018-06-10 10:33:30 +0200
From: MonetDB Mercurial Repository <>

Changeset d79ebbbaf60f made by Pedro Ferreira pedro.ferreira@monetdbsolutions.com in the MonetDB repo, refers to this bug.

For complete details, see https//devmonetdborg/hg/MonetDB?cmd=changeset;node=d79ebbbaf60f

Changeset description:

Added test for Bug #6610

Comment 26512

Date: 2018-06-27 14:27:12 +0200
From: MonetDB Mercurial Repository <>

Changeset b85418f83f4e made by Niels Nes niels@cwi.nl in the MonetDB repo, refers to this bug.

For complete details, see https//devmonetdborg/hg/MonetDB?cmd=changeset;node=b85418f83f4e

Changeset description:

fix bug #6610

Comment 26513

Date: 2018-06-27 14:27:42 +0200
From: @njnes

added missing constant 2 full bat conversion

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant