MySQL Proxy Scripting
1411
Attribute
Description
client.src.address
The IP address of the client (originating) TCP/IP port
client.src.port
The port of the client (originating) TCP/IP endpoint
server.scramble_buffer
The scramble buffer used to scramble the password
server.mysqld_version
The MySQL version number of the server
server.thread_id
The ID of the thread handling the connection to the current server
server.dst.name
The combined
address:port
for the backend server for the current
connection (i.e. the connection to the MySQL server)
server.dst.address
The address for the backend server
server.dst.port
The port for the backend server
server.src.name
The combined
address:port
for the TCP/IP endpoint used by the
Proxy to connect to the backend server
server.src.address
The address of the endpoint for the proxy-side connection to the
MySQL server
server.src.port
The port of the endpoint for the proxy-side connection to the MySQL
server
proxy.global.backends
The
proxy.global.backends
table is partially writable and contains an array of all the configured
backend servers and the server metadata (IP address, status, etc.). You can determine the array index
of the current connection using
proxy.connection["backend_ndx"]
which is the index into this
table of the backend server being used by the active connection.
The attributes for each entry within the
proxy.global.backends
table are shown in the following
table.
Attribute
Description
dst.name
The combined
address:port
of the backend server.
dst.address
The IP address of the backend server.
dst.port
The port of the backend server.
connected_clients
The number of clients currently connected.
state
The status of the backend server. See
Backend State/Type
Constants [1414]
.
type
The type of the backend server. You can use this to identify
whether the backed was configured as a standard read/write
backend, or a read-only backend. You can compare this value to the
proxy.BACKEND_TYPE_RW
and
proxy.BACKEND_TYPE_RO
.
proxy.queries
The
proxy.queries
object is a queue representing the list of queries to be sent to the server. The
queue is not populated automatically, but if you do not explicitly populate the queue, queries are
passed on to the backend server verbatim. Also, if you do not populate the query queue by hand, the
read_query_result()
function is not triggered.
The following functions are supported for populating the
proxy.queries
object.
Function
Description
append(id,packet,
[options])
Appends a query to the end of the query queue. The
id
is an integer
identifier that you can use to recognize the query results when they
are returned by the server. The packet should be a properly formatted
Содержание 5.0
Страница 1: ...MySQL 5 0 Reference Manual ...
Страница 18: ...xviii ...
Страница 60: ...40 ...
Страница 396: ...376 ...
Страница 578: ...558 ...
Страница 636: ...616 ...
Страница 844: ...824 ...
Страница 1234: ...1214 ...
Страница 1426: ...MySQL Proxy Scripting 1406 The following diagram shows an overview of the classes exposed by MySQL Proxy ...
Страница 1427: ...MySQL Proxy Scripting 1407 ...
Страница 1734: ...1714 ...
Страница 1752: ...1732 ...
Страница 1783: ...Configuring Connector ODBC 1763 ...
Страница 1793: ...Connector ODBC Examples 1773 ...
Страница 1839: ...Connector Net Installation 1819 2 You must choose the type of installation to perform ...
Страница 1842: ...Connector Net Installation 1822 5 Once the installation has been completed click Finish to exit the installer ...
Страница 1864: ...Connector Net Visual Studio Integration 1844 Figure 20 24 Debug Stepping Figure 20 25 Function Stepping 1 of 2 ...
Страница 2850: ...2830 ...
Страница 2854: ...2834 ...
Страница 2928: ...2908 ...
Страница 3000: ...2980 ...
Страница 3122: ...3102 ...
Страница 3126: ...3106 ...
Страница 3174: ...3154 ...
Страница 3232: ...3212 ...