Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix turbodbc.make_options parameters docstring #278

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix turbodbc.make_options parameters docstring #278

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions python/turbodbc/options.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,13 +54,13 @@ def make_options(read_buffer_size=None,
report a size of 2 billion characters.
Please note that this option only relates to retrieving results, not sending parameters to the
database.
:param force_extra_capacity_for_unicode Affects behavior/performance. Some ODBC drivers report the
:param force_extra_capacity_for_unicode: Affects behavior/performance. Some ODBC drivers report the
length of the ``VARCHAR``/``NVARCHAR`` field rather than the number of code points for which space is required
to be allocated, resulting in string truncations. Set this option to ``True`` to increase the memory
allocated for ``VARCHAR`` and ``NVARCHAR`` fields and prevent string truncations.
Please note that this option only relates to retrieving results, not sending parameters to the
database.
:param fetch_wchar_as_char Affects behavior. Some ODBC drivers retrieve single byte encoded strings
:param fetch_wchar_as_char: Affects behavior. Some ODBC drivers retrieve single byte encoded strings
into ``NVARCHAR`` fields of result sets, which are decoded incorrectly by turbodbc default settings,
resulting in corrupt strings. Set this option to ``True`` to have turbodbc treat ``NVARCHAR`` types
as narrow character types when decoding the fields in result sets.
Expand Down