SQLite Forum

[SOLVED] Getting SQLITE_LOCKED where SQLITE_BUSY is expected
Perhaps the CLI application can be modified to display the extended error code as well as the text.  It is displayed in some places, but not in others.

Instead of printing the error message as:

`Error: <message text>`

could it perhaps be displayed as:

`Error: <message text> (<extended error code>)`

Also, could the word `Error:` be augmented to indicate WHERE the error was detected:  `Error during Prepare:` or `Error during Step:` if it can be determined whether the error was detected at PREPARE or STEP time (though it is noteworthy that errors can already be distinguished because there are very few errors that can occur at BOTH places rather than only one).

That is instead of the CLI printing the message `Error: database is locked` in the above circumstance, perhaps the CLI could print the message `Error during Step: database is locked (517)`.

This would make the CLI more useful as a debugging tool.