From 25b1bd57cae8fbcf7aa5c3fc4355229c2fe4c629 Mon Sep 17 00:00:00 2001 From: Ulf Wendel Date: Wed, 20 Feb 2013 10:41:24 +0000 Subject: [PATCH] Document BC break and bug fix on SQL hints and trx stickiness git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@329519 c90b9560-bf6c-de11-be94-00142212c4b1 --- reference/mysqlnd_ms/changes.xml | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/reference/mysqlnd_ms/changes.xml b/reference/mysqlnd_ms/changes.xml index e22b6bc1c8..8a76a0fb20 100644 --- a/reference/mysqlnd_ms/changes.xml +++ b/reference/mysqlnd_ms/changes.xml @@ -56,6 +56,29 @@ transaction monitoring had detected transaction boundaries properly. + + + BC break and bug fix. SQL hints enforcing the use of a specific + kind of server (MYSQLND_MS_MASTER_SWITCH, + MYSQLND_MS_SLAVE_SWITCH, + MYSQLND_MS_LAST_USED_SWITCH) are ignored for the + duration of a transaction of transaction stickiness is enabled and + transaction boundaries have been detected properly. + + + This is a change in behaviour. However, it is also a bug fix and a step + to align behaviour. If, in previous versions, transaction stickiness, + one of the above listed SQL hints and the quality of service filtering + 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. + + + Please note, transaction boundary detection continues to be based on API + call monitoring. SQL commands controlling transactions are not monitored. + +