~drizzle-trunk/drizzle/development

« back to all changes in this revision

Viewing changes to docs/replication.rst

  • Committer: Andrew Hutchings
  • Date: 2011-02-02 12:51:57 UTC
  • mto: (2157.1.1 build)
  • mto: This revision was merged to the branch mainline in revision 2158.
  • Revision ID: andrew@linuxjedi.co.uk-20110202125157-r6thh7ox4g9l90ec
Make transaction_message_threshold a read-only global variable instead of a per-session variable
Make replication_dictionary column lengths use transation_message_threshold

Show diffs side-by-side

added added

removed removed

Lines of Context:
24
24
    default global value is FALSE which will not include the query in the
25
25
    messages. It can be controlled per session, as well. For example:
26
26
 
27
 
    .. code-block:: mysql
28
 
 
29
 
       drizzle> set @@replicate_query = 1;
 
27
    ``drizzle> set @@replicate_query = 1;``
30
28
 
31
29
    The stored query should be used as a guide only, and never executed
32
30
    on a slave to perform replication as this will lead to incorrect results.
166
164
It's easiest to understand this mechanism by following through a real-world
167
165
scenario.
168
166
 
169
 
Suppose the following table:
170
 
 
171
 
.. code-block:: mysql
 
167
Suppose the following table::
172
168
 
173
169
  CREATE TABLE test.person
174
170
  (
180
176
 
181
177
Also suppose that test.t1 contains 1 million records.
182
178
 
183
 
Next, suppose a client issues the SQL statement:
184
 
 
185
 
.. code-block:: mysql
 
179
Next, suppose a client issues the SQL statement::
186
180
 
187
181
  UPDATE test.person SET is_active = 'N';
188
182