Extented error codes aren't reported properly

[aureliar8]

Extented error codes aren't reported properly

[zombiezen]

Thanks for the report. I've been thinking this over for the last week and I don't believe adding the SQLite constant name to every error message is in the best interest of most users. While it's unfortunate the extended error codes in this case do not provide a more useful message, I think that addressing that in upstream SQLite is better for the ecosystem, if you want to bring it up there. The responsibility and scope of this project is to be a pretty direct binding to SQLite but adapt it for Go idioms.

As you saw, applications that want to log more detailed information about failures can already use sqlite.ErrCode to extract the more exact failure and do custom reporting.

I did address the potential duplication issue by skipping the branch you mentioned if the message reported by the connection is the same as the result code's message. However, in tracing the code, opening a connection does not call extreserr at any point, which suggests this string is what SQLite returns, not what this library returns.