When writing out a geometry table using something like this
python $HDDS_HOME/ccdb/hdds2ccdb.py -r 131001 get Target_HDDS.xml > Target_131001.xml
this line causes the explanatory text to be written at the top of the output file. This is a minor pain because the resulting xml file cannot be reused in ccdb until the explanatory text at the top of the file has been removed.
When using 'set' to load in a new table, this line is printed, and it gives the appearance that the user has made a mistake.
I don't think it is useful to print out these str1 variables every time. They would be more useful in the exceptions, when something went wrong.
When writing out a geometry table using something like this
python $HDDS_HOME/ccdb/hdds2ccdb.py -r 131001 get Target_HDDS.xml > Target_131001.xmlthis line causes the explanatory text to be written at the top of the output file. This is a minor pain because the resulting xml file cannot be reused in ccdb until the explanatory text at the top of the file has been removed.
When using 'set' to load in a new table, this line is printed, and it gives the appearance that the user has made a mistake.
I don't think it is useful to print out these str1 variables every time. They would be more useful in the exceptions, when something went wrong.