In my basex/.basex file I have this local option:
# Local Options CREATEFILTER=*.xml,*.dita,*.ditamap
I have three BaseX instances running.
And in the DBA panel for an instance not running on the default port (i.e., on port 10894) I see this in the Local Options column:
CREATEFILTER *.xml,*.dita,*.ditamap SKIPCORRUPT ✓
However, if I do this from the Query console of that same server:
db:create(‘mydatabase’, ‘/path/to/docs’)
The resulting database only reflects .xml files, not .dita or .ditamap files.
I’m wondering if this is a bug in how CREATEFILTER is being applied or my misunderstanding of the implications for CREATEFILTER?
This is running 9.6.4 on Centos.
If I specify createfilter directly on the db:create() call then of course it works as expected.
Cheers,
E. _____________________________________________ Eliot Kimber Sr Staff Content Engineer O: 512 554 9368 M: 512 554 9368 servicenow.comhttps://www.servicenow.com LinkedInhttps://www.linkedin.com/company/servicenow | Twitterhttps://twitter.com/servicenow | YouTubehttps://www.youtube.com/user/servicenowinc | Facebookhttps://www.facebook.com/servicenow
Hi Eliot,
I was surprised to see your observation leading me back to an adjustment made in 2014. Back then, global parsing options erroneously influenced the behavior of fn:doc. The global value of the CREATEFILTER, among others, is now considered when using db:create. See [1] for the whole picture and [2] for a new snapshot.
Cheers, Christian
[1] https://github.com/BaseXdb/basex/issues/2072 [2] https://files.basex.org/releases/latest/
On Sat, Feb 26, 2022 at 3:05 PM Eliot Kimber eliot.kimber@servicenow.com wrote:
In my basex/.basex file I have this local option:
# Local Options
CREATEFILTER=*.xml,*.dita,*.ditamap
I have three BaseX instances running.
And in the DBA panel for an instance not running on the default port (i.e., on port 10894) I see this in the Local Options column:
*CREATEFILTER*
*.xml,*.dita,*.ditamap
*SKIPCORRUPT*
✓
However, if I do this from the Query console of that same server:
db:create(‘mydatabase’, ‘/path/to/docs’)
The resulting database only reflects .xml files, not .dita or .ditamap files.
I’m wondering if this is a bug in how CREATEFILTER is being applied or my misunderstanding of the implications for CREATEFILTER?
This is running 9.6.4 on Centos.
If I specify createfilter directly on the db:create() call then of course it works as expected.
Cheers,
E.
*Eliot Kimber*
Sr Staff Content Engineer
O: 512 554 9368
M: 512 554 9368
servicenow.com https://www.servicenow.com
LinkedIn https://www.linkedin.com/company/servicenow | Twitter https://twitter.com/servicenow | YouTube https://www.youtube.com/user/servicenowinc | Facebook https://www.facebook.com/servicenow
Thanks for fixing it—glad to know it wasn’t just me 😊
Cheers,
E.
_____________________________________________ Eliot Kimber Sr Staff Content Engineer O: 512 554 9368 M: 512 554 9368 servicenow.comhttps://www.servicenow.com LinkedInhttps://www.linkedin.com/company/servicenow | Twitterhttps://twitter.com/servicenow | YouTubehttps://www.youtube.com/user/servicenowinc | Facebookhttps://www.facebook.com/servicenow
From: Christian Grün christian.gruen@gmail.com Date: Monday, February 28, 2022 at 9:24 AM To: Eliot Kimber eliot.kimber@servicenow.com Cc: basex-talk@mailman.uni-konstanz.de basex-talk@mailman.uni-konstanz.de Subject: Re: [basex-talk] CREATEFILTER Setting Not Being Applied [External Email]
Hi Eliot,
I was surprised to see your observation leading me back to an adjustment made in 2014. Back then, global parsing options erroneously influenced the behavior of fn:doc. The global value of the CREATEFILTER, among others, is now considered when using db:create. See [1] for the whole picture and [2] for a new snapshot.
Cheers, Christian
[1] https://github.com/BaseXdb/basex/issues/2072https://urldefense.com/v3/__https:/github.com/BaseXdb/basex/issues/2072__;!!N4vogdjhuJM!RG28s11PwUaBYEp5KOVE7ZHiZEyX59rxlvpkoEsxjtl51-KzPEMXlGnU4tAf-4grq3aEpg$ [2] https://files.basex.org/releases/latest/https://urldefense.com/v3/__https:/files.basex.org/releases/latest/__;!!N4vogdjhuJM!RG28s11PwUaBYEp5KOVE7ZHiZEyX59rxlvpkoEsxjtl51-KzPEMXlGnU4tAf-4gjkX1iZA$
On Sat, Feb 26, 2022 at 3:05 PM Eliot Kimber <eliot.kimber@servicenow.commailto:eliot.kimber@servicenow.com> wrote: In my basex/.basex file I have this local option:
# Local Options CREATEFILTER=*.xml,*.dita,*.ditamap
I have three BaseX instances running.
And in the DBA panel for an instance not running on the default port (i.e., on port 10894) I see this in the Local Options column:
CREATEFILTER *.xml,*.dita,*.ditamap SKIPCORRUPT ✓
However, if I do this from the Query console of that same server:
db:create(‘mydatabase’, ‘/path/to/docs’)
The resulting database only reflects .xml files, not .dita or .ditamap files.
I’m wondering if this is a bug in how CREATEFILTER is being applied or my misunderstanding of the implications for CREATEFILTER?
This is running 9.6.4 on Centos.
If I specify createfilter directly on the db:create() call then of course it works as expected.
Cheers,
E. _____________________________________________ Eliot Kimber Sr Staff Content Engineer O: 512 554 9368 M: 512 554 9368 servicenow.comhttps://www.servicenow.com LinkedInhttps://urldefense.com/v3/__https:/www.linkedin.com/company/servicenow__;!!N4vogdjhuJM!RG28s11PwUaBYEp5KOVE7ZHiZEyX59rxlvpkoEsxjtl51-KzPEMXlGnU4tAf-4jHKPZvmw$ | Twitterhttps://urldefense.com/v3/__https:/twitter.com/servicenow__;!!N4vogdjhuJM!RG28s11PwUaBYEp5KOVE7ZHiZEyX59rxlvpkoEsxjtl51-KzPEMXlGnU4tAf-4i_xBtN3Q$ | YouTubehttps://urldefense.com/v3/__https:/www.youtube.com/user/servicenowinc__;!!N4vogdjhuJM!RG28s11PwUaBYEp5KOVE7ZHiZEyX59rxlvpkoEsxjtl51-KzPEMXlGnU4tAf-4iiSK5jrw$ | Facebookhttps://urldefense.com/v3/__https:/www.facebook.com/servicenow__;!!N4vogdjhuJM!RG28s11PwUaBYEp5KOVE7ZHiZEyX59rxlvpkoEsxjtl51-KzPEMXlGnU4tAf-4hNB0Xwzg$
Greetings!
What I thought would be a simple task has turned out to not be so simple.
I wrote:
SET CHOP false SET EXPORTER indent=no,omit-xml-declaration=no SET BINDINGS $ndb=Ruth CREATE DB $ndb ./sources/Ruth.xml
In BaseX 9.6.4, and when testing it I got this result:
CHOP: false EXPORTER: indent=no,omit-xml-declaration=no BINDINGS: $ndb=Ruth Database '$ndb' created in 544.5 ms.
What? Why isn't the mapping of Ruth to the variable $ndb effective in the bxs file?
Moreover, there are query files that follow in the bxs file that I want to have resolve $ndb to Ruth (the desired name of the database).
1) How should I declare a variable in a bxs file?
2) In such a way that it carries over to following xquery files?
BTW, I've seen this posting by Christian: https://stackoverflow.com/questions/28018354/how-to-run-a-xquery-with-xml-fi...
but it doesn't seem to be working for me.
What am I missing?
Thanks!
Patrick https://twitter.com/servicenow--
Patrick Durusau patrick@durusau.net Technical Advisory Board, OASIS (TAB) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau
basex-talk@mailman.uni-konstanz.de
-
Christian Grün -
Eliot Kimber -
Patrick Durusau