This change allows developers to diagnose and debug difficult SQLite issues in a backwards compatible fashion by using sqlite3_extended_errcode() to return more detailed "extended error codes". See https://sqlite.org/rescode.html#primary_result_codes_versus_extended_result_codes for more info. There is no current mechanism to enable this.
This change allows developers to diagnose and debug difficult SQLite issues in a backwards compatible fashion by using
sqlite3_extended_errcode()to return more detailed "extended error codes". See https://sqlite.org/rescode.html#primary_result_codes_versus_extended_result_codes for more info. There is no current mechanism to enable this.In particular, at dropbox we have seen
SQLITE_IOERRquite a bit in production and expect that the extended error code will give us more detailed diagnosis (likeSQLITE_IOERR_VNODEreferenced in https://github.com/stephencelis/SQLite.swift/issues/630 and by apple https://devstreaming-cdn.apple.com/videos/wwdc/2016/242vdhuk4hmwrxnb465/242/242_whats_new_in_core_data.pdf)