What is the problem this feature will solve?
When using this new module mistakes made in providing the correct SQL for the tagstore functions often just result in an error "Failed to prepare statement" with a code of "ERR_SQLITE_ERR"
However the error thrown by sqlite itself (as picked up in the sqlite3 cli tool for instance, but other code as well) is more descriptive eg "No such column: availble" when I had misspelt a column name.
What is the feature you are proposing to solve the problem?
Make it easier to understand what the actual issue is.
What alternatives have you considered?
No response
What is the problem this feature will solve?
When using this new module mistakes made in providing the correct SQL for the tagstore functions often just result in an error "Failed to prepare statement" with a code of "ERR_SQLITE_ERR"
However the error thrown by sqlite itself (as picked up in the sqlite3 cli tool for instance, but other code as well) is more descriptive eg "No such column: availble" when I had misspelt a column name.
What is the feature you are proposing to solve the problem?
Make it easier to understand what the actual issue is.
What alternatives have you considered?
No response