BaseX-Talk May 2012

basex-talk@mailman.uni-konstanz.de

48 participants
64 discussions

whitespace handling
by Godmar Back 25 May '12

25 May '12

Hi, I'm confused about whitespace. I've written an XQuery that returns an XML fragment based on some computation on an underlying XML document. The returned XML contains insignificant whitespace, which then adversely affects my program. I'm not sure if I'm causing it or BaseX, or even what the rules are. My XQuery contains code such as this one (I'm using color to emphasize the relevant parts). declare function local:buildSubTree($id) { let $feed := doc($doc_name)/atom:feed let $parent := $feed/atom:entry[atom:id=$id] let $children := data($parent//libx:entry/@src) return if (fn:count($children) = 0) then () else for $child_id in $children return if (local:isInThisFeed($feed, $child_id)) then <node id='{$child_id}' type='{local:getType($feed, $child_id)}' title='{local:getTitle($feed, $child_id)}'>{ local:buildSubTree($child_id) }</node> else if (functx:is-absolute-uri($child_id)) then <node id='{$child_id}' title='Unpublished Entry' type='external' /> else <node id='{$child_id}' title='Unpublished Entry' type='import' /> }; but the result contains fragments such as this, which is an 2-space indented formatting of the XML, with insignificant whitespace added: <node id="180" title="Put Google Book results into Addison" type="libapp"> <node id="181" title="Search Google Books while searching Addison" type="module"/> <node id="182" title="Display HTML notifications via an embedded panel using jGrowl" type="module"/> </node> If I say <node>{ ... }</node> in the XQuery etc., should there be insignificant whitespace in the response? Thank you for any help/pointers. (Note that I have considered simply stripping insignificant whitespace, but I do not like this solution since for some queries, I'd like to preserve it, whereas for others I absolutely cannot have insignificant whitespace since I'm performing traversals of the resulting XML DOM Tree.) Thank you! - Godmar

2 1

file:list - a question
by Hans-Juergen Rennau 24 May '12

24 May '12

Hello, a question about the function file:list. The documenation says: "The returned paths are relative to the provided path." My understanding is that if the path is a/b/c and this dir contains a file fool.xml, the returned path would be "fool.xml", rather thatn "a/b/c/fool.xml". What confuses me is that I observe two different behaviours in two different BaseX versions, once with and once without path: version 7.2 with path, version 7.2.2 without path. (The OS also differs in the environments, but I suppose this is irrelevant.) My question: is the output without path (more generally: with a path relative to the stated dir) the correct one and will be produced in all future versions? Thank you. Kind regards, Hans-Juergen

2 1

Managing databases via XQuery
by Andy Bunce 24 May '12

24 May '12

I sometimes find myself, in code, wanting to create a database, or more specifically test if a database exists and create it if does not. The database module appears not have functions to create (or delete databases). Is this a deliberate design decision? I can do this via the command interface, although test and create is a bit messy; I can do it via the REST interface, and I think via the WebDAV interface, but not, it seems, via XQuery directly. Adding additional functions to the database module would be a solution, or maybe a util:command() that would execute any BaseX command? /Andy

3 4

RESTXQ and parameters in the media-type
by Philippe Rathé 22 May '12

22 May '12

Hello, I would like to know if the parameters in the media-type should be in the "produces" annotation or elsewhere. Because I can't get it to work with the media-type of an atom feed member. %rest:produces("application/atom+xml;type=entry") The valid syntax can be found in rfc2616 section 3.7 Media Types: http://tools.ietf.org/html/rfc2616#section-3.7 In the RESTXQ wiki page, we can see the media type of an atome feed %rest:produces("application/atom+xml") But I did not found anything about using a parameter in the media type. Thanks.

2 3

Open Source-based Business
by Yu, Yiqing 22 May '12

22 May '12

Hi open source software developer, I am a research assistant at Institute for Information Systems and New Media, University of Munich. Driven by the interest in open source software, I want to investigate open source-based business by connecting the decision-making theory to the software development practice. Based on this idea, I designed an online survey "OS-based business": http://www.unipark.de/uc/osb/ Through "advanced search" and your profile at Github I find you may fit into the survey's target group. I gladly invite you to it and look forward to your participation. Some points in the survey may inspire your research or business ideas. :) I would deeply appreciate your support! Best Regards, Yours, Yiqing Yu Institute for Information Systems and New Media Ludwig-Maximilians-Universität München www.wim.bwl.lmu.de<http://www.wim.bwl.lmu.de/>

1 0

Disable or control query caching
by Manuel Bernhardt 22 May '12

22 May '12

Hello, we're getting an apparent deadlock (followed by a GC overhead limit exceeded) on one machine, when starting some processing on a collection of over 800 000 records. Going after it with YourKit yields the following: application-akka.actor.default-dispatcher-110 <--- Frozen for at least 3m 7s org.basex.server.Query.cache(InputStream) org.basex.server.ClientQuery.cache() org.basex.server.Query.more() eu.delving.basex.client.Implicits$RichClientQuery.hasNext() scala.collection.Iterator$$anon$19.hasNext() scala.collection.Iterator$$anon$29.hasNext() scala.collection.Iterator$class.foreach(Iterator, Function1) scala.collection.Iterator$$anon$29.foreach(Function1) core.processing.CollectionProcessor$$anonfun$process$2.apply(ClientSession) core.processing.CollectionProcessor$$anonfun$process$2.apply(Object) core.storage.BaseXStorage$$anonfun$withSession$1.apply(ClientSession) core.storage.BaseXStorage$$anonfun$withSession$1.apply(Object) eu.delving.basex.client.BaseX$$anonfun$withSession$1.apply(ClientSession) eu.delving.basex.client.BaseX$$anonfun$withSession$1.apply(Object) eu.delving.basex.client.BaseX.withSession(Function1) eu.delving.basex.client.BaseX.withSession(String, Function1) core.storage.BaseXStorage$.withSession(Collection, Function1) core.processing.CollectionProcessor.process(Function0, Function1, Function1, Function3) core.processing.DataSetCollectionProcessor$.process(DataSet) actors.Processor$$anonfun$receive$1.apply(Object)<2 recursive calls> akka.actor.Actor$class.apply(Actor, Object) actors.Processor.apply(Object) akka.actor.ActorCell.invoke(Envelope) akka.dispatch.Mailbox.processMailbox(int, long) akka.dispatch.Mailbox.run() akka.dispatch.ForkJoinExecutorConfigurator$MailboxExecutionTask.exec() akka.jsr166y.ForkJoinTask.doExec() akka.jsr166y.ForkJoinPool$WorkQueue.runTask(ForkJoinTask) akka.jsr166y.ForkJoinPool.runWorker(ForkJoinPool$WorkQueue) akka.jsr166y.ForkJoinWorkerThread.run() In the server logs I can observe: 09:10:45.129 [192.168.1.214:47530]: dimcon____geheugen-van-nederland QUERY(3) for $i in /record[@version = 0] order by $i/system/index return $i OK 0.06 ms 09:10:45.129 [192.168.1.214:47530]: dimcon____geheugen-van-nederland QUERY(3) OK 0.03 ms 09:13:23.155 [192.168.1.214:47530]: dimcon____geheugen-van-nederland ITER(3) Error: Connection reset 09:13:23.155 [192.168.1.214:47530]: dimcon____geheugen-van-nederland LOGOUT admin OK I looked up the code, and it looks as though the whole (?) query is cached in memory upon retrieval. Given the DB is over 1.2 GB in size, our client server has a hard time (it only has 1,5 GB of Xmx). Is there any preferred way of dealing with this? What I am going to do for the moment, I think, is to override or intercept the creation of the ClientQuery and make an implementation that has a different caching strategy. Another approach may probably be to limit the query output and implement some custom iteration behavior - but if it that can be handled directly at the query level, I think it would make things easier. Manuel

2 6

db:add and ADD logic
by Fabrice Etanchaud 22 May '12

22 May '12

Dear all at BaseX, I don't understand the ADD/db:add behaviour when adding two documents with the same name : previous document is not replaced, but copied, and I did not find a way to correct, and delete only one of the documents, because they all have the same name... So, thanks to the db:replace function, I wrote a updating function which emulates desired behaviour (that adds or replaces the document if it already exists in the database). But if I try to insert the same document twice with this function (in the same updating query), I still get two documents in the database, because function is 'updating' and because of the pending update list... Are db:XXX functions really 'updating' ? Is there a way to delete only one of the duplicated documents ? Thank you again for your fantastic job. Regards, Fabrice ETANCHAUD Senior Software Engineer edital Berkenlaan 1 B-1831 Brussels, Belgium <skype:fabrice.etanchaud?call> +32 2 716 32 32 general +32 2 716 32 20 fax fetanchaud(a)edital.com corsearch.com <http://www.corsearch.com/> | edital.com <http://www.edital.com/> <outbind://899-00000000E439C83B50BF17409D8C27B7AE0425AF07005AA868536216F 543BAB9422EAEA5338B00000011020900005AA868536216F543BAB9422EAEA5338B00000 13AA36B0000/cid:image001.gif@01CC0F02.2C91B6C0> Confidentiality Notice: This email and its attachments (if any) contain confidential information of the sender. The information is intended only for the use by the direct addressees of the original sender of this email. If you are not an intended recipient of the original sender (or responsible for delivering the message to such person), you are hereby notified that any review, disclosure, copying, distribution or the taking of any action in reliance of the contents of and attachments to this email is strictly prohibited. If you have received this email in error, please immediately notify the sender at the address shown herein and permanently delete any copies of this email (digital or paper) in your possession.

2 1

Returned mail: see transcript for details
by sandeep＠marlabs.com 21 May '12

21 May '12

The original message was received at Mon, 21 May 2012 11:27:17 -0500 from [65.1.203.108] ----- The following addresses had permanent fatal errors ----- basex-talk(a)mailman.uni-konstanz.de

1 0

http server and client mode
by Gilles CARRY 21 May '12

21 May '12

Hello, I cannot set the http server to use a distant DB. In the restxq.xqm file, I always get Using this: let $count := (count(db:open('logs')/top/session)) in restxq.xqm, I always get the error: Stopped at line 15, column 38 in /usr/share/tomcat/webapps/BaseX72/restxq.xqm: [BASX0003] Database 'logs' not found. On the web browser. Using a CLI from a distant server, I can access the 'logs' DB. The db:list() instruction returns nothing. In web.xml, I set org.basex.mode to "client" and "host" to the IP of my DB server. Something I don't understand is that in the below output (db:system()) I can see that "host" is present whereas "mode" is not. Credential are OK. Any clue? When in "client" mode, is "dbpath" useful? Thanks, Gilles. <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE top PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <top> <system> <generalinformation> <version>7.2</version> <usedmemory>21887 KB</usedmemory> </generalinformation> <mainoptions> <dbpath>/home/basex/BaseXData</dbpath> <debug>true</debug> <eventport>1985</eventport> <host>10.129.63.129</host> <httppath>/usr/share/tomcat/webapps/BaseX72/</httppath> <httpport>8984</httpport> <keepalive>0</keepalive> <lang>English</lang> <langkeys>false</langkeys> <nonproxyhosts></nonproxyhosts> <parallel>8</parallel> <port>1984</port> <proxyhost></proxyhost> <proxyport>80</proxyport> <repopath>/usr/share/tomcat/webapps/BaseX72//repo</repopath> <serverhost></serverhost> <serverport>1984</serverport> <stopport>8985</stopport> <timeout>0</timeout> </mainoptions> <options> <addarchives>true</addarchives> <addraw>false</addraw> <attrindex>true</attrindex> <autoflush>true</autoflush> <bindings></bindings> <cachequery>false</cachequery> <casesens>false</casesens> <catfile></catfile> <chop>true</chop> <compplan>true</compplan> <createfilter>*.xml</createfilter> <diacritics>false</diacritics> <dotcompact>false</dotcompact> <dotdisplay>true</dotdisplay> <dotplan>false</dotplan> <dotty>dotty</dotty> <dtd>false</dtd> <exporter></exporter> <forcecreate>false</forcecreate> <ftindex>false</ftindex> <htmlopt>html=false,omit-xml-declaration=false,method=xml,nons=false,nobogons=false,nodefaults=false,nocolons=false,norestart=false,ignorable=false,emptybogons=false,any=false,norootbogons=false,nocdata=false,lexical=false,encoding=utf-8</htmlopt> <intparse>true</intparse> <language>en</language> <lserror>0</lserror> <mainmem>false</mainmem> <maxcats>100</maxcats> <maxhits>-1</maxhits> <maxlen>96</maxlen> <maxstat>30</maxstat> <parser>xml</parser> <parseropt>encoding=UTF-8,flat=false,format=verbose,header=false,jsonml=false,lines=true,separator=comma</parseropt> <pathindex>true</pathindex> <queryinfo>false</queryinfo> <querypath></querypath> <runs>1</runs> <scoring>0</scoring> <serialize>true</serialize> <serializer></serializer> <skipcorrupt>false</skipcorrupt> <stemming>false</stemming> <stopwords></stopwords> <tailcalls>42</tailcalls> <textindex>true</textindex> <updindex>false</updindex> <wildcards>false</wildcards> <writeback>false</writeback> <xmlplan>false</xmlplan> <xquery3>true</xquery3> </options> </system> </top>

4 9

Use of XML Schema validation with BaseX [SEC=UNCLASSIFIED]
by Steve Cameron 21 May '12

21 May '12

Hi Just wondering if anyone has gone down this path, maybe via a Servlet filter? Thanks Stephen Cameron Antarctic Fisheries Computing and Database Support Provider Australian Antarctic Division Kingston, Tasmania [cid:image001.jpg@01CD374E.353A91A0] Phone: 03 62323571 ___________________________________________________________________________ Australian Antarctic Division - Commonwealth of Australia IMPORTANT: This transmission is intended for the addressee only. If you are not the intended recipient, you are notified that use or dissemination of this communication is strictly prohibited by Commonwealth law. If you have received this transmission in error, please notify the sender immediately by e-mail or by telephoning +61 3 6232 3209 and DELETE the message. Visit our web site at http://www.antarctica.gov.au/ ___________________________________________________________________________

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk May 2012