[issue44976] [sqlite3] lazy creation of result rows

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue44976] [sqlite3] lazy creation of result rows

Pablo Galindo Salgado added the comment: New changeset 3df0fc89bc2714f5ef03e36a926bc795dcd5e05a by Erlend Egeberg Aasland in branch 'main': bpo-44976: Lazy creation of sqlite3 result rows (GH-27884) https://github.com/python/cpython/commit/3df0fc89bc2714f5ef03e36a926bc795dcd5e05a

[issue44976] [sqlite3] lazy creation of result rows

Erlend E. Aasland added the comment: Historical note: The current behaviour was introduced in pysqlite v2.0.2 (May 21 2005), in order to be able to finalise statements and thus close cursors as soon as possible. However, that effect was cancelled just after a couple of months, by the

[issue44976] [sqlite3] lazy creation of result rows

Change by Erlend E. Aasland : -- keywords: +patch pull_requests: +26339 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27884 ___ Python tracker

[issue44976] [sqlite3] lazy creation of result rows

New submission from Erlend E. Aasland : Currently, we build the first result row in the _pysqlite_query_execute() loop if sqlite3_step() returned SQLITE_ROW. When the user asks for a row (for example, using sqlite3.Cursor.fetchone()), this pre-built row is returned, and the next row is