BaseX-Talk February 2015

basex-talk@mailman.uni-konstanz.de

38 participants
63 discussions

following::* is 100x slower than preceding::*
by Gioele Barabucci 18 Feb '15

18 Feb '15

Hello, I have noticed that this query using the "following" axes //*[@xml:id = "lemma-aMSa"] /following::*[self::tei:entry or self::tei:re] [position() <= 3] is much slower than the same query with the "preceding" axes //*[@xml:id = "lemma-aMSa"] /preceding::*[self::tei:entry or self::tei:re] [position() <= 3] The query that uses "preceding" takes about 2.5 ms to execute, while the one using "following" takes about 250 ms: it is 100 times slower. Why this discrepancy between these two queries? I can provide the base XML file (19MB) on request. Also, I also get a warning about «'following::*[(self::tei:entry or self::tei:re)][(fn:position() <= 3)]' will never yield results.» but that is obviously false, as it yields exactly the 3 results I expect. Regards, -- Gioele Barabucci <gioele(a)svario.it>

4 11

BaseX in maven
by Wendell Piez 18 Feb '15

18 Feb '15

BaseX friends, If I run BaseX from Maven, do I always get to use the latest BaseX? Do I have to do anything special to set up BaseX in Maven to use SaxonHE instead of Xalan for xslt:transform()? (I have Saxon9he.jar in my BaseX lib.) Thanks! Wendell -- Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic publishing Eat Your Vegetables _____oo_________o_o___ooooo____ooooooo_^

4 26

Re: [basex-talk] BaseX-Talk Digest, Vol 62, Issue 31
by Jothivel S 17 Feb '15

17 Feb '15

Hi, I am new to BaseX and using version of 7.6 and I don't know where to post my questions. I have two questions as follows 1. When a database is created under the folder BaseXData, there were 9 files exist. Could you please share the details of eash file in the database. 2. Also, when I replace the content(same) in the database instead of droping and recreating, the database size is getting increased. Could you please explain why this is happened even the same data were replaced. 3. Is there any way to avoid the item #2 with using replace option(not recreating) Thanks,Jothivel On Saturday, 14 February 2015 4:30 PM, "basex-talk-request(a)mailman.uni-konstanz.de" <basex-talk-request(a)mailman.uni-konstanz.de> wrote: Send BaseX-Talk mailing list submissions to basex-talk(a)mailman.uni-konstanz.de To subscribe or unsubscribe via the World Wide Web, visit https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk or, via email, send a message with subject or body 'help' to basex-talk-request(a)mailman.uni-konstanz.de You can reach the person managing the list at basex-talk-owner(a)mailman.uni-konstanz.de When replying, please edit your Subject line so it is more specific than "Re: Contents of BaseX-Talk digest..." Today's Topics: 1. Re: BaseX in maven (Marc van Grootel) ---------------------------------------------------------------------- Message: 1 Date: Fri, 13 Feb 2015 22:27:13 +0100 From: Marc van Grootel <marc.van.grootel(a)gmail.com> To: BaseX <basex-talk(a)mailman.uni-konstanz.de> Subject: Re: [basex-talk] BaseX in maven Message-ID: <CA+bQNCv4MiNqG5m7iFN65bMU2gQO+15pqWW10KwZuHhggNzejQ(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Hi, I've created a simple starter build script for BaseX 8.0 with Gradle and Saxon 9.6. See https://github.com/xokomola/basex-gradle-starter Not a full-fledged build script yet but does illustrate how to set things up. Just follow the one-step installation instruction and you should be good to go ;-) Feedback welcome. Cheers, --Marc On Sun, Jan 18, 2015 at 10:29 PM, Wendell Piez <wapiez(a)wendellpiez.com> wrote: > BaseX friends, > > If I run BaseX from Maven, do I always get to use the latest BaseX? > > Do I have to do anything special to set up BaseX in Maven to use > SaxonHE instead of Xalan for xslt:transform()? (I have Saxon9he.jar in > my BaseX lib.) > > Thanks! Wendell > > > -- > Wendell Piez | http://www.wendellpiez.com > XML | XSLT | electronic publishing > Eat Your Vegetables > _____oo_________o_o___ooooo____ooooooo_^ -- --Marc End of BaseX-Talk Digest, Vol 62, Issue 31 ******************************************

2 3

test if a namespace prefix is declared
by Emmanuel Chateau 11 Feb '15

11 Feb '15

We wanna test if a function exists with fn:function-lookup As fn:function-lookup only takes QNames, in some cases the namespace isn’t declared. So unsurprisingly, we get an error FONS0004 No namespace declared for prefix ‘……’ Is there any way to test if the namespace is declared first ? Thanks a lot, and best regards ! Emmanuel

2 5

Basex 8.0: white-spaces left after delete node?
by Hondros, Constantine (ELS-AMS) 11 Feb '15

11 Feb '15

Hi all, Using Basex 8.0, I notice a difference in behaviour compared to Basex 7.82 that I thought worth mentioning. After creating a 5 GB db, then pruning it down to roughly 2GB using Xquery 'delete node', and after running db:optimize, in the GUI Result window I see vaaaast areas of white-space left over, presumably from where the nodes were deleted. Hundreds of screenfulls, actually. Is this to do with the 'adaptive serialisation' that is now the default? Any options to use to prevent it? (it's not a huge problem, just midly annoying since with this particular DB I get a blank screen whenever I hit the 'Home' button in the GUI). TIA, Constantine ________________________________ Elsevier B.V. Registered Office: Radarweg 29, 1043 NX Amsterdam, The Netherlands, Registration No. 33156677, Registered in The Netherlands.

2 1

Re: [basex-talk] duplicate keys, because of missing commit
by Lukas Kircher 10 Feb '15

10 Feb '15

Hi Christoph, I’m forwarding my answer (including yours) to the mailing list, as I think it is valuable input. I totally agree that the ‘equivalency' XQuery/transaction is very limiting. It sometimes leads to weird constructs trying to bypass the limitation. Quite often though the limitation is actually useful, as it forces you to re-write your query in a way that it fits a single transaction. Within a single transaction the compiler then has a lot more room for optimization etc.. I’m not defending our current approach here - there are cases where it causes real pain and affects overall application design. But I also think that, more often then not, a functional programming approach also solves the issue including all the benefits. After all, the concept of the XQuery Update Facility is true to the functional nature of XQuery, where variables are final (and cannot be changed once initiated). Extending XQuery with db:commit() kind of breaks these basic principles. I also think support for ‘chaining transactions’ would be beneficial, but maybe on another level (commands?). We write loads of production code in XQuery and this reflects just our experience - but I’d be happy to hear what others have to say. Cheers, Lukas > On 09 Feb 2015, at 09:38, Christoph Gaukel <christoph.gaukel(a)gmx.de> wrote: > > Hi Lukas, > > thank you for your answer, but this is no good news. In my specific case, i see a variant to solve the problem. But i think, that the concept of transactions, which combines a number of updating commands into an atomic unit, is a good idea and it is a heavy load on the freedom of design if the only chance, to build transactions is the unit of an xquery. > > From my point of view, it would be an important improvement, if something like the commit of sql would be added to the xquery-language. If BaseX would introduce it as a specific extension like db:commit(), this would be great! > > Cheers, > Christoph

1 0

BaseX 8.0: The XMLPrague 2015 Edition
by Christian Grün 09 Feb '15

09 Feb '15

Dear XML aficionados, We are proud to present you Version 8.0 of BaseX, your XML database system and XQuery processor (http://basex.org)! It is being released in alignment with the XML Prague 2015 Conference. We provide you with quite a bunch of new and exciting features: XQUERY - Support for XQuery 3.1 is nearly complete - We switched to a new default serialization ("adaptive") - Index rewritings have been improved, more precise cost estimations - MIXUPDATES option: update items and return results at the same time - New modules: Array and User Module - New annotations: %basex:inline, %basex:lazy - 13 of our modules were updated and extended WEB APPLICATIONS - DBA: Database Administration in the Browser - RESTXQ: regular expressions in paths, support for quality factors - AUTHMETHOD option: choose between Basic and Digest authentication STORAGE - Faster document index (storing paths to all XML documents) - Replace documents in-place whenever possible - Updatable index structures now take much less space - AUTOOPTIMIZE option: optimize after each update SECURITY - Revised user management; users are stored as XML - Digest authentication, Salted SHA256 - Clients in various languages updated GUI - Better code completions The documentation is available at http://docs.basex.org. We are looking forward to your feedback, Christian BaseX Team

1 0

XSD 1.1 Validation
by Alex R. Loayza 07 Feb '15

07 Feb '15

Hello, I tried to use xsd-info() to validate using a schema 1.1. However, I got the following error: Fatal:s4s-elt-invalid-content.1: The content of '#AnonType_reporte' is invalid. Element 'assert' is invalid, misplaced, or occurs too often. According to the validation module documentation, said module uses "Java’s standard validators". Does this refer to Xerces? If not, is there a way to call Xerces to perform validation from BaseX? Or maybe any other way to validate with 1.1? Thank you. Alex

2 1

USER option and WebDAV?
by C. M. Sperberg-McQueen 07 Feb '15

07 Feb '15

The documentation [1] says: The WebDAV service uses the database user credentials in order to perform authentication and authorization. If database user and password are explicitly specified when starting the BaseX HTTP Server using the corresponding startup options, WebDAV will not request additional user authentication from the client. [1] http://docs.basex.org/wiki/Webdav I take this to mean that if I start basexhttp from a directory my-app, with a .basex file containing, among other things, USER = myappuser PASSWORD = lips_are_sealed then when the client issues a PUT request against a URI of the form http://localhost:8984/webdav/my_app_dir/mydoc34.xml the PUT will be accepted and mydoc34.xml will be added to the database or updated there, depending on whether myappuser has WRITE privileges to the database my_app_dir. I also take it to be saying that the WebDAV server will not ask the client for credentials. (This last is important to me because it appears that in some Web browsers an XForms submission that requires credentials will cause the browser to ask the user for userid and password, and in other browsers the submission will fail silently. If I can just have BaseX use the application-specific user quietly, that will work fine for this particular application.) However, what I'm seeing suggests that WebDAV is not using the userid specified in the .basex configuration file -- in my tests, one browser is prompting me for credentials and another is failing silently. I suppose that what I'm seeing may be consistent with an error in the password in the .basex file, but I have tried it with passwords that are hard to mistype, so I don't think that that's it. I have not found a command to ask the server what user I currently am (the equivalent of whoami). Am I misreading the documentation? -- **************************************************************** * C. M. Sperberg-McQueen, Black Mesa Technologies LLC * http://www.blackmesatech.com * http://cmsmcq.com/mib * http://balisage.net ****************************************************************

2 1

Are WebDAV authorization failures returning 200? Or is the BaseX log being optimistic?
by C. M. Sperberg-McQueen 06 Feb '15

06 Feb '15

I'm a little puzzled. As other mail (just sent) describes, I'm having some trouble getting PUT requests to work in some browsers; as far as I can tell, the current cause is that WebDAV is requesting credentials for the PUT, and the browser is not asking the user for the credentials. However, when a PUT request fails for lack of credentials, or for wrong credentials, I would expect the request to return an HTTP 401. Instead, the BaseX log seems to show 200 requests, both for the initial request from the client without credentials, and for the second request, whether the second request was made with correct credentials (and succeeded) or with bad credentials (and failed). Is the WebDAV service really returning a 200, or are the logs inaccurate? -- **************************************************************** * C. M. Sperberg-McQueen, Black Mesa Technologies LLC * http://www.blackmesatech.com * http://cmsmcq.com/mib * http://balisage.net ****************************************************************

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk February 2015