Adding procedure that handles the logic of setting a configuration setting
Adding README for the set_sys_config procedure
Rename set_sys_config() to sys_get_config() and do not check whether the corresponding user variable already is set. There is little benefit checking whether the user variable is already set as sys_get_config() may be used from functions, e.g. format_statement() that in some cases is called for each row in a result set (see e.g. the processlist view) and it'll anyway be necessary to check whether the user variable is set in the parent program to avoid an additional unnecessary procedure call for each invokation. Removing the check for whether the user variable has already been set also greatly simplifies the sys_get_config() procedure.
Convert sys_get_config() to a function and return the value for the configuration option. This is needed as it can otherwise not be used by functions as dynamic SQL is not allowed in functions. This also removes the need to have a user variable in sys_get_config() for storing the value as that was only required due to the use of a prepared statement.
Change format_statement() to use the new sys_get_config() function
Change so the format_statement sys config option for the max length of a formatted statement is sys.statement_truncate_len instead of statement_truncate_len
Don't use the sys "namespace" in the option names stored in sys.sys_config
More detailed description and an extra example for sys_get_config()
The 5.6 host_summary and x$host_summary views and the 5.6 host_summary view incorrectly had the column with COUNT(DISTINCT accounts.user) named unique_hosts instead of unique_users
Merge pull request #41 from JesperWisborgKrogh/dev/20141210_host_summary

The 5.6 host_summary and x$host_summary views and the 5.6 host_summary v...
Merge pull request #39 from JesperWisborgKrogh/dev/20141207_get_sys_config

Dev/20141207 get sys config