Skip to content

Commit faf764b

Browse files
authored
Merge pull request #4231 from ClickHouse/Blargian-patch-84
Fix headers
2 parents 4633529 + 60d00a7 commit faf764b

File tree

1 file changed

+6
-6
lines changed
  • docs/integrations/language-clients/python

1 file changed

+6
-6
lines changed

docs/integrations/language-clients/python/index.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -355,7 +355,7 @@ settings = {'merge_tree_min_rows_for_concurrent_read': 65535,
355355
client.query("SELECT event_type, sum(timeout) FROM event_errors WHERE event_time > '2022-08-01'", settings=settings)
356356
```
357357

358-
### Client _command_ Method {#client-_command_-method}
358+
### Client `command` Method {#client-command-method}
359359

360360
Use the `Client.command` method to send SQL queries to the ClickHouse Server that do not normally return data or returns
361361
a single primitive or array value rather than a full dataset. This method takes the following parameters:
@@ -387,7 +387,7 @@ result
387387
Out[7]: 110
388388
```
389389

390-
### Client _query_ Method {#client-_query_-method}
390+
### Client `query` Method {#client-query-method}
391391

392392
The `Client.query` method is the primary way to retrieve a single "batch" dataset from the ClickHouse Server. It
393393
utilizes the Native ClickHouse format over HTTP to transmit large datasets (up to approximately one million rows)
@@ -465,7 +465,7 @@ generator):
465465
Each of these methods returns a `ContextStream` object that must be opened via a `with` statement to start consuming the
466466
stream. See [Advanced Queries (Streaming Queries)](#streaming-queries) for details and examples.
467467

468-
### Client _insert_ Method {#client-_insert_-method}
468+
### Client `insert` method {#client-insert-method}
469469

470470
For the common use case of inserting multiple records into ClickHouse, there is the `Client.insert` method. It takes the
471471
following parameters:
@@ -561,7 +561,7 @@ Similarly, you could save data in [TabSeparated](/interfaces/formats#tabseparate
561561
For use cases which do not require transformation between ClickHouse data and native or third party data types and
562562
structures, the ClickHouse Connect client provides two methods for direct usage of the ClickHouse connection.
563563

564-
#### Client _raw_query_ Method {#client-_raw_query_-method}
564+
#### Client `raw_query` Method {#client_raw_query_method}
565565

566566
The `Client.raw_query` method allows direct usage of the ClickHouse HTTP query interface using the client connection.
567567
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:
579579
It is the caller's responsibility to handle the resulting `bytes` object. Note that the `Client.query_arrow` is just a
580580
thin wrapper around this method using the ClickHouse `Arrow` output format.
581581

582-
#### Client _raw_stream_ Method {#client-_raw_stream_-method}
582+
#### Client `raw_stream` Method {#client_raw_stream_method}
583583
The `Client.raw_stream` method has the same API as the `raw_query` method, but returns an `io.IOBase` object which can be used
584584
as a generator/stream source of `bytes` objects. It is currently utilized by the `query_arrow_stream` method.
585585

586-
#### Client _raw_insert_ Method {#client-_raw_insert_-method}
586+
#### Client `raw_insert` Method {#client_raw_insert_method}
587587

588588
The `Client.raw_insert` method allows direct inserts of `bytes` objects or `bytes` object generators using the client
589589
connection. Because it does no processing of the insert payload, it is highly performant. The method provides options

0 commit comments

Comments
 (0)