bpo-41724: Explain when the conversion is not possible with detect_types enabled...

* Explain when the conversion is not possible with detect_types enabled

diff --git a/Doc/library/sqlite3.rst b/Doc/library/sqlite3.rst
index 13aa8c512d03197da9aee7a63f198a115572bc01..c36648775a615ee0d1c0de69b8183de3737f8eac 100644 (file)
--- a/Doc/library/sqlite3.rst
+++ b/Doc/library/sqlite3.rst
@@ -198,7 +198,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