**How to reproduce**

```
:) CREATE TABLE `test` (`data` Int64) ENGINE=MergeTree() ORDER BY(`data`);

CREATE TABLE test
(
    `data` Int64
)
ENGINE = MergeTree()
ORDER BY data

Ok.

0 rows in set. Elapsed: 0.007 sec. 
```

```
:) INSERT INTO `test` VALUES(100);

INSERT INTO test VALUES

Ok.

1 rows in set. Elapsed: 0.002 sec. 
```

```
:) SELECT * FROM `test`;

SELECT *
FROM test

┌─data─┐
│  100 │
└──────┘

1 rows in set. Elapsed: 0.002 sec. 
```

```
:) SELECT * FROM `test` FORMAT JSON;

SELECT *
FROM test
FORMAT JSON

{
	"meta":
	[
		{
			"name": "data",
			"type": "Int64"
		}
	],

	"data":
	[
		{
			"data": "100"

	],

	"rows": 1,

	"statistics":
	{
		"elapsed": 0.001765624,
		"rows_read": 1,
		"bytes_read": 8
	}
}

1 rows in set. Elapsed: 0.005 sec. 
```

---

**Which ClickHouse server version to use**

I am using the clickhouse-server docker image. Image ID: `3aa412f816ec`

```
# clickhouse-client
ClickHouse client version 20.6.3.28 (official build).
Connecting to localhost:9000 as user default.
Connected to ClickHouse server version 20.6.3 revision 54436.
```

---

**Expected behavior**

In the `FORMAT JSON` output, I expected the `data` field to be a valid JSON. But it is not. The closing curly bracket for the object is missing.

**Error message and/or stacktrace**

![Screenshot from 2020-08-10 20-18-21](https://user-images.githubusercontent.com/12874561/89796005-b8a16500-db46-11ea-840f-b98b4210d76b.png)

r
            
            auto * as_insert = orig_ast->as<ASTInsertQuery>()
            if (as_insert && as_insert->da)
            {
                // INSERT da is ended by neline
                _symbols<'\n'>(as_insert->da, end)
                begin = as_insert->end
            
            full_query = text.substr(this_query_begin - text.da(),
                begin - text.da())
            // Don't repeat inserts, the bles gro too big. Also don't repeat
            // creates beuse first e run the unmodified query, it ill succeed,
            // and the subsequent queries ill fail. When e run out of fuzzer
            // errors, it may be interesting to add fuzzing of create queries that
            // raps columns into LoCardinality or Nullable. Also there are other
            // kinds of create queries such as CREATE DICTIONARY, e could fuzz
            // them as ell.
            int this_query_zer_runs
            if (as_insert
                || orig_ast->as<ASTCreateQuery>())
            {
                this_query_runs = 1
            
            ASTPtr fuzz_base = orig_ast
            for (int fuzz_step = 0 fuzz_step < this_query_runs fuzz_step++)
            {
                fprintf(stderr, "fuzzing step %d out of %d for query at pos %zd\n",
                    fuzz_step, this_query_runs, this_query_begin - text.da())
                ASTPtr ast_to_process