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

"BATproject: does not match always" on abusive use of ALTER TABLE SET READ ONLY #3709

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

Comments

@monetdb-team
Copy link

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

Date: 2015-04-19 15:33:23 +0200
From: sorear
To: SQL devs <>
Version: 11.19.7 (Oct2014-SP1)
CC: @njnes

Last updated: 2015-05-07 12:37:25 +0200

Comment 20817

Date: 2015-04-19 15:33:23 +0200
From: sorear

This is a reliably reproducable error condition:

sql>drop table s10; create table s10 (x int); start transaction; insert into s10 values (8); alter table s10 set read only; select * from s10; rollback;
operation successful (3.3s)
operation successful (3.3s)
auto commit mode: on
1 affected row (3.3s)
operation successful (3.3s)
GDK reported error.
BATproject: does not match always
auto commit mode: on
sql>

It seems that in this case (readonly=1, nonempty ibat) sql.tid returns one row while sql.bind(x) returns zero, and algebra.leftfetchjoin throws the error above. Works fine if the table creation is moved into the transaction.

Comment 20824

Date: 2015-04-20 21:14:12 +0200
From: @njnes

disallow changing to readonly on tables without standing inserts.

Comment 20825

Date: 2015-04-20 21:21:06 +0200
From: MonetDB Mercurial Repository <>

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

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=df0d1a4be0ed

Changeset description:

added test for bug #3709
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