Hi Fabrice,
due to the ambiguities that would be caused by executing all command
scripts as XQuery, we decided to close Issue 929 [1]. However, some
good news: if you experience a little with the existing features of
BaseX, you will see that command scripts can easily be created via
XQuery and exe
Hi Fabrice,
> In order to allow for parameters, do you think one could declare external
> variables before the commands element ?
> Is it to say that a command file could be any xquery script generateding xml ?
Exactly; your command file will be evaluated the same as any other
XQuery expression.
--
De : Christian Grün [mailto:christian.gr...@gmail.com]
Envoyé : dimanche 4 mai 2014 22:08
À : Fabrice Etanchaud
Cc : basex-talk@mailman.uni-konstanz.de
Objet : Re: [basex-talk] apply variable bindings to command scripts
Hi Fabrice,
I'm still hesitant to introduce more features to the command script
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..
{
for $n in 1 to 10
return
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
wrote:
> Dear all,
>
>
>
> Currently, in order to obtain tailored command scripts, I found the
> following solution :
>
>
Dear all,
Currently, in order to obtain tailored command scripts, I found the following
solution :
A template test.bxs file :
A bash script test.sh:
#!/bin/bash
DBNAME=de-dpma-u-meta
eval "cat <.
or
Merci !
Best regards,
Fabrice
6 matches
Mail list logo
