Skip to content

Commit a1bb6f9

Browse files
authored
Fix docstring about default parameter approach (#287)
1 parent c3fdc2f commit a1bb6f9

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/databricks/sql/client.py

+4-4
Original file line numberDiff line numberDiff line change
@@ -709,18 +709,18 @@ def execute(
709709
Execute a query and wait for execution to complete.
710710
711711
The parameterisation behaviour of this method depends on which parameter approach is used:
712-
- With INLINE mode (default), parameters are rendered inline with the query text
713-
- With NATIVE mode, parameters are sent to the server separately for binding
712+
- With INLINE mode, parameters are rendered inline with the query text
713+
- With NATIVE mode (default), parameters are sent to the server separately for binding
714714
715715
This behaviour is controlled by the `use_inline_params` argument passed when building a connection.
716716
717717
The paramstyle for these approaches is different:
718718
719-
If the connection was instantiated with use_inline_params=False, then parameters
719+
If the connection was instantiated with use_inline_params=False (default), then parameters
720720
should be given in PEP-249 `named` paramstyle like :param_name. Parameters passed by positionally
721721
are indicated using a `?` in the query text.
722722
723-
If the connection was instantiated with use_inline_params=True (default), then parameters
723+
If the connection was instantiated with use_inline_params=True, then parameters
724724
should be given in PEP-249 `pyformat` paramstyle like %(param_name)s. Parameters passed by positionally
725725
are indicated using a `%s` marker in the query. Note: this approach is not recommended as it can break
726726
your SQL query syntax and will be removed in a future release.

0 commit comments

Comments
 (0)