svn: /phpdoc/en/trunk/reference/mysqlnd_ms/ changes.xml functions/mysqlnd-ms-set-qos.xml

uw Wed, 20 Feb 2013 17:13:50 +0000 Revision: http://svn.php.net/viewvc?view=revision&revision=329523 Log: Document BC break and bug fix related to mysqlnd_ms_set_qos() Changed paths: U phpdoc/en/trunk/reference/mysqlnd_ms/changes.xml U phpdoc/en/trunk/reference/mysqlnd_ms/functions/mysqlnd-ms-set-qos.xml Modified: phpdoc/en/trunk/reference/mysqlnd_ms/changes.xml =================================================================== --- phpdoc/en/trunk/reference/mysqlnd_ms/changes.xml 2013-02-20 17:10:01 UTC (rev 329522) +++ phpdoc/en/trunk/reference/mysqlnd_ms/changes.xml 2013-02-20 17:13:50 UTC (rev 329523) @@ -72,13 +72,28 @@ was combined it could happened that the SQL hints got ignored. In some case the SQL hints did work, in other cases they did not. The new behaviour is more consistent. SQL hints will always be ignore for - the duration of a transaction, if transaction stickiness is configured. + the duration of a transaction, if + <link linkend="ini.mysqlnd-ms-plugin-config-v2.trx-stickiness">transaction stickiness</link> + is enabled. </para> <para> Please note, transaction boundary detection continues to be based on API call monitoring. SQL commands controlling transactions are not monitored. </para> </listitem> + <listitem> + <para> + BC break and bug fix. Calls to <function>mysqlnd_ms_set_qos</function> + will fail when done in the middle of a transaction if + <link linkend="ini.mysqlnd-ms-plugin-config-v2.trx-stickiness">transaction stickiness</link> + is enabled. Connection switches are not allowed for the duration of a + transaction. Changing the quality of service likely results on a different + set of servers qualifying for query execution, possibly making it + necessary to switch connections. Thus, the call is not allowed in + during an active transaction. The quality of server can, however, be + changed in between transactions. + </para> + </listitem> </itemizedlist> </para> <para> Modified: phpdoc/en/trunk/reference/mysqlnd_ms/functions/mysqlnd-ms-set-qos.xml =================================================================== --- phpdoc/en/trunk/reference/mysqlnd_ms/functions/mysqlnd-ms-set-qos.xml 2013-02-20 17:10:01 UTC (rev 329522) +++ phpdoc/en/trunk/reference/mysqlnd_ms/functions/mysqlnd-ms-set-qos.xml 2013-02-20 17:13:50 UTC (rev 329523) @@ -48,6 +48,12 @@ using <literal>master_on_write</literal>, which would continue using the master after the first write. </para> + <para> + Since 1.5.0 calls will fail when done in the middle of a transaction if + <link linkend="ini.mysqlnd-ms-plugin-config-v2.trx-stickiness">transaction stickiness</link> + is enabled and transaction boundaries have been detected. + properly. + </para> </refsect1> <refsect1 role="parameters"> @@ -93,7 +99,7 @@ <function>mysqlnd_ms_get_last_gtid</function>. If set, the plugin considers both master servers and asynchronous slaves for session consistency (read your writes). Otherwise, only masters are - used to achieve session consistency. A slave is considered up-to-date and + used to achieve session consistency. A slave is considered up-to-date and checked if it has already replicated the global transaction ID from <parameter>option_value</parameter>. Please note, searching appropriate slaves is an expensive and slow operation. Use the feature sparsely, if the