Interesting idea; when I've finished diagnosing my current problem, it might be
worth expanding the repertoire of the Android library.
I presume that the sqlite logging function could be used to get the message at
least, is that correct? IIRC, it's called on an error and the OS file-related
errors are often still available, but I am very rusty on this stuff.
On 8/05/2017 5:32 PM, Rowan Worth wrote:
Preserving the underlying cause is still possible to do portably; something
like sqlite3_os_errmsg() would provide an "opaque" string suitable for
user/developer consumption.
_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
