UnamedRus

There is some confusion between "nested object" and "JSON", i guess > So for example, a single string or number would be valid JSON. As, just simple value is valid...

> Our new JSON type is actually Object type that can store only objects And it's planned to stay in that way in future? Just asking about compatibility with standard.

IMO, syntax for that should follow TABLE OVERRIDE idea. Ie separated from JSON column definition itself, it's already can be too big https://github.com/ClickHouse/ClickHouse/issues/31480

Any specific reason to make distinction between SKIP and SKIP PREFIX? I assume, that if a.b.c is "object", that if we set SKIP a.b.c, user may want to skip it...

> has type JSON, it cannot be NULL but can be empty. So, JSON can't be NULL ?

> What is the point for JSON to be NULL? There is difference between empty JSON and Null for people Like there is difference between empty Array and Null. For...

> `SELECT json.^a.b, json.^d.e.f FROM test;` May be adopt postgreSQL syntax then? https://www.postgresql.org/docs/current/functions-json.html#FUNCTIONS-JSON-PROCESSING ``` SELECT json->'a'->'b', json->'d'-> 'e'->'f' FROM test; or SELECT json #> '{a,b}', json #> '{d,e,f}' FROM test;...

> We will just need to allow Nullable(JSON) together with Nullable(Array/Tuple/Map). Sure, what's your opinion on `'null'`, which is also valid JSON object. It will need special implementation for JSON...

> So right now you will need to do insert select into another table. Why not just add new column and materialize it from old one (via update or DEFAULT)?...

Hi, We are currently in process of writing procedure to migrate CHK from old to new syntax. > Maybe I could create a new Keeper installation that syncs data with...