- BaseX-Talk - mailman.uni-konstanz.de

Reg : Group By In Xquery
by ChandraSekhar 19 Nov '13

19 Nov '13

Dear Basex Team, I am running XQuery using group by clause with large collection ,But I am getting out of main memory , it is taking huge memory to execute,our requirement should use the group by clause,Is their any alternate to group by.Please do the needful Thanks & regards Chandra Sekhar -- This message is for the intended recipient only. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of the information is strictly prohibited. __

2 1

Linear Algebra module in XQUERY ?
by jean-marc Mercier 18 Nov '13

18 Nov '13

Hi all, I was thinking about the opportunity of writing a basic linear algebra module in XQUERY (matrix / vector elementary computations, maybe up to cholesky decomposition), since I did not find any at present time. However, there are some little things that seems difficult to me. That could be nice to have opinions of more experimented XQUERY developers before starting trying to write it. Indeed, XQUERY might provide the two basics needs to write a good linear algebra modulus : - The first one is template programming. template programming is straightforward with XQUERY. - The second one is template expressions (see http://en.wikipedia.org/wiki/Expression_templates for a definition). I guess that such patterns are not too difficult to implement with XQUERY. However, the bad points seems to be the following ones. Maybe someone have some insight over these questions ? - I don't know how to allocate and address directly contiguous memory blocks in XQUERY. That is not a good point for performance issues, as working directly with such memory blocks drastically improves basic operations in copying objects (in linear algebra implementation, this is a key point to performance). - Immutability might result in a big overload in memory? This might not be true, see a recent thread over this topic (XQUERY for noobs). - I don't know how to overload the basic operators (*,+,-) with XQUERY. This may result in quite heavy notations like alg:prod($mat1,alg:minus($mat2,$mat3)) instead of $mat1*($mat2-$mat3). Notice however that there are alternatives to XQUERY, since some very good linear algebra modules exists, but written in imperative languages. I list some alternatives, however, it might not be a good idea to wrap a functional language like XQUERY to an imperative, not thread safe, external module (this point has been noticed to me by BaseX teams members). At my knowledge, UBLAS is very performant, flexible, and almost standardized one, but written in C++ http://www.boost.org/doc/libs/1_54_0/libs/numeric/ublas/doc/index.htm. I don't know how to bind C++ to JAVA, but it is certainly possible. However, I am wondering if this could be a good idea. Eigen is another quite interesting C++ implementation (less performant, but more complete). Indeed, it provides a JAVA wrapper, named JEIGEN. Thus it could suit most of my needs. Any suggestions welcome Regards, Jean-Marc

2 3

Grégoire Colbert vous invite à rejoindre Viadeo
by Grégoire Colbert 18 Nov '13

18 Nov '13

Rejoignez des millions de professionnels. Grégoire Colbert Ingénieur système d'information, Université européenne de Bretagne Voir son profil Bonjour, Je vous invite à rejoindre mon réseau de contacts sur Viadeo. Cordialement, Grégoire Confirmer que vous connaissez Grégoire Viadeo, le réseau de tous les professionnels. Retrouver vos collègues et camarades de classe. Echanger avec les professionnels de votre secteur Soigner votre image auprès des recruteurs. Inscrivez-vous Si vous ne souhaitez plus recevoir d'invitations de membres Viadeo, cliquez ici

1 0

Technical and commercial support informations about BaseX
by jean-marc Mercier 18 Nov '13

18 Nov '13

Hi, I'd like to start a thread regarding some technical and commercial support aspects of BaseX. The preliminary question is : is this mailing list the correct container for this topic ? regards, Jean-Marc

2 4

db:open(), xquery:eval(), and path()
by Imsieke, Gerrit, le-tex 17 Nov '13

17 Nov '13

I think that under certain conditions, the path() function does not return the proper paths. Here’s an example that works ok: for $doc in <doc><a/><c/></doc> let $nodes as element(*)* := xquery:eval("$doc//*", map{"doc":=$doc}) return for $node in $nodes return <result path="{path($node)}" name="{name($node)}"/> ⇒ <result path="Q{http://www.w3.org/2005/xpath-functions}root()/Q{}a[1]" name="a"/> <result path="Q{http://www.w3.org/2005/xpath-functions}root()/Q{}b[1]" name="b"/> <result path="Q{http://www.w3.org/2005/xpath-functions}root()/Q{}b[1]/Q{}c[1]" name="c"/> Now I create a database 'doc' with the document 'doc.xml' and invoke the slightly modified query: for $doc in db:open('doc', 'doc.xml')/* let $nodes as element(*)* := xquery:eval("$doc//*", map{"doc":=$doc}) return for $node in $nodes return <result path="{path($node)}" name="{name($node)}"/> ⇒ <result path="Q{http://www.w3.org/2005/xpath-functions}root()" name="a"/> <result path="Q{http://www.w3.org/2005/xpath-functions}root()" name="b"/> <result path="Q{http://www.w3.org/2005/xpath-functions}root()" name="c"/> The element names are still known, but not their paths. Is it a bug or am I missing something? Gerrit

2 5

how about use basex to manage the large quntity of personal health information files?
by easy 17 Nov '13

17 Nov '13

Hi, all I have a question consult with you, I want to plan using basex db to manage our cityizen EHR data( more than 500,0000 people),every people have more than 100 dataset xml file like: > ------------------ > <BasicDataset> > <DataSet code="HDSD00.01.01" codeSystem="WS365-2011" codeSystemName="城乡居民健康档案基本数据集"/> > <HDSN00.01.001 dataelementName="记录日期" value="20110411160000"/> > <HDSN00.01.002 dataelementName="记录者姓名" value="少华"/> > <HDSN00.01.003 dataelementName="记录人编号" value=""/> > <HDSN00.01.004 dataelementName="记录人联系电话" value="13518272323"/> > <HDSN00.01.005 dataelementName="记录人所属机构名称" value="卫生局"/> > <HDSN00.01.006 dataelementName="记录人所属机构代码" value="PDY87041051068311X1119"/> > <HDSN00.01.007 dataelementName="记录人所属机构地址" value="和路135号"/> > <HDSN00.01.008 dataelementName="文档保管机构名称" value="卫生局"/> > <HDSN00.01.009 dataelementName="文档保管机构代码" value="PDY87041051068311X1119"/> > <HDSN00.01.010 dataelementName="文档保管机构地址" value="路135号"/> > <HDSN00.01.011 dataelementName="文档保管机构联系电话" value="13518272323"/> > <HDSN00.01.012 dataelementName="" value=""/> > <HDSN00.01.013 dataelementName="文档编号" value="0000A28072174D28A92AC5716D39C544"/> > <HDSN00.01.014 dataelementName="文档生成日期" value="20131101195713"/> > <HDSN00.01.015 dataelementName="参与人电话" value="xxxxx"/> > <HDSN00.01.016 dataelementName="参与人姓名" value="华"/> > <HDSN00.01.032 dataelementName="源ID" value="0000A28072174D28A92AC5716D39C544"/> > <HDSD00.01.376 value=""/> > <HDSD00.01.377 value=""/> > <HDSD00.01.378 value=""/> > <HDSD00.01.379 value=""/> > <HDSD00.01.380 value=""/> > <HDSD00.01.381 value=""/> > <HDSD00.01.424 value=""/> > <HDSD00.01.008 value="18781045619"/> > <HDSD00.01.018 code="4" displayName="不详" codeSystem="CV07.10.003" codeSystemName="医疗费用来源类别代码表"/> > <HDSD00.01.041 code="1" displayName="卫生厕所" codeSystem="CV03.00.304" codeSystemName="厕所类别代码表"/> > <HDSD00.01.014 code="3" displayName="不详" codeSystem="" codeSystemName=""/> > <HDSD00.01.040 code="1" displayName="自来水" codeSystem="CV03.00.115" codeSystemName="饮水类别代码表"/> > <HDSD00.01.006 value="51062219500408121X"/> > <HDSD00.01.042 code="1" displayName="不详" codeSystem="" codeSystemName=""/> > <HDSD00.01.002 value="杨国安"/> > <HDSD00.01.013 code="5" displayName="不详" codeSystem="CV04.50.005" codeSystemName="ABO血型代码表"/> > <HDSD00.01.007 value="清泉村"/> > <HDSD00.01.019 value="true"/> > <HDSD00.01.009 value="唐公健"/> > <HDSD00.01.003 code="1" displayName="男" codeSystem="dicSex" codeSystemName="性别"/> > <HDSD00.01.017 code="2" displayName="已婚" codeSystem="dicMaritalStatus" codeSystemName="婚姻"/> > <HDSD00.01.001 value="51068310420305002501"/> > <HDSD00.01.010 value="13981093150"/> > <HDSD00.01.038 code="2" displayName="换气扇" codeSystem="CV03.00.302" codeSystemName="厨房排风设施类别代码表"/> > <HDSD00.01.030 value="false"/> > <HDSD00.01.024 value="false"/> > <HDSD00.01.015 code="1" displayName="研究生" codeSystem="dicEducational" codeSystemName="学历"/> > <HDSD00.01.027 value="false"/> > <HDSD00.01.039 code="1" displayName="液化气" codeSystem="CV03.00.303" codeSystemName="燃料类型类别代码表"/> > <HDSD00.01.016 code="5" displayName="农林牧渔水利业生产人员" codeSystem="Classifications" codeSystemName="职业"/> > <HDSD00.01.012 code="01" displayName="不详" codeSystem="dicNationality" codeSystemName="民族"/> > <HDSD00.0l.011 value="true"/> > <HDsD00.01.004 value="19500407160000"/> > <HDSD00.01.037 value="false"/> > <HDSD00.01.01.02> > <row/> > </HDSD00.01.01.02> > <HDSD00.01.01.03> > <row/> > </HDSD00.01.01.03> > <HDSD00.01.01.04> > <row/> > </HDSD00.01.01.04> > <HDSD00.01.01.06> > <row/> > </HDSD00.01.01.06> > <HDSD00.01.01.08> > <row/> > </HDSD00.01.01.08> > <HDSD00.01.01.09> > <row/> > </HDSD00.01.01.09> > <HDSD00.01.01.05> > <row/> > </HDSD00.01.01.05> > <HDSD00.01.01.07> > <row/> > </HDSD00.01.01.07> > </BasicDataset> > > ---------------------------- > > before, I used existdb to do this, but I found existdb is difficult ,query on large data often make system dead, so I want to know, the basex is better to do this, because I found basex can index much qucik, query response well, and do import data file quick, can you give me some advice? > > thanks. > -- 此致 easy 莫愁前路无知己，天下谁人不识君。

2 1

Collations and testing for attribute equality
by James Ball 15 Nov '13

15 Nov '13

Hello, I'm doing some work matching between XML documents - one set has no characters outside the basic ASCII range while the other has a mix of of Ø and Ö and lots of others. Some are in UPPER case and some in Mixed. I need to match a "James" in one file to "JAMES" in another and so on. To do the comparisons I've been looking at BaseX's support for collations. Following the example in the documentation like this works perfectly: declare default collation 'http://basex.org/collation?strength=primary'; "Straße" = "Strasse", "Jérome" = "Jerome", "James" = "JAMES" But it doesn't work when testing attribute (or node) values in a statement like this: declare default collation 'http://basex.org/collation?strength=primary'; let $doc := doc(' <root> <test name="Straße">Straße</test> <test name="Strasse">Strasse</test> </root> ') return count($doc/root/test[@name = "Strasse"]) I would expect that to return a count of 2 but it returns a count of 1. I can get round this by calling fn:compare() like this but it feels like a hack: declare default collation 'http://basex.org/collation?strength=primary'; let $doc := doc(' <root> <test name="Straße">Straße</test> <test name="Strasse">Strasse</test> </root> ') return count($doc/root/test[0=fn:compare(@name,"Strasse")]) Is this behaviour as intended? I can see that it might make query speed and indexes much better to ignore collation for = but I couldn't find it stated in the documentation. My quick read of the specification suggested that the operation of fn:compare would drive the behaviour of eq, gt, lt etc. I think that I'm probably doing this completely the wrong way and I should be using some of the other features of Full-Text but I'm not sure. If anyone can point me in the right direction I will be very grateful. Many thanks, James

3 3

how to get the data of a http post request?
by easy 15 Nov '13

15 Nov '13

hi,all, I can't find function in request module to get the request content. such as request:get-data(), any idea? -- 此致 easy 莫愁前路无知己，天下谁人不识君。

2 1

BaseX Scalability
by Martí Pàmies Solà 14 Nov '13

14 Nov '13

Hi, We are analysing BaseX as an option to store over 100 million xml documents, and one of our main concerns is, which scalability features it offers. We review at http://vschart.com/compare/basex/vs/exist-db that it is horizontal scalable but, on BaseX documentation portal we can not find it. Thanks, Martí.

2 1

XQUERY module for querying instance of XSD scheme ?
by jean-marc Mercier 14 Nov '13

14 Nov '13

Hi, I started to write an xquery module that performs basic operations over instances of XSD schemes. My needs are basics, I would like to list groups and abstract classes, or define automatic predicat like declare variable $XSD_scheme := doc("my_schem.xsd") declare function IsNodeOfGroup($node, $group as element(xsd:group)) as xs:boolean {..} declare function ListAbstractClassesOf($node as element()) as element(xsd:complexType)* {..} However, I guess that I am reinventing the wheel and such a module surely exists already. Has anybody heard about such a module ? Thanks, Jean-Marc

1 0

BaseX rest and PHP
by Lars Johnsen 13 Nov '13

13 Nov '13

Hi all This is a question for those with experience using PHP with BaseX and the rest interface. There is a peculiar case of lag for queries, and I wondered if it had to with how PHPdoes things, or if it is how BaseX does things (or if there is something else). This may be a long shot, but I still give it a try. The setup is fairly straight forward, with queries sent from a html-page via a PHPscript which places the call: file_get_contents(basex-rest-URL). The result is then sent back to the requesting html page. The problem is that this sometimes hangs: two or three queries then it stops or takes an awful lot of time. The peculiar thing is that the basex-rest-URL, when typed directly into browser address line, receives an immediate response, even while it is still being processed by the html-php-basex cycle. Sometimes the cycle gives an answer, sometimes not. The cycle do work when file_get_contents is directed towards an SQLite database, so it seems that there is something going on in the communication between PHP and BaseX. Any ideas? Regards Lars G Johnsen National Library of Norway

3 2

Multi threading doing slow process of Xquery Execution
by Pushpendra Singh Sengar 13 Nov '13

13 Nov '13

Hi All, I create a collection of 4.5 gb xml document. and process some Xquery in sequencial manner then it is taking adequate time to process all queries. But when I converting process to multi threading then it is taking more than 10 times of time. Please someone suggest what is the best way to process Xquey in multithreading model. MY code is following : Thread thread = new Thread(new XqueryProcessor( new Context(),"db1")); Thread thread1 = new Thread(new XqueryProcessor( new Context(),"db2")); Thread thread2 = new Thread(new XqueryProcessor( new Context(),"db3")); thread.start(); thread1.start(); thread2.start(); Xquery Processor has all queries which need to process. and db1, db2 ,db3 are basically same xml files three collection. -- Thanks & Regards , Pushpendra Singh

3 4

Xquery for noobs : the HashSet problem
by jean-marc Mercier 12 Nov '13

12 Nov '13

Hi, Following a recent discussion with BaseX team, here is a description of a problem that I don't know how to solve efficiently from within Xquery or BaseX Xquery extensions like map:module. Thus, any suggestion are welcomed ! The problem is the following : I want to write an XQUERY module called HashSet, implementing the XQUERY version of HashSet (I mean the JAVA object HashSet, or std::set in C++). An HashSet is indeed a map specialization. Thus a suggestion is to use the BaseX map:module. However, I don't know how to use it efficiently. The reasons are the following : This HashSet module 1) must expose a method "hashset:new()" to allocate memory dynamically. The map:module provides the function map:new, this point is ok, I can wrap that. 2) This module must expose a method "hashset:clear($hashset)" to de-allocate memory dynamically. The map:module provides the function map:remove, and I could remove all elements. However this point is ko for me, as, AFAIU (as far as I understand), map:remove copy an the references from a map object into a smaller map object. It does not dealllocate memory, leading to poor overall performances. 3) must expose a method "hashset:add($hashset,$element)" to add memory dynamically. Through map:module, the only possibility that I see is to wrap it as map:new($hashset, map:entry($element,$dummyboolean)). Here too, a in-memory copy is done, leading to poor overall performances. XQUERY is a very attractive langage to me. However, its very nature is to be a functional langage. The main inconvenients to working with XQUERY for me are : - first : its dynamic memory management (the in-memory printfoot of my XQUERY executables are usually tremendous). - second : it lacks powerful libraries, as complete math modules. However, I might miss something ? Do not hesitate to teach me some XQUERY basic ! Cheers JohnLeM

3 9

Replace node attribute value
by Thomas Knight 12 Nov '13

12 Nov '13

Hi everyone, I have a problem trying to replace the attribute value. For example, using factbook.xml: replace value of node attribute /mondial/country[@name='Austria']/@car_code with 'B' fails with: [XUDY0027] Replace target must not be empty. How should I be doing this? Thanks Tom

2 1

Request for information.
by yoann ponzo 12 Nov '13

12 Nov '13

3 4

Issue for JAVA Bindings for Basex 7.7
by jean-marc Mercier 11 Nov '13

11 Nov '13

Hi, To resume an exchange with BaseX members : The issue is JAVA Bindings for BAseX version <= 7.7, illustrated by the following XQUERY code import module namespace set = "java.util.HashSet";{ let $loop := for $i in 1 to 128 return set:add($i) let $loop := for $i in 1 to 128 return set:add($i) return set:size() } returning .. 129 (expected 128) Explanation : (courtesy by Christian Gruen) - The set:add function is no integer-specific function, so it allows all types of objects as argument. - This is why the XQuery item will not be explicitly cast to an integer; instead, the original Java XQuery Item object will be passed on to the Java function. - In BaseX, the first items of type xs:integer and in the range of 0-127 are cached<https://github.com/BaseXdb/basex/blob/master/basex-core/src/main/java/org/b…>. This means that if an integer like 84 is requested twice, the returned item will have the same reference in memory. - This is different for integers larger than 127: in this case, new references will be created. As XQuery items have nohashCode() function, their memory reference will be used when calculating the hash code. WorkAround : preferred : Last Stable Release 7.8 solves the issue. Other workaround : - Use the map:module to simulate HashSet (well, I do confess that I do not know how to achieve this) - wrap the JAVA Class in order to manage directly this issue (by forcing cast operation in your wrapper), then import your wrapper as a module in BAseX

2 1

dynamically evaluate XPath
by Imsieke, Gerrit, le-tex 11 Nov '13

11 Nov '13

I have a RESTXQ path/function that is supposed to retrieve a document fragment, restricted to an XPath expression that is given as a query parameter, i.e., as a string. The list of possible fragment XPaths has been calculated using path() by another function, and the user of a Web application may choose to retrieve any of the fragments. An example for such a path would be '/Q{http://www.tei-c.org/ns/1.0}TEI[1]/Q{http://www.tei-c.org/ns/1.0}text[1]/Q{http://www.tei-c.org/ns/1.0}front[1]/Q{http://www.tei-c.org/ns/1.0}div[3]'. Is there a better solution than the following, whose performance is of course quite poor (around 2 seconds execution time for the given documents)? I’m thinking of something like saxon:evaluate() or the XSLT 3 instruction xsl:evaluate. Maybe I’m just unaware of the obvious solution based upon XQuery 3 or a BaseX extension. Gerrit declare %rest:path("/content/fragment/{$db}/{$doc}") %rest:query-param("xpath", "{$xpath}") %rest:GET function page:get-frags( $db as xs:string, $doc as xs:string, $xpath as xs:string ) as item()* { <response> { for $doc in db:open($db, $doc) return $doc//*[path(.) eq $xpath] } </response> };

2 2

my first question: how to deal with the duplicated files in basex?
by easy 11 Nov '13

11 Nov '13

Hi,all, I found basex db can add same file in same db and collection many times, when I use doc('') func, there will be a error: database paths ..... pointed more than one document. how to avoid this?? -- 此致 easy 莫愁前路无知己，天下谁人不识君。

2 1

Feature request: output params for db:replace
by France Baril 09 Nov '13

09 Nov '13

Hi, I have a feature request. I have a nice file with just the correct indent, that I was able to create by adding the xml:space="preserve" attribute to the root before making my inserts. [From previous thread] Ex. <block xml:space="preserve"> <block>This is a test sentence.</block> </block> Note: I can't use the output indent = no declaration at the top of my query because I'm in a library module, and I need this function to stay there for sharing. Now, I can't save the content like this (with @xml:space). My DTD doesn't allow for xml:space="preserve", and I don't want it to. Authors can't get the correct indent (based on our DTD) in the editor as long as the xml:space="preserve" remains. If I apply: *let* *$clean-file* := *copy* *$copy* := *$new* *modify* (*delete* *node* *$copy*/*/* @xml:space*) *return **$copy* file:write('file.xml', $clean-file, $param), where param contains indent="no". It saves correctly, indicating that removing the @xml:space did not cause a the insertion of an indent space between and . However, the db:replace('db', 'path', $clean-file) function forces an indent on the content between the and the . Since this is a BaseX function, and not an XQuery fonction, I'm hoping we could get db:replace('db', 'path', $clean-file, $param), where param can include output params such as indent=no. Thank you! -- France Baril Architecte documentaire / Documentation architect france.baril(a)architextus.com (514) 572-0341

2 2

Re: [basex-talk] Writeback option
by Christian Grün 09 Nov '13

09 Nov '13

…I’ve made it an GitHub issue: https://github.com/BaseXdb/basex/issues/786 On Fri, Nov 8, 2013 at 5:31 PM, Christian Grün <christian.gruen(a)gmail.com> wrote: >> - Concerning your comment on using the WRITEBACK option only for single >> file data bases: debugging the basex server yields that when using more >> than one xml document (via the ADD command), the "original" field in the >> MetaData class is not set, thus the WRITEBACK operation does not write >> anything in these situations. > > …exactly. The original URI of added resources will not be stored in > the database, and the optional "original" string you mentioned refers > to the path of a single resource, which was added in the database > creation process. > >> - When raw files reside in the database (added via STORE commands) in >> addition to the single initial xml data file, then an error is thrown >> upon every xquery write statement stating: >> Stopped at .../backend/restxq/ajax/addmodel.xqm, 10/10: [FOUP0002] >> ".../backend/data/gallery.xml" could not be written. > > I agree that it would make sense to reduce the number of unwanted side > effects caused by the WRITEBACK option. I even think the best solution > is to only write back files when updating documents that have been > created within a query, e.g... > > delete node doc("file-on-disk.xml")//abc > > and disallow updates on database instances. > > Thanks, > Christian > > >> At the same time the file gallery.xml is in fact updated to reflect the >> write operations changes. >> >> >> Than you >> Stefan >> >> Am 06.11.13 19:58, schrieb Christian Grün: >>> Dear Stefan, >>> >>>> - My impression is that the WRITEBACK option only works for databases >>>> directly created from an initial input xml file (CREATE DB <name> >>>> <input.xml>). Is that true? My other tests involving ADD <file.xml> >>>> commands failed to write back inserted or deleted nodes. >>> >>> that’s correct: the WRITEBACK option is only recommendable if you are >>> working with single files. Usually, the EXPORT command is the better >>> choice for writing database contents back to files. >>> >>>> - I checked out the latest git version and noticed that the WRITEBACK >>>> option is not read from the .basex file anymore. In version 7.7.2 that I >>>> used for the other tests it was read. >>> >>> Thanks for the observation; I have committed a fix and uploaded a new >>> snapshot, which should fix the problem [1]. >>> >>> Christian >>> >>> [1] https://github.com/BaseXdb/basex/commit/2d618a18f4b2ad14cc17b15d155320a088f… >>> >>> >>>> Am 25.10.13 18:04, schrieb Dirk Kirsten: >>>>> Dear Stefan, >>>>> >>>>> please be aware that this is a english-speaking mailing list. As we want >>>>> most of our users to benefit from all questions and answers I'll stick >>>>> to english in my response (and aa your web page is in English as well I >>>>> guess it is no obstacle for you). >>>>> >>>>> Regarding your question about saving plain xml files: You can use the >>>>> Export Command (see https://docs.basex.org/wiki/Commands#EXPORT) to >>>>> export all your documents. You can e.g. use a cron job to export them >>>>> regularly. There also is a writeback option >>>>> (https://docs.basex.org/wiki/Options#WRITEBACK), which will update your >>>>> original input nodes. >>>>> >>>>> Secondly, regarding your question about empty WebDAV files: Please take >>>>> a look at a recent discussion on the list (see >>>>> https://mailman.uni-konstanz.de/pipermail/basex-talk/2013-September/005453.…), >>>>> which is about the same topic. Short answer: With another viewer it >>>>> should work. Computing the size is quite difficult as we store the data >>>>> in a special storage format to speed up querying. Seems like some >>>>> viewers don't like it if the file size isn't correct. >>>>> >>>>> Cheers, >>>>> Dirk >>>>> >>>>> On 25/10/13 17:27, Stefan Sechelmann wrote: >>>>>> Hallo, >>>>>> ich bin dabei BaseX für unser aktuelles Projekt zu evaluieren. Bis jetzt >>>>>> sieht alles danach aus als ob BaseX genau das ist wonach wir gesucht >>>>>> haben. Hier meine Fragen dazu: >>>>>> >>>>>> - Der Datenbankserver speichert seine XML-Daten optimiert in .basex >>>>>> Files. Gibt es die Möglichkeit den Server auch XML Files schreiben zu >>>>>> lassen (So wie er das mit raw Files tut), so dass ich alles auch ohne >>>>>> BaseX ansehen kann? Gibt es vielleicht einen automatischen Export? >>>>>> >>>>>> - Der Webdav-Support kommt mir unstabil vor. Wenn ich XML-Dateien >>>>>> kopiere sind diese danach teilweise leer oder werden vom Server als RAW >>>>>> erkannt. Ich benutze einen Mac und den Finder als Client. Sind das >>>>>> eventuell bekannte Probleme oder muss ich bei mir suchen? >>>>>> >>>>>> Vielen Dank >>>>>> Stefan Sechelmann >>>>>> >>>>> >>>> >>>> >>>> -- >>>> Stefan Sechelmann >>>> DFG-Forschungszentrum Matheon >>>> Mathematik für Schlüsseltechnologien >>>> Technische Universität Berlin >>>> Sekretariat MA 8-3 Tel. 030/314 29 486 >>>> Straße des 17. Juni 136 Fax 030/314 79 282 >>>> 10623 Berlin sechel(a)math.tu-berlin.de >>>> http://www.math.tu-berlin.de/~sechel >>>> >>>> >>>> _______________________________________________ >>>> BaseX-Talk mailing list >>>> BaseX-Talk(a)mailman.uni-konstanz.de >>>> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >>>> >> >> >> -- >> Stefan Sechelmann >> DFG-Forschungszentrum Matheon >> Mathematik für Schlüsseltechnologien >> Technische Universität Berlin >> Sekretariat MA 8-3 Tel. 030/314 29 486 >> Straße des 17. Juni 136 Fax 030/314 79 282 >> 10623 Berlin sechel(a)math.tu-berlin.de >> http://www.math.tu-berlin.de/~sechel

1 1

~webdav locks + server stop = conflicted locks
by France Baril 08 Nov '13

08 Nov '13

This Issue occurs when the server stops while files are open/locked: When basex starts it doesn't show lock icons on files the user had locked before the server stopped. When users tries to open a file oxygen says the file is locked, even though the current user owns the lock. In other words, the lock seems to be tracking something that doesn't survive sessions. To recover, we delete the webdav db + restart Oxygen. Granted, doing all check-ins prior to stopping the server for maintenance would be a best practice. But in case of an unexpected failure, since the lock are saved in ~webdav, is there anyway we could get back to the locks as set in ~webdav? -- France Baril Architecte documentaire / Documentation architect france.baril(a)architextus.com (514) 572-0341

3 3

Re: [basex-talk] xquery and hash:md5
by James Wright 07 Nov '13

07 Nov '13

Would this work $someDoc//@*/text() --- Original Message --- From: "buzz chopra" <buzz.chopra(a)gmail.com> Sent: November 2, 2013 11:38 PM To: "Dirk Kirsten" <dk(a)basex.org> Cc: "BaseX" <basex-talk(a)mailman.uni-konstanz.de> Subject: Re: [basex-talk] xquery and hash:md5 Hello Dirk, Yes in that case, the issue exists in the nature of our data - and my poor choice of the return value of fn:string as the content to hash. Our data looks like: <test guid="blah"> <e1 attr0="a" attr1="b"/> <e2 attr0="c" attr1="d" attr2="e"/> </test> As you state, fn:string behaves the way http://www.w3.org/TR/xpath-functions-30/#func-string says it should. i.e. the empty string is returned for the document above. I'll have to try and find something that returns all attribute values in each document. Thanks again for your help. Buzz On Fri, Nov 1, 2013 at 10:37 AM, Dirk Kirsten <dk(a)basex.org> wrote: > Hello Buzz, > > The result of string() depends on the kind of element as an input. For > an attribute value it will simply be the value of the attribute. For an > element node it will be a concatination of the node content and all > descendant nodes. So if string($r) for $r being an element node is > always empty I would guess it is an empty node (something like <reps > />), which will always yield an empty result. > > If you want to create different hashs for empty elements with different > attribute values you might want to do something like the following > > let $reps := fn:collection($coll)//reps > for $r at $lcv in $reps > let $l := string-join($r/@*, '') > let $hash := xs:hexBinary(hash:md5(fn:string($l))) > return <hash i="{$lcv}">{$hash}</hash> > > If this is not what you actually want to achieve it would be very > helpful to actually get a small example of your data (especiall the reps > nodes) to get an idea how it looks like. > > Cheers, > Dirk > > On 01/11/13 16:19, buzz chopra wrote: > > Dirk, > > > > Thank you for your quick response. > > > > Upon your suggestion (and prior to that) I checked that the values for $r > > are different. Indeed they are. But, what I didn't check until your > > suggestion is that the values of fn:string($r) are different. They in > fact > > are the same - thank you for your suggestion. > > > > Is it possible that there is some sort of type casting related issue > going > > on where I call fn:string($r)? > > > > I get different values for the hash of each attribute value when I select > > attributes in the collection like: > > > > let $reps := fn:collection($coll)//reps/@att0 > > for $r at $lcv in $reps > > let $hash := xs:hexBinary(hash:md5(fn:string($r))) > > return <hash i="{$lcv}">{$hash}</hash> > > > > > > when I select elements in the collection like: > > > > let $reps := fn:collection($coll)//reps > > for $r at $lcv in $reps > > let $hash := xs:hexBinary(hash:md5(fn:string($r))) > > return <hash i="{$lcv}">{$hash}</hash> > > > > I found that the value of fn:string($r) is blank for all values of $r > > (which are different) which is why the hash is the same. > > > > I appreciate your help. > > > > Buzz > > > > > > On Fri, Nov 1, 2013 at 2:52 AM, Dirk Kirsten <dk(a)basex.org> wrote: > > > >> Hello buzz, > >> > >> it is ok to also ask more general XQuery questions on this list. > >> > >> For testing I executed the following query: > >> > >> for $r in ("123", "234", "345") > >> let $hash := xs:hexBinary(hash:md5(fn:string($r))) > >> return $hash > >> > >> which yields different results for each value of $r. Are you absolutely > >> sure you have different values for $r (you can check using trace())? > >> Also, given they query I would be very suprised if indeed it shows the > >> same result. > >> > >> Cheers, > >> Dirk > >> > >> On 01/11/13 08:24, buzz chopra wrote: > >>> This may be a question better suited for an xquery forum but I'll start > >>> here since I'm using basex: > >>> > >>> Can someone suggest why I'd be getting the same result for the hash > call > >>> even though > >>> the content of $r should be changing? > >>> > >>> let $reps := fn:collection($coll)/Rep > >>> for $r at $lcv in $reps > >>> let $hash := xs:hexBinary(hash:md5(fn:string($r))) > >>> return <hash i="{$lcv}">{$hash}</hash> > >>> }; > >>> > >>> Please let me know if I should post this elsewhere (and please include > >>> where). > >>> > >>> Thanks in advance for any suggestions. > >>> > >>> Buzz > >>> > >>> > >>> > >>> _______________________________________________ > >>> 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 > >> _______________________________________________ > >> 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 > _______________________________________________ BaseX-Talk mailing list BaseX-Talk(a)mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk

1 0

Receiving user feedback (too much traffic for BaseX?)
by France Baril 07 Nov '13

07 Nov '13

Hi, Our online help offers a form to collect comments from end-users. We have a lot of users and when a new product hits the market, we get a lot of feedback. We have found that BaseX is unable to handle so many write operations. Is there a suggested setup/configuration to handle multiple write operations coming from http requests. Is it possible to queue them somehow? Or is it better to use a more traditional approach to feedback collection? I.e. use a different toolset? Right now, BaseX just goes blank (freeze) with all the feedback coming in. Expectations: Average 5 comments/minute, but bursts of 2 per second should not break anything. Dropping comments during bursts is acceptable to us for our current business case because we hope to identify the most important issues after a new product release/software upgrade. Major issues should come up often enough. Any suggestion would be appreciated. -- France Baril Architecte documentaire / Documentation architect france.baril(a)architextus.com (514) 572-0341

2 1

BaseX
by Stefan Sechelmann 06 Nov '13

06 Nov '13

Hallo, ich bin dabei BaseX für unser aktuelles Projekt zu evaluieren. Bis jetzt sieht alles danach aus als ob BaseX genau das ist wonach wir gesucht haben. Hier meine Fragen dazu: - Der Datenbankserver speichert seine XML-Daten optimiert in .basex Files. Gibt es die Möglichkeit den Server auch XML Files schreiben zu lassen (So wie er das mit raw Files tut), so dass ich alles auch ohne BaseX ansehen kann? Gibt es vielleicht einen automatischen Export? - Der Webdav-Support kommt mir unstabil vor. Wenn ich XML-Dateien kopiere sind diese danach teilweise leer oder werden vom Server als RAW erkannt. Ich benutze einen Mac und den Finder als Client. Sind das eventuell bekannte Probleme oder muss ich bei mir suchen? Vielen Dank Stefan Sechelmann -- Stefan Sechelmann DFG-Forschungszentrum Matheon Mathematik für Schlüsseltechnologien Technische Universität Berlin Sekretariat MA 8-3 Tel. 030/314 29 486 Straße des 17. Juni 136 Fax 030/314 79 282 10623 Berlin sechel(a)math.tu-berlin.de http://www.math.tu-berlin.de/~sechel

3 3

Adding WKT/WKB To Geo Module
by Zachary DeLuca 03 Nov '13

03 Nov '13

Hi All, apologies in advance for the long message, I have many documents that store WKB (base64-encoded) geometry data (going for speed not readability). I want to be able to do queries where I can use the geo predicate functions with the stored WKB geometry and a provided WKT geometry. Example: Sample document structure: <root><geoWKBdata type=xs:base64Binary/></root> Sample query: collection()/root[geo:intersects(*geo:fromWKB*(geoWKBData), * geo:fromWKT*("LINESTRING((0,0),(1,1))")) I have looked at the module code and the only problem is that all methods assume an input of GML. I don't want to just make functions to convert from WKB/WKT to GML on input because I think that would be very inefficient (slow). I could just hack something together for my own needs, but I would like some input so that ideally I can produce something good enough to contribute back to the project. Options: 1) Add copies of all methods to accept each possible encoding type (GML, WKB, WKT). I don't like this approach because it doesn't scale well, and I don't even know if it's possible? (Pretty sure you can't overload functions in XPath/XQuery) 2) Leave the Geo module the way it is and add "sister" modules for the additional encoding types. Yuck. 3) The only thing that makes sense, really. Define 3 new functions, *fromGML *, *fromBinary*, and *fromText* and change the signatures of all module functions to just accept Geometry objects. That way you can load your geometry however you want and then pass it to the desired function. I will also modify the functions *asText *and *asBinary *to accept a Geometry object, and add an additional *asGML* so that the many existing functions that already return GML (envelope, boundary, etc.) can instead return Geometry, and can then be converted as needed to the desired format. This should scale well too because if any future encoding formats are desired all you need to do is add *fromXYZ* and *asXYZ *functions. With these functions, you could also string together 2 calls to convert between any of the supported encoding types. Does this make sense? It seems easy enough, am I missing anything? Also, assume for a second that I implement #3. Refer to my sample document/query above. As I understand it, for each document in the collection, the back end will have to parse "LINESTRING((0,0),(1,1))" into a Geometry first in order to compare. Is there any way to make that happen only once for the duration of the query? Is it as easy as this?: let $data = geo:fromText("LINESTRING((0,0),(1,1))"); return collection()/root[geo:intersects(*geo:fromWKB*(geoWKBData), $data) This would work, right? (I'm new to XQuery, sorry) So, am I on the right track with this? Have I overlooked some absurdly simple solution to my problem? I would appreciate any and all input. As I said, I would like to go beyond meeting my own needs and actually get this into the code base. I'll leave you with this snippet taken from the EXPath Geo Module Spec: "The data model envisioned by EXPath Geo module is abstract in the sense that it may be possible for module implementers to support more than one encoding on input. Output data types are specified in GML and XML Schema, where appropriate. All that is necessary is that the input geometry be transformable to the model specified by OGC SF and supported by the EXPath implementation. -SNIP- *Implementations are not limited to GML, KML, nor even XML, on input. It is possible that geometries encoded as “Well Known Text”, GeoJSON, or even “Well Known Binary”, among other possibilities, could be supported by an implementation.*" Thanks, Zach

3 9

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk