[MCOL-948] Columnstore engine(1.0.11): Transaction is NOT integrated with TRIGGER in an INSERT statement ! Created: 2017-09-29 Updated: 2021-01-17 Resolved: 2021-01-17 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | MariaDB Server, writeengine |
| Affects Version/s: | 1.0.11 |
| Fix Version/s: | N/A |
| Type: | New Feature | Priority: | Major |
| Reporter: | Gavin Chen | Assignee: | Todd Stoffel (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | Transaction, integrity | ||
| Environment: |
CentOS 7 |
||
| Epic Link: | ColumnStore Compatibility Improvements |
| Description |
|
Current culumnstore can't support constraints FOREIGN KEY,UNIQUE,PRIMARY KEY, but these constraints is very important for avoid logic error from applications, I try use TRIGGER to avoid the limitations, but I found NOT an integrated transaction in an INSERT statement: CREATE TABLE detail_inno DELIMITER // INSERT INTO detail_inno(fk,sData) VALUES(1,'data1'),(2,'data2'),(4,'data4');--GOOD: NOT any records inserted at here. |
| Comments |
| Comment by David Thompson (Inactive) [ 2017-09-29 ] |
|
Correct, most analytics databases don't always support more complex referential integrity due to larger data scales since normally the data is not system of record. Even if we fix the trigger support for dml inserts, it would be a very high amount of work to enforce this with bulk load since that is working at the lower level writeengine level rather than mysqld level. If you need to do some validation and cleanup of your source data, you would be better loading and validating to an innodb table and perform any clean up there before doing an insert select to the columnstore table (this is essentially the ELT paradigm). |
| Comment by Gavin Chen [ 2017-09-30 ] |
|
Hi,David: |