Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

mysqlnd_ms_fabric_select_global(3) [php man page]

MYSQLND_MS_FABRIC_SELECT_GLOBAL(3)					 1					MYSQLND_MS_FABRIC_SELECT_GLOBAL(3)

mysqlnd_ms_fabric_select_global - Switch to global sharding server for a given table

SYNOPSIS
array mysqlnd_ms_fabric_select_global (mixed $connection, mixed $table_name) DESCRIPTION
Warning This function is currently not documented; only its argument list is available. MySQL Fabric related. Switch the connection to the nodes handling global sharding queries for the given table name. PARAMETERS
o $connection - A MySQL connection handle obtained from any of the connect functions of the mysqli, mysql or PDO_MYSQL extensions. o $table_name - The table name to ask Fabric about. RETURN VALUES
FALSE on error. Otherwise, TRUE NOTES
Note mysqlnd_ms_fabric_select_global(3) requires PECL mysqlnd_ms >> 1.6.0. PHP Documentation Group MYSQLND_MS_FABRIC_SELECT_GLOBAL(3)

Check Out this Related Man Page

MYSQLND_MS_GET_LAST_USED_CONNECTION(3)					 1				    MYSQLND_MS_GET_LAST_USED_CONNECTION(3)

mysqlnd_ms_get_last_used_connection - Returns an array which describes the last used connection

SYNOPSIS
array mysqlnd_ms_get_last_used_connection (mixed $connection) DESCRIPTION
Returns an array which describes the last used connection from the plugins connection pool currently pointed to by the user connection handle. If using the plugin, a user connection handle represents a pool of database connections. It is not possible to tell from the user connection handles properties to which database server from the pool the user connection handle points. The function can be used to debug or monitor PECL mysqlnd_ms. PARAMETERS
o $connection - A MySQL connection handle obtained from any of the connect functions of the mysqli, mysql or PDO_MYSQL extensions. RETURN VALUES
FALSE on error. Otherwise, an array which describes the connection used to execute the last statement on. Array which describes the connection. +---------------+--------------------------------------+---+ | Property | | | | | | | | | Description | | | | | | | | Version | | | | | | +---------------+--------------------------------------+---+ | | | | | scheme | | | | | | | | | Connection scheme. Either | | | | tcp://host:port or | | | | unix://host:socket. If you want to | | | | distinguish connections from each | | | | other use a combination of scheme | | | | and thread_id as a unique key. Nei- | | | | ther scheme nor thread_id alone are | | | | sufficient to distinguish two con- | | | | nections from each other. Two | | | | servers may assign the same | | | | thread_id to two different connec- | | | | tions. Thus, connections in the pool | | | | may have the same thread_id. Also, | | | | do not rely on uniqueness of scheme | | | | in a pool. Your QA engineers may use | | | | the same MySQL server instance for | | | | two distinct logical roles and add | | | | it multiple times to the pool. This | | | | hack is used, for example, in the | | | | test suite. | | | | | | | | Since 1.1.0. | | | | | | | | | | | host | | | | | | | | | Database server host used with the | | | | connection. The host is only set | | | | with TCP/IP connections. It is empty | | | | with Unix domain or Windows named | | | | pipe connections, | | | | | | | | Since 1.1.0. | | | | | | | | | | | host_info | | | | | | | | | A character string representing the | | | | server hostname and the connection | | | | type. | | | | | | | | Since 1.1.2. | | | | | | | | | | | port | | | | | | | | | Database server port used with the | | | | connection. | | | | | | | | Since 1.1.0. | | | | | | | | | | |socket_or_pipe | | | | | | | | | Unix domain socket or Windows named | | | | pipe used with the connection. The | | | | value is empty for TCP/IP connec- | | | | tions. | | | | | | | | Since 1.1.2. | | | | | | | | | | | thread_id | | | | | | | | | Connection thread id. | | | | | | | | Since 1.1.0. | | | | | | | | | | | last_message | | | | | | | | | Info message obtained from the | | | | MySQL C API function mysql_info(). | | | | Please, see mysqli_info(3) for a | | | | description. | | | | | | | | Since 1.1.0. | | | | | | | | | | | errno | | | | | | | | | Error code. | | | | | | | | Since 1.1.0. | | | | | | | | | | | error | | | | | | | | | Error message. | | | | | | | | Since 1.1.0. | | | | | | | | | | | sqlstate | | | | | | | | | Error SQLstate code. | | | | | | | | Since 1.1.0. | | | | | | +---------------+--------------------------------------+---+ NOTES
Note mysqlnd_ms_get_last_used_connection(3) requires PHP >= 5.4.0 and PECL mysqlnd_ms >> 1.1.0. Internally, it is using a mysqlnd library C call not available with PHP 5.3. EXAMPLES
The example assumes that myapp refers to a plugin configuration file section and represents a connection pool. Example #1 mysqlnd_ms_get_last_used_connection(3) example <?php $link = new mysqli("myapp", "user", "password", "database"); $res = $link->query("SELECT 1 FROM DUAL"); var_dump(mysqlnd_ms_get_last_used_connection($link)); ?> The above example will output: array(10) { ["scheme"]=> string(22) "unix:///tmp/mysql.sock" ["host_info"]=> string(25) "Localhost via UNIX socket" ["host"]=> string(0) "" ["port"]=> int(3306) ["socket_or_pipe"]=> string(15) "/tmp/mysql.sock" ["thread_id"]=> int(46253) ["last_message"]=> string(0) "" ["errno"]=> int(0) ["error"]=> string(0) "" ["sqlstate"]=> string(5) "00000" } PHP Documentation Group MYSQLND_MS_GET_LAST_USED_CONNECTION(3)
Man Page