ALTER TABLE operations silently remove previously set READ ONLY property #3362
Last updated: 2013-09-27 13:47:19 +0200
Date: 2013-09-12 14:43:26 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.57 Safari/537.36
As the example below shows, the READ ONLY property is reset silently by a primary key constraint. The same holds for a foreign key constraints - I haven't tried other ALTER TABLE statements.
I guess there should be no reason to reset the flag. If a reason exists, then this change shouldn't be silent.
sql>create table x(a int);
Date: 2013-09-18 16:09:31 +0200
fixed, it the intermediat table representation didn't properly set
Date: 2013-09-18 16:36:53 +0200
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=45a59d9fadb5
Date: 2013-09-27 09:31:11 +0200
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c0bf1946fc19
The text was updated successfully, but these errors were encountered: