@@ -355,7 +355,7 @@ settings = {'merge_tree_min_rows_for_concurrent_read': 65535,
355
355
client.query(" SELECT event_type, sum(timeout) FROM event_errors WHERE event_time > '2022-08-01'" , settings = settings)
356
356
```
357
357
358
- ### Client _ command _ Method {#client-_ command _ -method}
358
+ ### Client ` command ` Method {#client-command -method}
359
359
360
360
Use the ` Client.command ` method to send SQL queries to the ClickHouse Server that do not normally return data or returns
361
361
a single primitive or array value rather than a full dataset. This method takes the following parameters:
@@ -387,7 +387,7 @@ result
387
387
Out[7 ]: 110
388
388
```
389
389
390
- ### Client _ query _ Method {#client-_ query _ -method}
390
+ ### Client ` query ` Method {#client-query -method}
391
391
392
392
The ` Client.query ` method is the primary way to retrieve a single "batch" dataset from the ClickHouse Server. It
393
393
utilizes the Native ClickHouse format over HTTP to transmit large datasets (up to approximately one million rows)
@@ -465,7 +465,7 @@ generator):
465
465
Each of these methods returns a ` ContextStream ` object that must be opened via a ` with ` statement to start consuming the
466
466
stream. See [ Advanced Queries (Streaming Queries)] ( #streaming-queries ) for details and examples.
467
467
468
- ### Client _ insert _ Method {#client-_ insert _ -method}
468
+ ### Client ` insert ` method {#client-insert -method}
469
469
470
470
For the common use case of inserting multiple records into ClickHouse, there is the ` Client.insert ` method. It takes the
471
471
following parameters:
@@ -561,7 +561,7 @@ Similarly, you could save data in [TabSeparated](/interfaces/formats#tabseparate
561
561
For use cases which do not require transformation between ClickHouse data and native or third party data types and
562
562
structures, the ClickHouse Connect client provides two methods for direct usage of the ClickHouse connection.
563
563
564
- #### Client _ raw_query _ Method {#client- _ raw_query _ -method }
564
+ #### Client ` raw_query ` Method {#client_raw_query_method }
565
565
566
566
The ` Client.raw_query ` method allows direct usage of the ClickHouse HTTP query interface using the client connection.
567
567
The return value is an unprocessed ` bytes ` object. It offers a convenient wrapper with parameter binding,
@@ -579,11 +579,11 @@ error handling, retries, and settings management using a minimal interface:
579
579
It is the caller's responsibility to handle the resulting ` bytes ` object. Note that the ` Client.query_arrow ` is just a
580
580
thin wrapper around this method using the ClickHouse ` Arrow ` output format.
581
581
582
- #### Client _ raw_stream _ Method {#client- _ raw_stream _ -method }
582
+ #### Client ` raw_stream ` Method {#client_raw_stream_method }
583
583
The ` Client.raw_stream ` method has the same API as the ` raw_query ` method, but returns an ` io.IOBase ` object which can be used
584
584
as a generator/stream source of ` bytes ` objects. It is currently utilized by the ` query_arrow_stream ` method.
585
585
586
- #### Client _ raw_insert _ Method {#client- _ raw_insert _ -method }
586
+ #### Client ` raw_insert ` Method {#client_raw_insert_method }
587
587
588
588
The ` Client.raw_insert ` method allows direct inserts of ` bytes ` objects or ` bytes ` object generators using the client
589
589
connection. Because it does no processing of the insert payload, it is highly performant. The method provides options
0 commit comments