mirror of
https://github.com/sigmasternchen/php-doc-en
synced 2025-03-16 00:48:54 +00:00
A little cleanup
git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@329450 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
parent
974b97a175
commit
44accdb4dc
2 changed files with 21 additions and 21 deletions
|
@ -197,7 +197,7 @@
|
|||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Support for built-in global transaction identifier feature of MySQL 5.6.5-m8 or newer.
|
||||
Support for built-in global transaction identifier feature of MySQL 5.6.5 or newer.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
|
@ -247,15 +247,15 @@
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
Servers of a replication cluster can be organized in groups.
|
||||
Queries can be manually directed to to a specific group using a SQL hint.
|
||||
Grouping can be used to partition (shard) data, or to cure the issue of
|
||||
hotspots in update anywhere setups.
|
||||
Servers of a replication cluster can be organized into groups. SQL hints
|
||||
can be used to manually direct queries to a specific group.
|
||||
Grouping can be used to partition (shard) the data, or to cure the issue of
|
||||
hotspots with updates.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
MySQL Replication filter are supported through the table filter.
|
||||
MySQL Replication filters are supported through the table filter.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
|
|
@ -54,31 +54,31 @@
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
Introduced <literal>node_group</literal> filter.
|
||||
Introduced the <literal>node_group</literal> filter.
|
||||
The filter lets you organize servers (master and slaves)
|
||||
in groups. Queries can be directed to a certain group of servers
|
||||
into groups. Queries can be directed to a certain group of servers
|
||||
by prefixing the query statement with a SQL hint/comment that contains
|
||||
a groups configuration name. Grouping can be used for
|
||||
partitioning and sharding but also to optimize for cache locality.
|
||||
In case of sharding, think of a group name as a shard key.
|
||||
the groups configured name. Grouping can be used for
|
||||
partitioning and sharding, and also to optimize for local caching.
|
||||
In the case of sharding, a group name can be thought of like a shard key.
|
||||
All queries for a given shard key will be executed on the
|
||||
configured shard. Please, note that sharding setups require
|
||||
both client and server support.
|
||||
configured shard. Note: both the client and server must support sharding
|
||||
for sharding to function with mysqlnd_ms.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Extended configuration file validation during PHP startup (RINIT).
|
||||
A warning will be thrown if the configuration file can not be read, is empty
|
||||
or parsing the JSON failed. Please note, execution is not halted.
|
||||
Warnings may appear in log files only depending on your PHP deployment.
|
||||
Distributions that aim to provide a pre-configured setup including a
|
||||
configuration file stub are asked to put <literal>{}</literal> into
|
||||
the configuration file to prevent any warnings about an invalid
|
||||
configuration.
|
||||
An <constant>E_WARNING</constant> level error will be thrown if the configuration
|
||||
file can not be read (permissions), is empty, or the file (JSON) could not be parsed.
|
||||
Warnings may appear in log files, which depending on how PHP is configured.
|
||||
Distributions that aim to provide a pre-configured setup, including a
|
||||
configuration file stub, are asked to put <literal>{}</literal> into
|
||||
the configuration file to prevent this warning about an invalid
|
||||
configuration file.
|
||||
</para>
|
||||
<para>
|
||||
Code examples from the source distribution have been updated.
|
||||
The code examples in the mysqlnd_ms source were updated.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
|
Loading…
Reference in a new issue