a) suppressing errors giving surprising results (hint: try opening a misspelt database file)
b) "syntax error near 'as'": almost impossible to find errors in longer sql statements (are other engines better, giving line numbers?)
c) no full outer join https://www.sqlite.org/omitted.html which can be worked around by writing about the double code, thus giving chance for twice as much errors
a - This way you'll still have valid sqlite context (object), which would contain the error message (and the memory allocated to it), but it would be in erroneous state. That could embed much more information rather than just returning an error code.
c - My guess is that would put more memory pressure in terms of rewriting the SQL statement, which could explode more than what a typical sqlite user would expect (there is much tighter memory usage limit, and it could be even more limited).
e.g. SQLite is not trying to do everything, and does not encourage you to. I guess you basically wrap your style around it, rather than other way around.
But what bugs me about sqlite is
a) suppressing errors giving surprising results (hint: try opening a misspelt database file)
b) "syntax error near 'as'": almost impossible to find errors in longer sql statements (are other engines better, giving line numbers?)
c) no full outer join https://www.sqlite.org/omitted.html which can be worked around by writing about the double code, thus giving chance for twice as much errors
I really love the simplicity of using it, though!