gh-88239: Use sqlite3_stmt_busy() to determine if statements are in use by erlend-aasland · Pull Request #25984 · python/cpython
Erlend E. Aasland added 2 commits
Erlend E. Aasland added 2 commits
Erlend E. Aasland added 2 commits
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
changed the title
bpo-44073: Use sqlite3_stmt_busy() to check statement status
bpo-44073: Simplify sqlite3 statement handling; only reset statements when needed
erlend-aasland
changed the title
bpo-44073: Simplify
bpo-44073: Use sqlite3_stmt_busy() to determine if we need to reset statementssqlite3 statement handling; only reset statements when needed
Erlend E. Aasland added 2 commits
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
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