ClickHouse/docs/en/introduction/features_considered_disadvantages.md

# ClickHouse Features that Can be Considered Disadvantages

1. Lack of full transactions.
2. Previously recorded data can't be changed or deleted with low latency and high query frequency. Mass deletions to clear data that is no longer relevant or falls under [GDPR](https://gdpr-info.eu) regulations. Batch changes to data are in development (as of July, 2018).
3. The sparse index makes ClickHouse ill-suited for point-reading single rows on its own keys.
Capitalize most words in titles of docs/en/ 2018-08-07 16:49:40 +00:00			`# ClickHouse Features that Can be Considered Disadvantages`
Sources for english documentation switched to Markdown. Edit page link is fixed too for both language versions of documentation. 2017-12-28 15:13:23 +00:00
Update of english documentation (#2918) * Updating of english translation. * Some bugs are fixed. 2018-09-04 11:18:59 +00:00			`1. Lack of full transactions.`
			`2. Previously recorded data can't be changed or deleted with low latency and high query frequency. Mass deletions to clear data that is no longer relevant or falls under [GDPR](https://gdpr-info.eu) regulations. Batch changes to data are in development (as of July, 2018).`
Apply useful patches from TANKER-453459 2018-09-05 08:41:04 +00:00			`3. The sparse index makes ClickHouse ill-suited for point-reading single rows on its own keys.`
Sources for english documentation switched to Markdown. Edit page link is fixed too for both language versions of documentation. 2017-12-28 15:13:23 +00:00