should DROP TABLE work even after a table has been SET READ ONLY?
hi, this bugzilla ticket is marked as resolved, but this behavior seems unintuitive to me.. is it ok? thanks team CREATE TABLE my_table AS SELECT 1 AS my_column WITH DATA; ALTER TABLE my_table SET READ ONLY; SELECT COUNT(*) FROM my_table; DROP TABLE my_table; from https://www.monetdb.org/bugzilla/show_bug.cgi?id=3895
Hi, I assume Niels' comment in the bug report says it all. In my words: "READ ONLY" (in MonetDB) protects against table content changes, but not against schema changes (DDL). (The main (and only?) intention of READ ONLY is to make (read-only) queries simpler (and hence faster) by avoiding the need to take care of "deltas", i.e., changes to the tables content that have not yet been merged into the genuine table storage. (Content changes are not instantly applied on / merged into the genuine table storage to facilitate correct and efficient transaction management.)) Consequently, the bug should have been / was meant to be closed with "Won't fix" or "Invalid" rather than "Fixed". Best, Stefan ----- On Mar 7, 2016, at 12:00 AM, Anthony Damico ajdamico@gmail.com wrote:
hi, this bugzilla ticket is marked as resolved, but this behavior seems unintuitive to me.. is it ok? thanks team
CREATE TABLE my_table AS SELECT 1 AS my_column WITH DATA; ALTER TABLE my_table SET READ ONLY; SELECT COUNT(*) FROM my_table; DROP TABLE my_table;
from https://www.monetdb.org/bugzilla/show_bug.cgi?id=3895
_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
-- | Stefan.Manegold@CWI.nl | DB Architectures (DA) | | www.CWI.nl/~manegold/ | Science Park 123 (L321) | | +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) |
MonetDB is coherent with a file system rights. $ touch /tmp/readonly && chmod -w /tmp/readonly $ echo hello > /tmp/readonly bash: /tmp/readonly: Permission denied But you can remove it: $ rm -f /tmp/readonly ; echo $? 0 Le 07/03/2016 00:00, Anthony Damico a écrit :
hi, this bugzilla ticket is marked as resolved, but this behavior seems unintuitive to me.. is it ok? thanks team
CREATE TABLE my_table AS SELECT 1 AS my_column WITH DATA; ALTER TABLE my_table SET READ ONLY; SELECT COUNT(*) FROM my_table; DROP TABLE my_table;
from https://www.monetdb.org/bugzilla/show_bug.cgi?id=3895
_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
-- Guillaume Savary Securactive R&D
funny, i had thought read only was primarily used to keep stupid users (like me) from ourselves.. this all makes sense, and as usual windows behavior is the exception. thanks!!! On Mon, Mar 7, 2016 at 5:28 AM, Guillaume Savary < guillaume.savary@securactive.net> wrote:
MonetDB is coherent with a file system rights.
$ touch /tmp/readonly && chmod -w /tmp/readonly
$ echo hello > /tmp/readonly bash: /tmp/readonly: Permission denied
But you can remove it:
$ rm -f /tmp/readonly ; echo $? 0
Le 07/03/2016 00:00, Anthony Damico a écrit :
hi, this bugzilla ticket is marked as resolved, but this behavior seems unintuitive to me.. is it ok? thanks team
CREATE TABLE my_table AS SELECT 1 AS my_column WITH DATA; ALTER TABLE my_table SET READ ONLY; SELECT COUNT(*) FROM my_table; DROP TABLE my_table;
from https://www.monetdb.org/bugzilla/show_bug.cgi?id=3895
_______________________________________________ users-list mailing listusers-list@monetdb.orghttps://www.monetdb.org/mailman/listinfo/users-list
-- Guillaume Savary Securactive R&D
_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
participants (3)
-
Anthony Damico -
Guillaume Savary -
Stefan Manegold