BaseX-Talk June 2018

basex-talk@mailman.uni-konstanz.de

28 participants
26 discussions

"Infinity" is incorrectly cast to xs:float.
by Reece Dunn 28 Jun '18

28 Jun '18

Hi, I have found the following behaviour in BaseX 9.0: "Infinity" cast as xs:float (: INF :) "-Infinity" cast as xs:float (: -INF :) "infinity" cast as xs:float (: [FORG0001] Cannot convert xs:string to xs:float: "infinity". :) "Infinity" cast as xs:double (: [FORG0001] Cannot convert xs:string to xs:double: "Infinity". :) "-Infinity" cast as xs:double (: [FORG0001] Cannot convert xs:string to xs:double: "-Infinity". :) >From my reading of Functions and Operators 3.1, and XML Schema 1.1 Part 2 Datatypes, "Infinity" and "-Infinity" are both invalid values for xs:float (like with xs:double) -- they should only be "INF" and "-INF". Kind regards, Reece H. Dunn

2 1

Fwd: Tracing query execution
by Iwan Briquemont 28 Jun '18

28 Jun '18

I forgot to reply to the mailing list too. ---------- Forwarded message ---------- From: Iwan Briquemont <tracnar(a)gmail.com> Date: 2018-06-28 10:51 GMT+02:00 Subject: Re: [basex-talk] Tracing query execution To: Fabrice ETANCHAUD <fetanchaud(a)pch.cerfrance.fr> Hi Fabrice, Indeed that's another solution. I also thought about restricting the expression to a subset of what XQuery supports to implement what you describe. But then the information would be restricted to the expressions which follow that subset. Note that I do not need to know how it is decided per-se for my application, it is as a debugging feature. Behind the boolean expressions there are also some more complicated queries (like joining data from multiple sources), which is why I like to be able to use XQuery all the way. I think this kind of debugging would be useful for actual queries too. Regards, Iwan 2018-06-28 10:18 GMT+02:00 Fabrice ETANCHAUD <fetanchaud(a)pch.cerfrance.fr>: > Hi Iwan, > > > > IMHO it is more a design issue than a tool issue. > > If you need to know exactly where a boolean expression is decided, > > You might have to implement a boolean algebra interpreter. > > You could even describe your questions in xml format, to be interpreted by > a recursive function against your hardware corpus. > > > > That way you could implement rules like : > > All ancestors are ‘and’ operators and my current node is ‘false’ => ‘false’ > > All ancestors are ‘or’ operators’ and my current node is ‘true’ => ‘true’ > > And detect exactly where your expression is decided. > > > > This make me think of the MarkLogic stored query feature. > > > > Sorry I just thought about that a few minutes, > > I hope it helps, > > > > Best regards, > > Fabrice > > > > *De :* BaseX-Talk [mailto:basex-talk-bounces@mailman.uni-konstanz.de] *De > la part de* Iwan Briquemont > *Envoyé :* mercredi 27 juin 2018 23:04 > *À :* basex-talk(a)mailman.uni-konstanz.de > *Objet :* [basex-talk] Tracing query execution > > > > Hello, > > > > I use BaseX mostly for boolean queries, I have a hardware database and I > check if specific hardware support features I need. > > > > It works great but when something is not as expected, it's hard to find > out the reason. > > > > E.g. given an expression like: > > $some-value = $some-list and (custom:predicate() or $x > $y) > > > > I would like to know why it's true or false. > > For now I add trace() manually on the subexpressions, rerun, add trace to > more specific parts, etc. > > > > Ideally I would want to break down the query execution so it shows the > values of subparts of the query to pinpoint why it is false, e.g. have an > output like: > > $some-value = $some-list and (custom:predicate() or $x > $y) -> false() > > $some-value = $some-list -> true() > > $some-value -> 1 > > $some-list -> (1, 2, ..., 10) > > custom:predicate() or $x > $y -> false() > > custom:predicate() -> false() > > ... # It should also go inside the function > > $x > $y -> false() > > $x -> 10 > > $y -> 11 > > > > Any ideas how it could be achieved? > > Looking at the code, maybe a debug() (like iter() or item()) method could > be added to Expr objects which would trace the expression query, file, line > and the result of the expression (or probably the first x characters of the > result to avoid huge output)? With an xquery function which would trigger > it. > > > > I also thought of modifying the query programmatically to add trace() > calls but that seems overly complicated. > > > > Best regards, > > Iwan >

1 0

How to export a database containing xi:include to multiple files
by Marco Randazzo 27 Jun '18

27 Jun '18

Hi, I'm posting again the same question I did some time ago, unfortunately unanswered :( I used baseX GUI (9.0.1) to create a database similar to the following test file: <main xmlns:xi="http://www.w3.org/2001/XInclude"> <xi:include href="folder1/file1.xml" /> <xi:include href="folder2/file1.xml" /> </main> The Result displayed in the baseX gui is correct: <main xmlns:xi="http://www.w3.org/2001/XInclude"> <data xml:base="folder1/file1.xml">5555</data> <data xml:base="folder2/file1.xml">6666</data> </main> Now, after editing the values, I would like to export the contents of the database to MULTIPLE xml files, recreating the same files and the original folders (I see this information is not lost, it is stored in the value of xml:base) However, using the export function available in the baseX GUI, I am able to obtain only a SINGLE file containing the Result shown above, where the two files have been merged in a single file. What can I do? Thank you, Cheers, Marco Randazzo

2 1

DBA session timeout
by Omar Siam 26 Jun '18

26 Jun '18

Hi list! I just got asked if I can change the session timeout for DBA. I actually can't. I don't know where to look. Can anybody can give me a hint? Best regards Omar Siam

2 1

Re: [basex-talk] doc path in basex
by Martin Lourduswamy 26 Jun '18

26 Jun '18

Hi, I used db:node-pre(db:text("db", "ae4b577bd9f578556cd")//../..) delete node db:open-pre("db",333) to immensely speed the basex access. Thanks for helping me with how to get a db:node form basex. I have one more question. I am using FreeBSD to host BaseX and it is stable so for in the testing. Are there any known problems of openjdk8 on FreeBSD and baseX. I could not find any issues so far with basex. But I read somewhere that openjdk8 on FreeBSD dumps core some time. I think it is for specific applications only not for baseX. Just a architectural suggestion on picking the best OS to host baseX. Please let me know when you have some time, ( BaseX works excellent on Windows, CentOS and FreeBSD and produced same results in all of them. But on windows the disk was close to 100% in windows while running my application, centos and FreeBSD has no problems. ) Thanks, Regards Martin Lourduswamy On Thu, Jun 14, 2018 at 2:36 PM, Christian Grün <christian.gruen(a)gmail.com> wrote: > Hi Martin, > > The behavior of BaseX is similar on Windows and Linux. > > I would guess you started the application from different directories? > With file:current-dir(), you get your current working directory [1]. > file:base-dir() points you to the directory in which your XQuery file > is stored. > > Best, > Christian > > [1] http://docs.basex.org/wiki/File_Module#file:current-dir > > > On Thu, Jun 14, 2018 at 2:35 PM Martin Lourduswamy > <martin.louis(a)gmail.com> wrote: > > > > Hi, > > I have a query that creates DB > > > > db:create("database", "db.xml") > > > > I have put the db.xml in the bin dir. > > > > This works for unix/Linux, but on windows I need to specifically give > bin dir lke > > > > db:create("database", "bin/db.xml") > > Otherwise it does not work. > > > > I do not want to hard code path in the script. Is there a general way to > specify the path, > > Thanks, > > Regards > > Martin Lourduswamy >

2 2

Re: [basex-talk] Usage of doc's in BaseX
by Fabrice ETANCHAUD 14 Jun '18

14 Jun '18

Hi Bram, You are welcome, BaseX is such a versatile tool ! Keep index and data content separate could help in various ways. The main one is that, considering you still have to index your index database, you will index only needed data, and you might even set autoupdate to forget about index management. As it seems your data is 'append only', you should build your index on 'pre' node values instead of 'id' node values, in order to gain direct access to data. When working on XML documents, I try to replace 'database' with 'collection', and that seems to help in making effective decisions. Best regards, Fabrice Etanchaud [1] http://docs.basex.org/wiki/Node_Storage [2] http://docs.basex.org/wiki/Database_Module#db:node-pre [2] http://docs.basex.org/wiki/Database_Module#db:open-pre De : Bram Vanroy [mailto:Bram.Vanroy@UGent.be] Envoyé : jeudi 14 juin 2018 13:48 À : Fabrice ETANCHAUD Objet : RE: Usage of doc's in BaseX Hi Fabrice Thanks for the reply. The values that I am trying to index are indeed computed from the original XML but not present in it. Thanks for the limitations link, I had seen it but couldn't find it when googling for 'basex limitations' or others. Considering that my databases will be static and don't need updating, would you still argue for a separation? Thanks again Bram Van: BaseX-Talk <basex-talk-bounces(a)mailman.uni-konstanz.de> Namens Fabrice ETANCHAUD Verzonden: donderdag 14 juni 2018 11:18 Aan: BaseX <basex-talk(a)mailman.uni-konstanz.de> Onderwerp: Re: [basex-talk] Usage of doc's in BaseX Hello Bram, IMHO the main argument for data/index separation is the ease of index recreation, and the ease of reindexation of your index database. Is there still a need for ad hoc indexing, now that BaseX let us index only a node name selection ? I guess you need to index computed values ? For current BaseX limitations, you will find them in [1], but you might have already read that page. I hit the database node number limit once working with the European Patent Office DOCDB collection. So I had to set up a database naming politics to dispatch the documents. Hoping it helps, Best regards, Fabrice Etanchaud Senior Data Specialist CERFrance PCH [1] http://docs.basex.org/wiki/Statistics De : BaseX-Talk [mailto:basex-talk-bounces@mailman.uni-konstanz.de] De la part de Bram Vanroy Envoyé : jeudi 14 juin 2018 10:47 À : BaseX Objet : [basex-talk] Usage of doc's in BaseX Dear BaseX team I am planning an update on our previous custom indexing system [1]. But to do this I have a couple of questions. The major ones will be how to write an efficient custom indexing query in XQuery, but that'll be for another email. (In fact, we have a dual indexing system, so two index files per main file.) For now I am mainly interested in different documents in a single databases, and the doc() functionality. Intuitively, I'd say that documents that are related to each other should be put in the same database. E.g. one database with different documents for plants, and one database with different documents for animals. But when I was scrolling through the documentation of BaseX, I noticed that when creating custom indices you do not put those in the same db as the original content, so you have on database for the content and one for the index [2]. Is this the way it's typically done? More generally, the questions that I have are the following: * What is the actual difference in BaseX between using separate documents in a single database, or using different databases all together? * Is there a performance difference when I would put my index file in the same database as the content, vs. when using different databases altogether? * What is the max allowed size for a document in a database and a database itself respectively? (I have files that are 100's of GB in size. It might not be plausible to have a file and its index file in the same database.) Thank you in advance Kind regards Bram Vanroy Doctoral Research at Ghent University, Belgium https://www.lt3.ugent.be/people/bram-vanroy/ [1] https://biblio.ugent.be/publication/8534144 [2] http://docs.basex.org/wiki/Indexes#Custom_Index_Structures

1 0

doc path in basex
by Martin Lourduswamy 14 Jun '18

14 Jun '18

Hi, I have a query that creates DB db:create("database", "db.xml") I have put the db.xml in the bin dir. This works for unix/Linux, but on windows I need to specifically give bin dir lke db:create("database", "bin/db.xml") Otherwise it does not work. I do not want to hard code path in the script. Is there a general way to specify the path, Thanks, Regards Martin Lourduswamy

1 0

Usage of doc's in BaseX
by Bram Vanroy 14 Jun '18

14 Jun '18

Dear BaseX team I am planning an update on our previous custom indexing system [1]. But to do this I have a couple of questions. The major ones will be how to write an efficient custom indexing query in XQuery, but that'll be for another email. (In fact, we have a dual indexing system, so two index files per main file.) For now I am mainly interested in different documents in a single databases, and the doc() functionality. Intuitively, I'd say that documents that are related to each other should be put in the same database. E.g. one database with different documents for plants, and one database with different documents for animals. But when I was scrolling through the documentation of BaseX, I noticed that when creating custom indices you do not put those in the same db as the original content, so you have on database for the content and one for the index [2]. Is this the way it's typically done? More generally, the questions that I have are the following: * What is the actual difference in BaseX between using separate documents in a single database, or using different databases all together? * Is there a performance difference when I would put my index file in the same database as the content, vs. when using different databases altogether? * What is the max allowed size for a document in a database and a database itself respectively? (I have files that are 100's of GB in size. It might not be plausible to have a file and its index file in the same database.) Thank you in advance Kind regards Bram Vanroy Doctoral Research at Ghent University, Belgium https://www.lt3.ugent.be/people/bram-vanroy/ [1] https://biblio.ugent.be/publication/8534144 [2] http://docs.basex.org/wiki/Indexes#Custom_Index_Structures

2 1

Issue with selecting child nodes
by Shaun Flynn 13 Jun '18

13 Jun '18

Hello there, I have the following query: declare variable $queryPath external := "D:\NROD Projects\xqCrews\diagrams.v3\"; declare variable $testSet := doc($queryPath || "tests\testSet1.xml"); $testSet where testSet1.xml is: <test> <test1> <content>Foobar</content> </test1> <test1> <content>Foobar</content> </test1> </test> When I run $testSet/*, I would expect to get the following result: <test1> <content>Foobar</content> </test1> <test1> <content>Foobar</content> </test1> However, I get the complete document in testSet1.xml When I run this against testSet1.xml $testSet/*/* then I get what would I expect to see: <test1> <content>Foobar</content> </test1> <test1> <content>Foobar</content> </test1> Am I misunderstanding something? Shaun

2 1

Nugets?
by Peter Villadsen 08 Jun '18

08 Jun '18

Hello, I am building a system that relies on a Basex backend, and for that I have chosen to use the TCP protocol. My system is built in managed code, so I went ahead and copied the code provided here: https://github.com/BaseXdb/basex/tree/master/basex-api/src/main/c%23 which satisfied my needs very nicely. However, since I have not written this code myself, it is subject to expensive and time consuming pre-shipping legal audits where it is checked that the code does not contain references to other public domain code. Engineers developing managed code today expect APIs to be shipped as Nuget packages. This has the advantages that it is extremely easy to uptake, you can regard it as a black box (but get the source if you need to), and it supports dependencies (none, in your case) and you can go back and use previously shipped versions (which is important in your case, since you have just changed the authentication scheme I believe). Could you consider offering the API as both Nugets and source on Github? Best Regards Peter Villadsen Principal Architect Microsoft Business Applications Group

5 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk June 2018