Bug #46313 no backends address
Submitted: 20 Jul 2009 16:22 Modified: 23 Jul 2009 14:33
Reporter: savage savage Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Proxy Severity:S3 (Non-critical)
Version:0.7.2 OS:Any (no backends address)
Assigned to: CPU Architecture:Any
Tags: regression
Triage: Needs Triage: D2 (Serious)

[20 Jul 2009 16:22] savage savage
Description:
Hello,

backends[...].address does not seem to be available in the lua. 
I can find only backends[..].dst which is in hex and this way I can not choose my backend based on the address.
Other than that.. is there any option to add/remove or modify backend addresses on read_auth() ? .. currently I can see that only uuid and state changes are valid.. ?
Also.. I would like to ask, is there any particular reason why the documentation on mysql.com regarding the mysql-proxy is so out of date ?

How to repeat:
1. create a lua script
2. try to find backends[...].address that is not nil
[20 Jul 2009 18:43] Sveta Smirnova
Thank you for the report.

Verified as described using current bzr tree.
[23 Jul 2009 14:32] Enterprise Tools JIRA Robot
Jan Kneschke writes: 
http://forge.mysql.com/wiki/MySQL_Proxy_0.6_to_0.7 documents the changes. 

->address is now ->dst.name