◐ Shell
clean mode source ↗

gh-88239: Use sqlite3_stmt_busy() to determine if statements are in use by erlend-aasland · Pull Request #25984 · python/cpython

pablogsal

erlend-aasland

Erlend E. Aasland added 2 commits

June 7, 2021 01:10

Erlend E. Aasland added 2 commits

June 18, 2021 00:13

Erlend E. Aasland added 2 commits

August 19, 2021 09:35
Instead of resetting a statment on every "exit" path, only reset when
needed:
  1. reset before first sqlite3_step()
  2. on cursor close, reset the statement attached to it

@erlend-aasland erlend-aasland changed the title bpo-44073: Use sqlite3_stmt_busy() to check statement status bpo-44073: Simplify sqlite3 statement handling; only reset statements when needed

Aug 19, 2021

@erlend-aasland erlend-aasland changed the title bpo-44073: Simplify sqlite3 statement handling; only reset statements when needed bpo-44073: Use sqlite3_stmt_busy() to determine if we need to reset statements

Aug 19, 2021

Erlend E. Aasland added 2 commits

September 21, 2021 14:30

@erlend-aasland erlend-aasland changed the title bpo-44073: Use sqlite3_stmt_busy() to determine if we need to reset statements gh-88239: Use sqlite3_stmt_busy() to determine if we need to reset statements

Apr 10, 2022

@erlend-aasland erlend-aasland changed the title gh-88239: Use sqlite3_stmt_busy() to determine if we need to reset statements gh-88239: Use sqlite3_stmt_busy() to determine if statements are in use

Jun 23, 2022