BaseX-Talk December 2018

basex-talk@mailman.uni-konstanz.de

17 participants
17 discussions

Feature Request: Save untitled, open scripts when exiting GUI
by Andreas Mixich 30 Jul '20

30 Jul '20

SublimeText has this nifty feature, that it saves all open tabs, even if the have no representation on the filesystem, so one can continue exactly, where one has left off. I find myself often to have several, unnamed, XQueries open, to test this concept, to compose that function, etc. It would be nice, if one could simply shut off and have them reopened next time without naming a file and saving each item in question. -- Minden jót, all the best, Alles Gute, Andreas Mixich

2 6

Schema 1.1 validation and Xerces cta-full-xpath-checking?
by Zimmel, Daniel 15 Feb '19

15 Feb '19

Hi, is there any chance BaseX will support the cta-full-xpath-checking option (see https://xerces.apache.org/xerces2-j/features.html)? Without it, schema 1.1 validation is limited. I could not find any switches to configure Xerces features, but did find someone mentioning it from two years ago: https://www.mail-archive.com/basex-talk@mailman.uni-konstanz.de/msg08446.ht… Or have I missed something in the documentation? Regards, Daniel

3 5

Global locks
by Andy Bunce 11 Feb '19

11 Feb '19

Running the following in the GUI (8.6.5) ``` let $db:="BEP" return count(collection($db)) ``` The info windows shows $db is inlined Compiling: - inline $db_0 - pre-evaluate collection("BEP") to document-node() sequence - pre-evaluate count((db:open-pre("BEP",0), ...)) to xs:integer - simplify gflwor Optimized Query: 9193 All good. Submitting a job ``` let $q:='let $db:="BEP" return count(collection($db))' return jobs:eval($q,(),map{"cache":true()})!(jobs:wait(.),jobs:list-details(.)) ``` returns: <job id="job90" type="ScheduledXQuery" state="cached" user="admin" duration="PT0.007S" reads="(global)" writes="(none)">let $db:="BEP" return count(collection($db))</job> Note @reads="(global)" But ``` let $q:='count(collection("BEP"))' return jobs:eval($q,(),map{"cache":true()})!(jobs:wait(.),jobs:list-details(.)) ``` <job id="job92" type="ScheduledXQuery" state="cached" user="admin" duration="PT0.006S" reads="BEP" writes="(none)">count(collection("BEP"))</job> Note @reads="BEP" Is this correct and/or of any consequence? /Andy

2 8

many distinct namespaces
by Сергей Чесноков 24 Jan '19

24 Jan '19

Hi all, Is it possible to bypass the following restriction (I cannot change "ep_ins_med_q.xsd" (Central Bank xbrl scheme))?: BaseX 9.1 Command: CREATE DB bfo D:/portal/xbrl/CBR/final_1_3_1/Taxonomy_1_3_1/www.cbr.ru/xbrl/bfo/ Error: "D:/portal/xbrl/CBR/final_1_3_1/Taxonomy_1_3_1/www.cbr.ru/xbrl/bfo/rep/2018-03-31/ep/ep_ins_med_q.xsd""ep_ins_med_q.xsd" (Line 21): Too many distinct namespaces (limit: 256). Best regards, Sergei.

7 16

Scaling and Jsoniq
by Ben Pracht 02 Jan '19

02 Jan '19

Hi, I'm sorry if this was covered earlier, but I haven't seen it in a Google search. First, are there any support plans for scaling outwards? I know MarkLogic has splits clusters into multiple enodes and dnodes. But the idea is that there isn't one central bottleneck for requests. Second, I read about Jsoniq and was intrigued by it. It seemed like it supported JSON without requiring an XML intermediary. Having good JSON support would really help with frameworks like Angular or React. I really love Basex overall though and think it's underrated for what it can do. Regards, Ben

4 3

update:output() update:cache()
by Dieter Zanzinger 02 Jan '19

02 Jan '19

I do not exactly understand, for which purpose update:output() is meant. Does anybody have an example, where one can see, how it works? (There is no example in the docs.) (I am searching for a way, to run a update-expression on a database and give the altered nodes as result back to the restq-user in one query. The update:output() or update:cache() - expression sounded like they do something similar… At present, i am helping me with a copy/modify/return-solution and am giving back the altered result, before I actually write back the result-node of the previous to the db. But I am searching for a more intuitive way to get this result). Sincerly Dieter

2 1

Re: [basex-talk] 9.1.1: Relative path resolution fails with non-ascii characters
by Christian Grün 21 Dec '18

21 Dec '18

Hi Alex (cc to the list), This might be an OS-specific problem (I tried to reproduce the problem with Windows and Ubuntu, but I didn’t succeed). Which operating system are you using, and what’s the default encoding of your file system? > '../xqm/path:frequently used paths.xqm'; This is actually an invalid path in XQuery, as spaces should be encoded via %20. BaseX accepts it anyway, at least in version 9 (we might change that in future). Maybe you’ll generally encounter less issues if you use standard URI characters in your file paths. But as soon as I’ll manage to reproduce the encoding problem you encountered, I’ll be happy to have a closer look at it. Feel free to provide me with a minimal step-by-step procedure; maybe I missed something. Saludos, Christian On Fri, Dec 21, 2018 at 5:28 AM Alex R. Loayza <arx.inbox(a)gmail.com> wrote: > Hello Christian, > > I have encountered an issue in BaseX 9.1.1 after migrating from 8.5.3. It > seems to be a character encoding problem. > > In many queries, I import a module with a relative path: > > import module namespace path = 'http://myns' at '../xqm/path:frequently > used paths.xqm'; > > While this worked fine in 8.5.3, in 9.1.1 I get the following error > message: > > If I substitute the absolute path to the module for the relative path, > > import module namespace path = 'http://myns' at > '/home/arx/devWorks/otherProjects/almacén/procRep/xqy/xqm/path:frequently > used paths.xqm'; > > ...the import again succeeds. This tells me that the code resolving the > relative path in 9.1.1 is having problems with non-ascii characters: the > *é* in this case, which is changed to *?* in the resolved path. > > I see no way to fix this myself. Is this is a bug, or is there some > workaround? > > Cheers, > > Alex > > > --------------------------- > From: Christian Grün <christian.gruen(a)gmail.com> > <christian.gruen(a)gmail.com> > To:Alex R. Loayza > Cc:BaseX > Dec 20 at 3:36 AM > Hi Alex, > > All changes in the 9.0 storage layout are backward compatible. If you > update your database, it will be optimized incrementally. > > Breaking changes in BaseX will be documented explicitly. For example, if > you have written a lot of XQuery code, you may need to update some > BaseX-specific function calls. You will find those changes in the docs by > searching for "9.0" or "9.1". > > Hope this helps, > Christian >

1 0

possible basex 9.1.1 bug in java binding exception handling
by Mark McSweeny 21 Dec '18

21 Dec '18

Hello, I am seeing a possible bug during exception-handling while using Java binding in BaseX version 9.1.1. The problem can be illustrated by the following minimal working example query: Q{java.lang.String}new*java.lang.String(()) This is equivalent to the Java expression "new String(null)". "null" is not valid for this constructor so an exception is thrown. In version 9.1, I see the expected error: [XPTY0004] String.new(empty-sequence()): java.lang.NullPointerException. In version 9.1.1, I get message suggesting a potential bug along with a full stack trace: Improper use? Potential bug? Your feedback is welcome: Contact: basex-talk@... Version: BaseX 9.1.1 Java: Oracle Corporation, 1.8.0_92 OS: Windows 10, amd64 Stack Trace: java.lang.NullPointerException at org.basex.util.Util.className(Util.java:70) at org.basex.query.func.java.JavaEval.type(JavaEval.java:203) at org.basex.query.func.java.JavaEval.types(JavaEval.java:188) at org.basex.query.func.java.JavaEval.execError(JavaEval.java:149) at org.basex.query.func.java.DynJavaConstr.eval(DynJavaConstr.java:78) at org.basex.query.func.java.JavaCall.value(JavaCall.java:70) at org.basex.query.func.java.JavaCall.iter(JavaCall.java:63) at org.basex.query.scope.MainModule.iter(MainModule.java:118) at org.basex.query.QueryContext.iter(QueryContext.java:335) at org.basex.query.QueryContext.cache(QueryContext.java:613) at org.basex.query.QueryProcessor.cache(QueryProcessor.java:112) at org.basex.core.cmd.AQuery.query(AQuery.java:103) at org.basex.core.cmd.XQuery.run(XQuery.java:22) at org.basex.core.Command.run(Command.java:257) at org.basex.core.Command.execute(Command.java:93) at org.basex.gui.GUI.exec(GUI.java:429) at org.basex.gui.GUI.lambda$4(GUI.java:372) at java.lang.Thread.run(Thread.java:745) The stack trace suggests that the error is occurring while the system is assembling the error message. It generates a string describing the Java arguments: https://github.com/BaseXdb/basex/blob/9.1.1/basex-core/src/main/java/org/ba… ... but when it tries to determine the type of "null": https://github.com/BaseXdb/basex/blob/9.1.1/basex-core/src/main/java/org/ba… ... it incurs a NullPointerException while calling "null.getClass()": https://github.com/BaseXdb/basex/blob/9.1.1/basex-core/src/main/java/org/ba… I hope this report is helpful. Take care, Mark Mark McSweeny Development Team Lead t: 403-648-4602 + 4602 e: mark.mcsweeny(a)aucerna.com Learn more about Aucerna www.3esi-enersight.com/blog/palantir-solutions Confidentiality Notice: The information transmitted herein may contain confidential, proprietary and/or privileged material which belongs to Aucerna and is only for the intended addressee(s). Any unauthorized review, distribution or other use of this information is prohibited. Finally, the recipient should check this email and any attachments for the presence of viruses. The organization accepts no liability for any damage caused by any virus transmitted by this email. If you received this email in error, please contact us at (403) 270-3270 or by return email and delete this email and any copies immediately. v&7.11.1989&$

2 1

Re: [basex-talk] possible basex 9.1.1 bug in java binding exception handling
by Mark McSweeny 20 Dec '18

20 Dec '18

The character in the example query between "new" and "java" was meant to be the "middle dot character" (&#xB7), not an asterisk: Trying again... and hoping it gets through the various mailers :) Q{java.lang.String}new·java.lang.String(())

1 0

Migrating Data
by Alex R. Loayza 20 Dec '18

20 Dec '18

Hello, I want to upgrade from 8.5.3 to 9.1.1, but I'm unsure if the data format is compatible. In the changelog for 9.0, I find that regarding storage there has been the following change: "Improved database compression (short strings, whitespaces)" Does this mean that the old data format is incompatible? If so, how to migrate the data? Is there some documentation page detailing compatibility of data formats across BaseX versions? I'm been unable to find it. An upgrade guide would be a welcome addition to the docs! Best regards, Alex

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk December 2018