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

Restart sequence with a non atomic sub-query cardinality gives wrong error message #6657

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

Comments

@monetdb-team
Copy link

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

Date: 2018-11-06 15:00:07 +0100
From: @PedroTadim
To: SQL devs <>
Version: 11.31.11 (Aug2018-SP1)

Last updated: 2019-06-11 14:31:33 +0200

Comment 26662

Date: 2018-11-06 15:00:07 +0100
From: @PedroTadim

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

Restarting a sequence with a non atomic sub-query leads to the generation of an unknown MAL function call.

Reproducible: Always

Steps to Reproduce:

  1. create sequence "testme" as integer start with 1;
  2. alter sequence "testme" restart with (select 1 union select 2);

Actual Results:

An error message in the MAL layer:
'sqlcatalog.alter_seq' undefined in: sqlcatalog.alter_seq(X_17:str, X_19:str, X_21:ptr, X_16:bat[:lng]);

Expected Results:

An error message unrelated to MAL.

I already fixed this bug, I'm just mentioning it here.

Comment 26664

Date: 2018-11-06 15:16:55 +0100
From: @PedroTadim

For complete details, see https://dev.monetdb.org/hg/MonetDB/rev/6d4152a6de27

Comment 27043

Date: 2019-06-11 14:31:33 +0200
From: MonetDB Mercurial Repository <>

Changeset ac68d2a866de 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=ac68d2a866de

Changeset description:

fixes for  bug #6657
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