#5256 - readonly_db massively maintenance code broken: re-add support for this
-
By PDStig
- Added
- 8 views
| Identifier | #5256 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | readonly_db massively maintenance code broken: re-add support for this |
| Status | Open |
| Tags |
Roadmap: Over the horizon (custom) |
| Handling member | Deleted |
| Addon | core |
| Description | Currently (especially in the upcoming v11), the Composr site crashes when a DB loses write access. It is not feasible for us to fix that at this time given the complexity. Therefore, this has been knocked back to feature-request status.
readonly_db has been marked unsupported, not even for bugs. The maintenance sheet will need updating once we support this again. |
| Steps to reproduce | |
| Additional information | Attached is the start of me working on this issue. However, I stopped when I realized this issue extends far beyond core Composr even for a simple page load. There are queries across different hooks, such as the blocks, which will also break the site when DB loses write access. |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
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.