Skip to content

Feature for tracing SQL queries #150

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
simonw opened this issue Sep 7, 2020 · 0 comments
Closed

Feature for tracing SQL queries #150

simonw opened this issue Sep 7, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@simonw
Copy link
Owner

simonw commented Sep 7, 2020

Debugging sqlite-utils when something weird happens (e.g. #149) can be a bit tricky since it runs a bunch of different SQL statements behind the scenes.

An optional "tracing" mechanism for seeing what SQL is being executed would be useful.
@simonw simonw added the enhancement New feature or request label Sep 7, 2020
simonw added a commit that referenced this issue Sep 7, 2020
@simonw
Sketched out a trace mechanism, refs #150
64aa5cf
@simonw simonw mentioned this issue Sep 7, 2020
Merged
simonw added a commit that referenced this issue Sep 7, 2020
@simonw
Sketched out a trace mechanism, refs #150
6104cbd
@simonw simonw closed this as completed in cf2cb24 Sep 7, 2020
simonw added a commit that referenced this issue Sep 7, 2020
@simonw
Release 2.17
f28cd4d 
Refs #144, #148, #149, #150, #151, #152, #153
simonw added a commit that referenced this issue Sep 8, 2020
@simonw
Tracer example using print, refs #150
32f1bad
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@simonw