From 6f2fd6eaa87e4bb2bf63f9ebeb00b2590435cf67 Mon Sep 17 00:00:00 2001
From: Jennifer Hodgdon <yahgrp@poplarware.com>
Date: Wed, 20 Mar 2013 09:06:05 -0700
Subject: [PATCH] Issue #1926758 by balsama, mitron: Fix code comment in
system.module
---
core/modules/system/system.module | 23 ++++++++++++-----------
1 file changed, 12 insertions(+), 11 deletions(-)
diff --git a/core/modules/system/system.module b/core/modules/system/system.module
index cd016f4370f1..13469b0e6f43 100644
--- a/core/modules/system/system.module
+++ b/core/modules/system/system.module
@@ -2515,17 +2515,18 @@ function system_filetransfer_info() {
function system_init() {
// Ignore slave database servers for this request.
//
- // In Drupal's distributed database structure, new data is written to the master
- // and then propagated to the slave servers. This means there is a lag
- // between when data is written to the master and when it is available on the slave.
- // At these times, we will want to avoid using a slave server temporarily.
- // For example, if a user posts a new node then we want to disable the slave
- // server for that user temporarily to allow the slave server to catch up.
- // That way, that user will see their changes immediately while for other
- // users we still get the benefits of having a slave server, just with slightly
- // stale data. Code that wants to disable the slave server should use the
- // db_set_ignore_slave() function to set $_SESSION['ignore_slave_server'] to
- // the timestamp after which the slave can be re-enabled.
+ // In Drupal's distributed database structure, new data is written to the
+ // master and then propagated to the slave servers. This means there is a
+ // lag between when data is written to the master and when it is available on
+ // the slave. At these times, we will want to avoid using a slave server
+ // temporarily. For example, if a user posts a new node then we want to
+ // disable the slave server for that user temporarily to allow the slave
+ // server to catch up. That way, that user will see their changes immediately
+ // while for other users we still get the benefits of having a slave server,
+ // just with slightly stale data. Code that wants to disable the slave
+ // server should use the db_ignore_slave() function to set
+ // $_SESSION['ignore_slave_server'] to the timestamp after which the slave
+ // can be re-enabled.
if (isset($_SESSION['ignore_slave_server'])) {
if ($_SESSION['ignore_slave_server'] >= REQUEST_TIME) {
Database::ignoreTarget('default', 'slave');
--
GitLab