BaseX-Talk

basex-talk@mailman.uni-konstanz.de

6 participants
5250 discussions

Traling empty nodes in csv:serialize
by Lars Johnsen 22 Mar '14

22 Mar '14

Hi all I have a question about csv:serialize and blank nodes. Trailing blanks are indicated with a separator, but those in the middle are. csv:serialize( <rows> <row> <f>1</f> <s>2</s> <t>3</t></row> <row> <f></f> <s></s> <t>3</t></row> <row> <f>1</f> <s></s> <t>3</t></row> <row> <f>1</f> <s></s> <t></t></row> <row> <f>1</f> <s>2</s> <t></t></row> </rows>) Here is the output (BaseX 7.8.1) , where line 4 and 5 are missing trailing separators: 1,2,3 ,,3 1,,3 1 1,2 Could this be fixed, or is it a feature? All the best Lars G Johnsen National Library of Norway

3 3

Re: [basex-talk] Bug (?) - trailing whitespace in text nodes
by Hans-Juergen Rennau 21 Mar '14

21 Mar '14

Mm, the documentation says: "Chops all leading and trailing whitespaces from text nodes while building a database, and discards empty text nodes. By default, this option is set to true, as it often reduces the database size by up to 50%. It can also be turned off on command line via -w." The text states clearly that chopping affects only text nodes stored into a database. At any rate - the problem remains, whether or not I use option -w, and whether or not I use prolog option db:chop. (Side remark: it would be a serious issue if the prolog option were required, as this would imply that standard conformant behaviour could only be achieved by making the code unportable.) Kind regards, Hans-Juergen -------------------------------------------- Dirk Kirsten <dk(a)basex.org> schrieb am Do, 20.3.2014: Betreff: Re: [basex-talk] Bug (?) - trailing whitespace in text nodes An: "Hans-Juergen Rennau" <hrennau(a)yahoo.de>, "basex-talk(a)mailman.uni-konstanz.de" <basex-talk(a)mailman.uni-konstanz.de> Datum: Donnerstag, 20. März, 2014 18:28 Uhr Dear Hans-Jürgen, I am not quite sure it is intended that the CHOP option is applied to text nodes. At least the wording in the documentation ("while building a database") does not indicate it, while I think it actually does make sense. Christian will have to answer whether this works as is intended behavior. However, you can set the chop option to false within your XQuery by declaring it declare option db:chop "false"; and this should also affect reading in files from the file system. At least this works for me. Cheers, Dirk On 20/03/14 17:47, Hans-Juergen Rennau wrote: > My understanding is that it only affects database documents, and I used file input. > > Nevertheless, I also tried option -w, but always got the same result. > > Kind regards, > Hans-Jürgen > > > > > > Hans-Juergen Rennau <hrennau(a)yahoo.de> schrieb am 17:45 Donnerstag, 20.März 2014: > > Dear Dirk, thank you. > > But this is strange - I ran the query using a file as input - not a database document. > > I tried two versions: > BaseX 7.8.2 beta f505185 [Standalone] > BaseX 8.0 beta 606f18b [Standalone] > > OS is Windows 7. > > I always get this result: > <para>xxx<emphasis role="italic">abc</emphasis>yyy.</para> > > Using a different XQuery processor, I get this result, as expected: > <para>xxx <emphasis role="italic">abc</emphasis> yyy.</para> > > Kind regards, > Hans-Jürgen > > > > > > Dirk Kirsten <dk(a)basex.org> schrieb am 17:10 Donnerstag, 20.März 2014: > > Dear Hans-Jürgen, > > When running local:edit() on an in-memory node I get the expected and > correct result, including whitespaces. > > I guess that you run this command on a database node and the XML > documents were parsed with CHOP being true (which is the default), this > would explain the behavior and would be as expected. If you do not want > this you might consider setting the CHOP option (see > https://docs.basex.org/wiki/Options#CHOP) to false. > > Cheers, > Dirk > > > On 20/03/14 16:57, Hans-Juergen Rennau wrote: >> Dear BaseX team, >> >> I think I observed a bug concerning trailing whitespace in text nodes. >> >> Please consider this input document: >> >> <para>xxx <emphasis role="italic">abc</emphasis> yyy.</para> >> >> >> [Note the blanks between xxx and <emphasis>.] >> >> The result of the following "null-transformation" >> >> ======================= >> >> declare function > local:edit($n as node()) >> as node()? { >> typeswitch($n) >> case document-node() return >> document {for $c in $n/node() return local:edit($c)} >> case element() return >> element {node-name($n)} >> {for $ac in $n/(@*, node()) return local:edit($ac)} >> default return $n >> }; >> local:edit(.) >> ======================= >> >> should be identical, but what I get is this: >> >> <para>xxx<emphasis role="italic">abc</emphasis>yyy.</para> >> >> The > blanks after "xxx" are gone! >> >> >> When transforming mixed content like docbook, this can have awkware consequences. >> >> Kind regards, >> Hans-Jürgen >> >> >> >> _______________________________________________ >> BaseX-Talk mailing list >> BaseX-Talk(a)mailman.uni-konstanz.de >> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >> > -- Dirk Kirsten, BaseX GmbH, http://basex.org |-- Firmensitz: Blarerstrasse 56, 78462 Konstanz |-- Registergericht Freiburg, HRB: 708285, Geschäftsführer: | Dr. Christian Grün, Dr. Alexander Holupirek, Michael Seiferle `-- Phone: 0049 7531 28 28 676, Fax: 0049 7531 20 05 22

2 4

feature's requests and not publicly released features
by Fabrice Etanchaud 21 Mar '14

21 Mar '14

Dear all, First of all, BaseX is just fantastic ! Could you please tell me if you may release the following features in near future ? 1. User defined indexes Let's consider you have to index multi lingual documents. Currently, one have to partition each document in mono-lingual documents, and add them in separate collections because there can be only one fulltext index per collection, and because all text() nodes will be indexed. Are others BaseX users interested with user defined indexes (attribute, text, and fulltext) ? Wouldn't user defined indexes dramatically improve performance (during requests, and optimization) ? 2. Break current collection limitation on the maximum number of nodes. 3. Possibility to store millions of small documents, and do efficient 'db:replaces' or 'db:delete'. Last, How does BaseX team provide non-open-source features ? Best regards, Fabrice Etanchaud Questel/Orbit

2 1

Performance
by Marco Lettere 21 Mar '14

21 Mar '14

Hello to everyone, while trying to trace the performance I could expect from my RestXQ app I created a DB with something like 300/400k documents. For the test the documents are rather homogenoeus and stored plainly in the DB root collection. I had two major objectives. 1) understand the behaviour of the query when run on a significant (even if not huge) number of documents. I've noticed that something like collection('db')/a[@att = 'xxx' and b/text() = 'zzz'] on my laptop (Intel I7, 8 GB Ram and SSD) takes some 5 to 7 seconds. Is this reasonable? I was expecting slightly better performance but I must admit that the documents are rather similar thus maybe the indexing is not very selective. What I noticed and this is feeling strange is that the time is often spent in rather similar proportion between query compilation and query evaluation and in some runs (1 every 5) most of the time is spent in compilation and only few msec in evaluation. But the query is rather simple so I assume that time spent in opening large collections (or accessing the indexes) is computed in the compilation phase. Is it like that? Is there a way to restructure my query to be somehow more selective reducing the time of accessing the collection/index? 2) to measure the difference between the same query when run directly and when run through xquery:eval. Here I noticed that the difference between plain and xquery:eval() execution is negligible when the time for the evaluation increases. So I assume that the xquery:eval is using the indexing system even if this is not reported in the info view of the GUI. Is it like that? Thank you all. Regards, Marco.

2 1

Namespaces ...
by Marco Lettere 21 Mar '14

21 Mar '14

Hello all, I've a few questions related to namespaces. I've noticed that on one of the info panels of the the GUI all the namespaces of the documents stored in a DB are listed. Is there a way to get this information from inside an XQuery? My problem is that I have to perform queries that are dynamically generated on a heterogeneuos set of documents. By now I have to store somewhere an association between one input parameter of the query and a corresponding set of namespaces to be used. This is then transformed into a list of "declare namespace ..." statements. I thought I could pregenerate a declare statement for every namespace in the DB by default thus avoiding to maintain the association. Would there be a significant impact on query or query compilation performance? Thanks, Marco.

3 2

restriction on number of namespaces has apparently been lifted – thank you
by Imsieke, Gerrit, le-tex 21 Mar '14

21 Mar '14

Today I noticed that I could actually build an index of all XSLT, XProc, Relax NG and Schematron files on my hard disk (3316 files). I couldn’t do that 2 years ago because the maximum number of distinct namespaces in a DB was limited to 256 or so. Thanks, BaseX team, for lifting this restriction! This has already proved really useful: I knew that I wrote an XProc step that conditionally invoked a step whose local name I remembered. The simple XPath expression collection('home')//*:declare-step[*:choose//*:paths] helped me identify the two relevant files. Since we do a lot of development in XML-syntax languages, an XML database is really really good for structured searches on these files. I bet you XQuery devs still use grep to query your code ;) Gerrit

1 1

mailing list archives 403?
by Jesse Clark 20 Mar '14

20 Mar '14

Is anybody else getting a 403 Forbidden error trying to access the mailing list archives? https://mailman.uni-konstanz.de/pipermail/basex-talk/ -Jesse

2 2

Bug (?) - trailing whitespace in text nodes
by Hans-Juergen Rennau 20 Mar '14

20 Mar '14

Dear BaseX team, I think I observed a bug concerning trailing whitespace in text nodes. Please consider this input document: <para>xxx <emphasis role="italic">abc</emphasis> yyy.</para> [Note the blanks between xxx and <emphasis>.] The result of the following "null-transformation" ======================= declare function local:edit($n as node()) as node()? { typeswitch($n) case document-node() return document {for $c in $n/node() return local:edit($c)} case element() return element {node-name($n)} {for $ac in $n/(@*, node()) return local:edit($ac)} default return $n }; local:edit(.) ======================= should be identical, but what I get is this: <para>xxx<emphasis role="italic">abc</emphasis>yyy.</para> The blanks after "xxx" are gone! When transforming mixed content like docbook, this can have awkware consequences. Kind regards, Hans-Jürgen

3 5

Question about BaseX JAVA API Usage ...
by Christopher Lyons 20 Mar '14

20 Mar '14

I've just starting using BaseX (V.7.8.1) and have a very quick question that I hope somebody can help me with. I've reviewed the BaseX docs and tried looking for an answer to this on the Wiki but have not been successful. I've installed BaseX (on Win7 Pro/64-bit) and have been using the GUI interface (non-server) and it has been working great. I just started exploring the JAVA API and am having a few basic problems. I'm trying to use the RunQueries.java example file (currently just need to do some local queries from a JAVA app). Just an FYI, the links from BaseX doc site to the GitHub example repository are all broken. The examples are on GitHub but it looks like they were recently moved/updated and the links must have changed and haven't been updated on the BaseX site. I'm an experienced programmer but am just getting up-to-speed with JAVA, so my question may be more related to that than a specific BaseX problem but hopefully someone can point me in the right direction. I use Eclipse and when I create a test class with the RunQueries.java code, Eclipse is not able to resolve the BaseX package imports at the start of the class. Namely, the following code: import org.basex.core.*; import org.basex.core.cmd.*; import org.basex.data.*; import org.basex.io.serial.*; import org.basex.query.*; import org.basex.query.iter.*; import org.basex.query.value.item.*; Should the general install of BaseX put these packages into their proper places? Or is there something else I have to do to get these packages properly installed and able to be resolved? Appreciate any help. Thanks, Chris Lyons

2 1

Re: [basex-talk] BaseX-Talk Digest, Vol 51, Issue 20
by John Best 19 Mar '14

19 Mar '14

Dear Christian, Good to see these features... What about MIXED Content searching ? :( On Wed, Mar 19, 2014 at 4:30 PM, <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. BaseX: Upcoming Features (Christian Gr?n) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 18 Mar 2014 13:03:26 +0100 > From: Christian Gr?n <christian.gruen(a)gmail.com> > To: BaseX <basex-talk(a)mailman.uni-konstanz.de>, BaseX > <basex-announce(a)mailman.uni-konstanz.de> > Subject: [basex-talk] BaseX: Upcoming Features > Message-ID: > <CAP94bnOKazkmPDE4qbw+MZ9OR= > ceCh+4vM9E3tcgOrBMFcKyBg(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Dear BaseX aficionados, > > An upcoming version of our software (7.9 or 8.0) will make it much > easier to perform updates and return items at the same time [1]. It > will also contain an xquery:update function and will bring xquery:eval > and xquery:evaluate together again [2] Another exciting and > sophisticated feature we are working on is query precompilation [3], > which will particularly speed up large XQuery applications and allow > for more request-specific optimizations. > > Next, we are working on a Database Administration interface based on > RESTXQ, and we will also drop out the confusing client/server dialog > from the GUI. > > Feature 1 and 2 are already available via a feature branch [4]. If you > are working with the git sources, we are excited to get your feedback! > > Christian > > [1] https://github.com/BaseXdb/basex/issues/873 > [2] https://github.com/BaseXdb/basex/issues/878 > [3] https://github.com/BaseXdb/basex/issues/874 > [4] https://github.com/BaseXdb/basex/tree/issue873 > > > ------------------------------ > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk(a)mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk > > > End of BaseX-Talk Digest, Vol 51, Issue 20 > ****************************************** > -- Have a nice day JBest

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk