Scripted sqlite - error messages go where?

[cw1nte]

Feel I should know or find answer to this, but it might take me a while and also be useful to others...
I actually fixed the source of my issue by spotting that I can add the IF EXISTS clause to a DROP TABLE command I had in the start of a script designed to collate & summarise key data from my logs into a TopConcerns table...
But next time I get SQL errors it would save time if it were possible to see the culprit line and the error message...
Enjoying 0.9.0!

[tstack]

Yes, error reporting is poor and needs to be improved. Have you tried running lnav with the debug log option (-d /path/to/log). I think many of the error messages will come out there.

[cw1nte]

Ahhh yes, I have used that before and forgot that is where I saw SQL errors. I might leave it on more but there used to be rather a lot of timer loops logging no actions as I recall. I'll look again to refresh myself!

[cw1nte]

I am not seeing lots of repeated logs from curl_looper = good. Did not see see any sql script error though I did see the script fail in the command area. Direct ;sql_commands do report their error in the command area nicely enough.