💬 l0rinc commented on pull request "refactor: inline constant return values from `dbwrapper` write methods":
(https://github.com/bitcoin/bitcoin/pull/33042#issuecomment-3140630235)
The [IRC meeting](https://bitcoin-irc.chaincode.com/bitcoin-core-dev/2025-07-31#1140025) contained feedback on the overall direction:
> \<achow101> #topic dbwrapper read/write asymmetry (l0rinc)
> \<l0rinc> dbwrapper writes currently pretend to return bool but always return true, while real errors surface via exceptions – #33042 makes that explicit, but we need to decide the canonical error path
> \<l0rinc> `read` catches the exception and returns, but `write` always returned `true`, while th
...
(https://github.com/bitcoin/bitcoin/pull/33042#issuecomment-3140630235)
The [IRC meeting](https://bitcoin-irc.chaincode.com/bitcoin-core-dev/2025-07-31#1140025) contained feedback on the overall direction:
> \<achow101> #topic dbwrapper read/write asymmetry (l0rinc)
> \<l0rinc> dbwrapper writes currently pretend to return bool but always return true, while real errors surface via exceptions – #33042 makes that explicit, but we need to decide the canonical error path
> \<l0rinc> `read` catches the exception and returns, but `write` always returned `true`, while th
...