Hi Richard,
There's nothing stopping you from saving XML from MartEditor then using
the upload option in MartEditor to reinstate it into another database,
as long as the target database shares exactly the same physical table
structure.
Yes, I had thought of doing it this way, but that means that
the user has to do it interactively. What I was interested in
was the possibility to do the same thing with a script. I
was hoping that there would be an undocumented feature
of MartShell, where I could just type "upload <filename.xml>"
and *pow* I now have the new XML in my database. Or
something like that.
However, due to the way the config system works it is not possibly to do
this on a running system without having to restart any applications
currently using it (and, in the case of the Perl API and
MartView/MartService, re-run the configuration step to update their
local copies of the XML).
That's fine, we would only need to do this for a release, where
it's normal to restart everything anyway.
Cheers,
David.
