From: Mariusz Felisiak <felisiak.mariusz@gmail.com>
Date: Tue, 11 Jul 2023 20:09:04 +0000 (+0200)
Subject: gh-96165: Clarify omitting the FROM clause in SQLite queries (#106513)
X-Git-Tag: v3.13.0a1~1429
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=fc7ff1af457e27b7d9752600b3436641be90f598;p=thirdparty%2FPython%2Fcpython.git

gh-96165: Clarify omitting the FROM clause in SQLite queries (#106513)
---

diff --git a/Doc/library/sqlite3.rst b/Doc/library/sqlite3.rst
index bc69387fca8a..f6a8714519f5 100644
--- a/Doc/library/sqlite3.rst
+++ b/Doc/library/sqlite3.rst
@@ -2519,6 +2519,13 @@ Queries now return :class:`!Row` objects:
    >>> row["RADIUS"]  # Column names are case-insensitive.
    6378
 
+.. note::
+
+    The ``FROM`` clause can be omitted in the ``SELECT`` statement, as in the
+    above example. In such cases, SQLite returns a single row with columns
+    defined by expressions, e.g. literals, with the given aliases
+    ``expr AS alias``.
+
 You can create a custom :attr:`~Cursor.row_factory`
 that returns each row as a :class:`dict`, with column names mapped to values: