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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: