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.
I have problem with dynamic field in clickhouse json datatype. My database looks for now like this
If some field contains string like bellow
SELECT log.message, FROM click.log_json_better WHERE ...
with result
but this is representation, select for whole log
truncated result with message part
so it's stored as escaped string and API is returning it as escaped string as well

"{\"took\":7,\"errors\":false...trunc
Then when I clicked on such row, it is escaped again and created query has no match in DB.
so I've made a simple fix with SqlString.raw. I've tried to match record with md5, to not use whole field content for search query, but no luck with playing around with escaping and stripping escaping.
At first, I've removed
Search value/object key too large.
error, because this was problem that I've encountered as first, trowing error crashed whole UI. I've had no problem with string 10x larger than 1000 chars.