Hi Fabrice,
I'm still hesitant to introduce more features to the command script syntax, as all of them will be BaseX-specific. But we could interpret all input as XQuery and execute the resulting XML as BaseX commands. This way, we could write things like..
<commands>{ for $n in 1 to 10 return <create-db name='db{ $n }'/> }</commands>
What do you think? Christian
On Mon, Apr 14, 2014 at 11:44 AM, Christian Grün christian.gruen@gmail.com wrote:
Hi Fabrice,
I've recorded your feature request in a new issue:
https://github.com/BaseXdb/basex/issues/929
Christian
On Fri, Apr 11, 2014 at 3:57 PM, Fabrice Etanchaud fetanchaud@questel.com wrote:
Dear all,
Currently, in order to obtain tailored command scripts, I found the following solution :
A template test.bxs file :
<commands>
<open name='${DBNAME}'/>
<xquery>
<![CDATA[ (/document)[1] ]]></xquery>
<close/>
</commands>
A bash script test.sh:
#!/bin/bash
DBNAME=de-dpma-u-meta
eval "cat <<EOF
$(<$1)
EOF
" | basex -c-
And then call :
./test.sh test.bxs
Could it be possible for the variable bindings to be applied also to script commands,
So basex -bDBNAME=de-dpma-u-meta test.bxs
does the whole job ?
that would work also for commands' sequences like :
<set option='bindings'>.....
<execute> or <run>
Merci !
Best regards,
Fabrice