diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-08-02 12:10:09 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-08-02 12:10:09 +0300 |
| commit | 1930898566965dbc1bd779089ec9e58e17674268 (patch) | |
| tree | a1e4384e4e8927431b637daa885dc8793cbb0035 /doc/development/verifying_database_capabilities.md | |
| parent | 2691cff8296517651e4bcd8adac09640f8cc28f5 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/verifying_database_capabilities.md')
| -rw-r--r-- | doc/development/verifying_database_capabilities.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/verifying_database_capabilities.md b/doc/development/verifying_database_capabilities.md index a6575dc79f8..c5e854701c2 100644 --- a/doc/development/verifying_database_capabilities.md +++ b/doc/development/verifying_database_capabilities.md @@ -30,7 +30,7 @@ end The database can be used in read-only mode. In this case we have to make sure all GET requests don't attempt any write operations to the database. If one of those requests wants to write to the database, it needs -to be wrapped in a `Gitlab::Database.main.read_only?` or `Gitlab::Database.main.read_write?` +to be wrapped in a `Gitlab::Database.read_only?` or `Gitlab::Database.read_write?` guard, to make sure it doesn't for read-only databases. We have a Rails Middleware that filters any potentially writing |