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

GUI Editor, Code Completions
by Christian Grün 19 Nov '13

19 Nov '13

Dear followers, we are interested to get your opinion on the code completions that we’ve just added to the text editor of our BaseX GUI [1]. You are invited to propose templates that you are missing here! Many of you would probably love to have context-based code completions (such as all functions in the current context, etc.). All I can say is that this is indeed planned for a future version of BaseX. Beside that, we’ve just added an implementation of the upcoming EXPath Binary Module [2]. As usual, a new stable snapshot is available, which contains the new features [3]. Thanks all, Christian [1] http://docs.basex.org/wiki/Shortcuts#Code_Completions [2] http://docs.basex.org/wiki/Binary_Module [3] http://files.basex.org/releases/latest/

2 1

Is it right query using ft:search ?
by John Best 19 Nov '13

19 Nov '13

Hi Team, Below is my XML Structure - <Docs> <Doc> <DocTitle C="1"></DocTitle> <MainDesc></MainDesc> <FullDesc></FullDesc> </Doc> <Doc> <DocTitle C="2"></DocTitle> <MainDesc></MainDesc> <FullDesc></FullDesc> </Doc> ............ ............ </Docs> I have to search the Full Text DB of above documents with 3 different options - 1. Complete Document 2. Only in MainDesc (Main Description) 3. Only in FullDesc (Full Description) Below is the query, using ft:search, for the first options, mentioned above for $x in ft:search("docMaster", ("emf","waves"), map{'mode':='all words'})/ancestor::*:Doc return $x/DocTitle/text() Now, this is for the 2nd options, i.e; for MainDesc - for $x in ft:search("docMaster", ("emf","waves"), map{'mode':='all words'})/ancestor::*:Doc/MainDesc return $x/DocTitle/text() Is it right ? I am little bit confused.. -- Have a nice day JBest

2 1

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/><b><c/></b></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