Tin mới
erlend-aasland:sqlite-bound-trace
GitHub CopilotWrite better code with AI
GitHub Copilot appDirect agents from issue to merge
CodespacesInstant dev environments
Code ReviewManage code changes
Code QualityEnforce quality at merge
GitHub Advanced SecurityFind and fix vulnerabilities
Code securitySecure your code as you build
Secret protectionStop leaks before they start
GitHub SponsorsFund open source developers
Copilot for BusinessEnterprise-grade AI features
Premium SupportEnterprise-grade 24/7 support
Use expanded SQL when tracing using v2 API
Fall back to unexpanded sql if expanded sql is too long
Revert spurious print traceback change
Merge branch 'main' into sqlite-bound-trace
Merge branch 'main' into sqlite-bound-trace
Merge branch 'main' into sqlite-bound-trace
Chain exceptions if multiple exceptions happen
Merge branch 'main' into sqlite-bound-trace
Merge branch 'main' into sqlite-bound-trace
Merge branch 'main' into sqlite-bound-trace
Merge branch 'main' into sqlite-bound-trace
Merge branch 'main' into sqlite-bound-trace
We can't rely on sqlite_schema being present
Merge branch 'main' into sqlite-bound-trace
Merge branch 'main' into sqlite-bound-trace
Merge branch 'main' into sqlite-bound-trace
Merge branch 'main' into sqlite-bound-trace
Learn more about hiding disruptive comments
The reason will be displayed to describe this comment to others. Learn more.
Update Lib/test/test_sqlite3/test_hooks.py
PEP 8 Co-authored-by: Jelle Zijlstra <[email protected]>
Address review: clean up namespace
: Expand traced SQL statements in
sqlite3 regression: bound values are not expanded in traced statements #89301
gh-89301: Fix regression with bound values in traced SQLite statements #92053