BaseX-Talk March 2022

basex-talk@mailman.uni-konstanz.de

29 participants
35 discussions

validate:xsd-info agains more than one schema
by Arantza Etxebarria Pablo 04 Mar '22

04 Mar '22

Dear Community, We have been trying to validate a file using the function *validate:xsd-info*($input as item(), $schema as item()?) as xs:string* against several different schemas and, we don't know how to send the parameter “schema” with more than one schema for this function. We have tried to declare the variable *schema *like this : let $schema:= " http://inspire.ec.europa.eu/schemas/bu-base/4.0/BuildingsBase.xsd http://schemas.opengis.net/gml/3.2.1/gml.xsd" But it returns this error message: XML document 'example.gml': -1:-1: schema_reference.4: Failed to read schema document ' http://inspire.ec.europa.eu/schemas/bu-base/4.0/BuildingsBase.xsd http://schemas.opengis.net/gml/3.2.1/gml.xsd' , because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. I have tried this function when no schema is given and it takes the contain of schemaLocation attribute, and in this case, is able to validate more than one schema. But I need to pass the schemas through a variable Could any of you point us in the right direction? Thanks -- *Arantza Etxebarria *

3 2

Re: [basex-talk] feature request: opening database at arbitrary file path
by Eric Levy 03 Mar '22

03 Mar '22

On Tue, 2022-02-22 at 23:10 +0100, Christian Grün wrote: > > The other contributor's comments were deeply rooted in particular > > assumptions that stood in stark contrast to the scenario I had > > described. > > It always depends on the way you interpret others’ comments. But > we're getting circular again (there must be a reason for it ;). > > > To me, "embedded" and "standalone" carry the same > > implication in the context of a database > > I see. With standalone, we want to indicate that the application > stands “on its own” and needs no external accessors. In contrast, > something that's embedded is fully dependant on other applications. > > In other words, if we use BaseX embedded, we import it as Java > library. If we use it as standalone processor, we access it > externally, similar to other installed applications and along with > all their idiosyncrasies. > > Would Java be an option for you? I understand the distinction. It seems the issues I originally raised would be the same in both cases. The difference is whether the application would be built as a collection of scripts versus a full Java application. I had planned to begin with Bash scripts calling the command-line database application, and then migrate to a more integrated application model (e.g. Java application using a library) only if required by the evolving needs. Frankly, I would hope to avoid the latter for the foreseeable future, as both the overall application complexity and maintenance resources are rather limited. However, as I explained, the overriding concern is whether the databases may be maintained inside of projects' folders without any dependency on resources elsewhere on the file system.

3 11

How Best to Determine What BaseX Is Doing When It Pegs the Processor?
by Eliot Kimber 03 Mar '22

03 Mar '22

I have a RESTXQ page that makes a query call to construct a report and then displays it. When I run this page something is triggering BaseX to peg the processor and it basically never returns from whatever it is doing. Using proc:dump() I can see that the call to construct the report runs and returns the expected value—this takes about 3 seconds, and then the page never returns and top shows that the java process for the BaseX HTTP server is pegged at 100%. The behavior is consistent so I know it must be something I’m doing or the effect of some configuration setting I have but no idea what might be going on. I get the behavior both on my development machine and on my production server, so it must be something in my code or some reproducible issue with the databases I’m managing. I’ve tried connecting the BaseX HTTP server to the Eclipse debugger, which works, but I’m not sure where I should be focusing my attention in the code. Turning on the -d flag isn’t that helpful either as the log is flooded with exceptions from BaseX trying to load Java classes for my XQuery modules, which swamps any more detailed debugging log messages and what messages I see appear to be entirely about the HTTP interaction, not what’s happening in the core BaseX server. Is there a particular place in the code I can focus on in the interactive debugger that would be a likely source of the behavior or another debugging technique I haven’t considered? Thanks, 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>

2 4

Re: [basex-talk] Declaring a variable in bxs that carries over to called xquery scripts
by ETANCHAUD Fabrice 02 Mar '22

02 Mar '22

Hi Patrick, I don't think bxs scripts have something like variables (but I may have missed the point with all the work BaseX team achieves). Bindings are way to parametrize XQuery scripts, and you can indeed set external variables' value in bxs, or on command line. Best regards, Fabrice Here are a few examples : https://docs.basex.org/wiki/Options#BINDINGS Options - BaseX Documentation<https://docs.basex.org/wiki/Options#BINDINGS> This page is linked from the Getting Started Section.. The options listed on this page influence the way how database commands are executed and XQuery expressions are evaluated. Two kinds of options exist: Global Options are valid for all BaseX instances in the same JVM. This is particularly relevant if you are working with the client/server architecture. docs.basex.org https://docs.basex.org/wiki/Command-Line_Options Command-Line Options - BaseX Documentation<https://docs.basex.org/wiki/Command-Line_Options> Standalone []. The following options are available for the standalone Command-Line Client: $ basex -h BaseX [Standalone] Usage: basex [-bcdiIoqrRstuvVwxz] [input] [input] XQuery or command file, or query string -b<args> Bind external query variables -c<input> Execute commands from file or string -d Toggle debugging output -i<input> Bind file or database to context -I<input> Bind input string ... docs.basex.org ________________________________ De: BaseX-Talk de la part de Patrick Durusau Envoyé: Mercredi 02 mars 2022 01:38 À: basex-talk(a)mailman.uni-konstanz.de Objet: [basex-talk] Declaring a variable in bxs that carries over to called xquery scripts 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-f… but it doesn't seem to be working for me. What am I missing? Thanks! Patrick <https://twitter.com/servicenow>-- Patrick Durusau patrick(a)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

1 0

CREATEFILTER Setting Not Being Applied
by Eliot Kimber 01 Mar '22

01 Mar '22

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>

3 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk March 2022