We discussed this, and the main issue is that while we could error-suppress our way through all the failing write queries, it's just kind of sweeping things under the rug, causing potential future bugs where important queries are invisibly failing.
A better approach is to change it so that an error handling option is passed to the query functions which allows normal error handling, no error handling, or error logging.
We would have to review all existing use of the option to use the correct flag.
We would then have to reimplement working readonly_db support.