From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Sun, 20 Dec 2020 00:02:58 +0000 (-0800) Subject: bpo-41724: Explain when the conversion is not possible with detect_types enabled... X-Git-Tag: v3.8.7~4 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=24862b02dfd1e2843727f28fa2ba05828fdfa8de;p=thirdparty%2FPython%2Fcpython.git bpo-41724: Explain when the conversion is not possible with detect_types enabled (GH-23855) (GH-23863) * Explain when the conversion is not possible with detect_types enabled (cherry picked from commit 09a36cdfb7c22f44df45b44e5561776206bcedfb) Co-authored-by: sblondon --- diff --git a/Doc/library/sqlite3.rst b/Doc/library/sqlite3.rst index 314d3a58e275..e49332449589 100644 --- a/Doc/library/sqlite3.rst +++ b/Doc/library/sqlite3.rst @@ -197,7 +197,9 @@ Module functions and constants *detect_types* defaults to 0 (i. e. off, no type detection), you can set it to any combination of :const:`PARSE_DECLTYPES` and :const:`PARSE_COLNAMES` to turn - type detection on. + type detection on. Due to SQLite behaviour, types can't be detected for generated + fields (for example ``max(data)``), even when *detect_types* parameter is set. In + such case, the returned type is :class:`str`. By default, *check_same_thread* is :const:`True` and only the creating thread may use the connection. If set :const:`False`, the returned connection may be shared