Fix incorrect queries in example

Setting insert_deduplication_token: fix incorrect queries in example
This commit is contained in:
Igor Nikonov 2022-08-12 17:18:02 +02:00 committed by GitHub
parent 1f9d247299
commit 5768e40ef7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -1289,14 +1289,14 @@ ENGINE = MergeTree
ORDER BY A ORDER BY A
SETTINGS non_replicated_deduplication_window = 100; SETTINGS non_replicated_deduplication_window = 100;
INSERT INTO test_table Values SETTINGS insert_deduplication_token = 'test' (1); INSERT INTO test_table SETTINGS insert_deduplication_token = 'test' VALUES (1);
-- the next insert won't be deduplicated because insert_deduplication_token is different -- the next insert won't be deduplicated because insert_deduplication_token is different
INSERT INTO test_table Values SETTINGS insert_deduplication_token = 'test1' (1); INSERT INTO test_table SETTINGS insert_deduplication_token = 'test1' VALUES (1);
-- the next insert will be deduplicated because insert_deduplication_token -- the next insert will be deduplicated because insert_deduplication_token
-- is the same as one of the previous -- is the same as one of the previous
INSERT INTO test_table Values SETTINGS insert_deduplication_token = 'test' (2); INSERT INTO test_table SETTINGS insert_deduplication_token = 'test' VALUES (2);
SELECT * FROM test_table SELECT * FROM test_table