From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Tue, 11 Jul 2023 20:31:16 +0000 (-0700) Subject: [3.12] gh-96165: Clarify omitting the FROM clause in SQLite queries (GH-106513) ... X-Git-Tag: v3.12.0rc1~165 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=bf7e92583dd33aa7e83d5929f2138c5d6957f571;p=thirdparty%2FPython%2Fcpython.git [3.12] gh-96165: Clarify omitting the FROM clause in SQLite queries (GH-106513) (#106645) (cherry picked from commit fc7ff1af457e27b7d9752600b3436641be90f598) Co-authored-by: Mariusz Felisiak --- diff --git a/Doc/library/sqlite3.rst b/Doc/library/sqlite3.rst index 3ca8ea9011c7..26f4bfd06f5b 100644 --- a/Doc/library/sqlite3.rst +++ b/Doc/library/sqlite3.rst @@ -2522,6 +2522,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: