Details
-
New Feature
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Won't Do
-
1.1.0
-
None
-
CentOS 6.4
Description
CHECK constrains on a ColumnStore table works for INSERTs, but not for UPDATEs. UPDATEs that violates CHECK constraints are executed anyway.
DROP TABLE IF EXISTS columnstore1; |
CREATE TABLE columnstore1(c1 INTEGER NOT NULL, CHECK(c1 > 10)) Engine=ColumnStore; |
INSERT INTO columnstore1 VALUES(10); |
INSERT INTO columnstore1 VALUES(11); |
UPDATE columnstore1 SET c1 = 10; |
SELECT c1 FROM columnstore1; |
In the above example, the first INSERT fails, the second succeeds and the update is also successful, meaning that we end up with invalid data in the table.
Attachments
Issue Links
- relates to
-
MCOL-3693 Table CHECK constraint pretends to work but breaks transactional properties
- Closed