2014-06-06 03:52:09 Opened by Bjoern Kiesbye

Many server side errors occur because the XML Configuration has unexpected or missing values. A check of a caught error msg for :

"procedure "slony::config::"

Taken from:

invalid command name ""
while executing
"[[$cur_table_node getElementsByTagName "Key"] childNodes] nodeValue"
(procedure "slony::config::get::all_tables" line 14)
invoked from within
"slony::config::get::all_tables -slony_config_id $slony_config_id"


can trigger a automatic recreation of the XML configuration with values from the DB Configuration. After the recreation the code is likely to execute error less. For that to make sense all slony::config commands must be wrapped in a function which implements the catch block, checking of the error stack trace, and conditional re issuing of the command.