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

Readonly tables call for UNSET #3353

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

Readonly tables call for UNSET #3353

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

Comments

@monetdb-team
Copy link

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

Date: 2013-08-29 00:57:54 +0200
From: @mlkersten
To: SQL devs <>
Version: 11.15.7 (Feb2013-SP2)
CC: @njnes

Last updated: 2013-09-27 13:47:18 +0200

Comment 19102

Date: 2013-08-29 00:57:54 +0200
From: @mlkersten

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:23.0) Gecko/20100101 Firefox/23.0
Build Identifier:

The system allows to turn an individual table to become readonly. There is, however, no way back (except by copying it into another table).
The SQL statement
ALTER TABLE xyz SET READ ONLY;
should be complemented with
ALTER TABLE xyz UNSET READ ONLY;

Which seems a few liner fix in sql_parser, rel_schema

Reproducible: Always

Comment 19103

Date: 2013-08-31 14:43:00 +0200
From: @njnes

ALTER table xyz SET READ WRITE

Comment 19104

Date: 2013-08-31 15:35:37 +0200
From: @mlkersten

Do you also allow for

ALTER TABLE xyz SET WRITE ONLY

to allow for inserts but no updates?

Comment 19105

Date: 2013-08-31 16:06:44 +0200
From: @njnes

no just alter read only and read write (for now). The write only would require more work (ie changes to the storage layer, so only added if there is a use case).

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