When throwing sqlite exceptions, it makes sense to pull the error message and include that in the exception. Use sqlite3_errmsg. I am concerned that this may have issues in a multithreaded environment, but since we're making sure one connection is being accessed by one thread at a time, it'll probably be fine.
kpgalligan
commented
1 year ago
When throwing sqlite exceptions, it makes sense to pull the error message and include that in the exception. Use
sqlite3_errmsg. I am concerned that this may have issues in a multithreaded environment, but since we're making sure one connection is being accessed by one thread at a time, it'll probably be fine.