This repository was archived by the owner on Nov 7, 2025. It is now read-only.
Comments/docs on "bring your own table" and ALTER situation
#1484
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When users connect Quesma to ClickHouse and would like to work with tables which are not created by Quesma,
ALTERstatements doesn't work, unlessattributes_*columns are present. Therefore we end up with:ALTERexecutedattributes_*column to store it.In general, we discourage such setup in read/write scenarios - it's always better to have Quesma manage your CH tables so that it controls any required metadata.
In most cases BYOT is used in read-only, ingest-disabled situations. However, there's a simple way to mitigate this limitation: