There is currently this comment in the LiskDAO class:
// TODO: There is currently no protection on 'r' queries against writing.If this is still the case, this seems worthwhile fixing. If I understand correctly, there is currently nothing preventing writes on database connections established with establishConnection('r').
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Duplicate | epriestley | T4209 Multiserver / High-Availability Configuration | ||
| Resolved | epriestley | T10751 Make Phabricator Highly Available | ||
| Resolved | epriestley | T4571 Allow Phabricator to run in Read-Only Mode | ||
| Open | None | T8543 Prevent write queries from executing on "r" connections in LiskDAO |
Yep, this is correct. Context is that there's no difference today between 'r' and 'w' connections. Distinguishing between them (primarily so we can send some reads to a replica) has always been a theoretical far-future goal, and I think we're mostly consistent about connection use in practice, so this piece hasn't been built yet. Building it would make eventual replica reads easier.
(Just clarifying the title since I thought "write protection" might mean something like makeEphemeral().)