MySQL Proxy Release Notes  /  Changes in MySQL Proxy 0.7.0 (Not Released)

Changes in MySQL Proxy 0.7.0 (Not Released)

Functionality Added or Changed

  • Support for using a configuration file, in addition to the command-line options, has been added. To specify such a file, use the --defaults-file=file_name command-line option. See MySQL Proxy Command Options. (Bug #30206)

  • A number of the internal structures developed for use with Lua scripts that work with MySQL Proxy have been updated and harmonized to make their meaning and contents easier to use and consistent across multiple locations.

    • The address information has been updated. Instead of a combined ip:port structure that you had to parse to extract the individual information, you can now access that information directly. For example, instead of structures providing a single .address item, you now have these items: name (the combined ip:port), address (the IP address), and port (port number). In addition, all addresses now supply both the src (source) and dst (destination) socket information for both ends of connections.

      Some familiar structures have been updated to accommodate this information:

      • proxy.connection.client.address is

      • proxy.connection.server.address is

    • proxy.backends is now in The .address field of each backend is an address-object as described earlier. For example, proxy.backends[1].address is[1]

    • The read_auth() and read_handshake() functions no longer receive an auth parameter. Instead, all the data is available in the connection tables.

      In read_handshake(), you access the information through the global proxy.connection table:

      0.6 0.7
      auth.thread_id proxy.connection.server.thread_id
      auth.mysqld_version proxy.connection.server.mysqld_version
      auth.scramble proxy.connection.server.scramble_buffer

      In read_auth(), you can use the following:

      0.6 0.7
      auth.username proxy.connection.client.username
      auth.password proxy.connection.client.scrambled_password
      auth.default_db proxy.connection.client.default_db
    • In the proxy.queries:append() function, a third parameter is an (optional) table with options specific to the this packet. Specifically, if you want to have access to the result set in the read_query_result() hook, you must set the resultset_is_needed flag:

      proxy.queries:append( 1, ..., { resultset_is_needed = true } )

      For more information, see proxy.queries.

    • proxy.backends is now in

Bugs Fixed

  • Security Enhancement: Accessing MySQL Proxy using a client or backend from earlier than MySQL 4.1 resulted in Proxy aborting with an assertion. This is because Proxy supports only MySQL 4.1 or higher. Proxy now reports a fault. (Bug #31419)

  • MySQL Proxy was configured with the LUA_PATH and LUA_CPATH directory locations according to the build host rather than the execution host. In addition, during installation, certain Lua source files could be installed into the incorrect locations. (Bug #44877, Bug #44497)

  • Using MySQL Proxy with very large return data sets from queries could cause a crash, with or without manipulation of the data set within the Lua engine. (Bug #39332)

  • MySQL Proxy terminated if a submitted packet was smaller than expected by the protocol. (Bug #36743)

  • When using MySQL Proxy in a master-master replication scenario, Proxy failed to identify failure in one of the replication masters and did not redirect connections to the other master. (Bug #35295)

Download these Release Notes
PDF (US Ltr) - 64.3Kb
PDF (A4) - 65.1Kb
EPUB - 30.3Kb