Fix opening a new cdb with ConfigCDBAccessSvc
This only affects the case where ConfigCDBAccessSvc(File='x.cdb', Mode='ReadWrite')
is used and x.cdb
does not exist. The fix is only applicable to 2018-patches and master.
We should perhaps ensure the validity of the cdb
object closer to where it's used, e.g. in the icdb
class' methods. I'm not sure if an assert
is enough or we need to do more.
/cc @graven