Unit tests that interact with the database operate on a single database connection. Since the connection returned for the DB_REPLICA flag is the same as the one returned for the DB_MASTER flag, code that attempts to write to the connection obtained with the DB_REPLICA flag will not fail.
This should be changed so that in tests, asking the LoadBalancer for a DB connection with the DB_REPLICA flag will return a wrapper that prevents write operations.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | daniel | T183242 DB handles obtained with DB_REPLICA should not allow writes | |||
| Invalid | daniel | T183244 Unit tests should fail when code writes to a DB connection obtained with the DB_REPLICA flag. |
Why only in tests? It would be useful for the same thing to be done in development environments where there is only one DB. That would make it easier for mistakes to be caught in development.
@Catrope yes, I see the point in that. But that should probably be a separate ticket. The mechanism may be the same, but the story is different. I'll file that.