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
-
Activity
Field | Original Value | New Value |
---|---|---|
Issue Type | Bug [ 1 ] | New Feature [ 2 ] |
Priority | Critical [ 2 ] | Minor [ 4 ] |
Epic Link |
|
Assignee | Todd Stoffel [ toddstoffel ] |
Fix Version/s | N/A [ 22302 ] |
Rank | Ranked higher |
Rank | Ranked lower |
Fix Version/s | 1.7 [ 23713 ] | |
Fix Version/s | N/A [ 22302 ] |
Fix Version/s | 1.6 [ 23712 ] | |
Fix Version/s | 1.7 [ 23713 ] |
Rank | Ranked lower |
Rank | Ranked lower |
Fix Version/s | Icebox [ 22302 ] | |
Fix Version/s | 1.6 [ 23712 ] |
Rank | Ranked higher |
Rank | Ranked higher |
Rank | Ranked higher |
Rank | Ranked higher |
Resolution | Won't Do [ 10201 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
CHECK() is not yet a supported feature for ColumnStore. Please see the create table syntax:
https://mariadb.com/kb/en/library/columnstore-create-table/
I'll modify this to be a feature request accordingly.