BaseX-Talk

basex-talk@mailman.uni-konstanz.de

9 participants
5241 discussions

The Spot Provider invites you to check out Make Money Online
by The Spot Provider 17 May '11

17 May '11

I'm following Make Money Online and think you'll be interested in it as well. To check it out, follow the link below: http://thenetworkit.blogspot.com/?psinvite=ALRopfWTUpk6M4ceaH7CO7Vxq2zik9nt… "I wanted to see you this." ----- Google Friend Connect helps people with common interests discover interesting sites and interesting people. To learn more, visit http://www.google.com/friendconnect

1 0

BaseXServer.bat not respecting the -c"SET DBPATH ..." option?
by Jason Klassen 16 May '11

16 May '11

I'm trying to run a BaseX Server and have it read data from a different directory than the default. So I add the flag -c"SET DBPATH C:/Working/BaseXData;info". To make sure that no previous settings are corrupting it I renamed the old .basex file to something else so it wouldn't find it. The info shows me the Database Path is correct. C:\Working>C:\basex\bin\basexserver -p1985 -c"SET DBPATH C:/Working/BaseXData;info" Saving properties in "C:\Users\jklassen/.basex"... BaseX 6.6 [Server] Server was started. General Information Database Path: C:/Working/BaseXData Used Main Memory: 1154 KB Database Creation Whitespace Chopping: ON Entity Parsing: OFF Indexes Path Summary: ON Text Index: ON Attribute Index: ON Full-Text Index: OFF Upon running basexserver a new .basex file is created. The contents of my .basex file are # Property File. # You can set additional options at the end of the file. DBPATH = C:\Users\jklassen/BaseXData JAXRXPATH = C:\Users\jklassen/BaseXWeb LANG = English LANGKEYS = false HOST = localhost PORT = 1984 SERVERPORT = 1984 JAXRXPORT = 8984 TIMEOUT = 0 # User defined section You can see that it created the file using the default windows directory. (I'm on windows 7). I would be fine with it except for the fact that no matter what I specify in SET DBPATH the server is only accessing the default C:\Users\jklassen/BaseXData folder. It does correctly initiate on the 1985 port. If I change the file to read # Property File. # You can set additional options at the end of the file. DBPATH = C:/Working/BaseXData JAXRXPATH = C:\Users\jklassen/BaseXWeb LANG = English LANGKEYS = false HOST = localhost PORT = 1984 SERVERPORT = 1984 JAXRXPORT = 8984 TIMEOUT = 0 # User defined section It works and finds the data in the right directory. If I add the flag -c"SET DBPATH C:/FakeDirectory/BaseXData;info" it still works, even though the info shows the new database path, leading me to believe it's ignoring the command. The problem for me lies in the fact that I want two BaseX Servers running on the same machine. One on port 1984 for my backend app and one on port 1985 for my web app and I'd like them to use separate file directories. Is SET DBPATH the right way to accomplish this? ________________________________ Jason Klassen Protegra Business. Technology. Solutions. Office: 204-272-2290 www.protegra.com <http://www.protegra.com>

3 5

JSON output
by Erol Akarsu 16 May '11

16 May '11

Is there a way Basex server can send us JSON output instead of xml? Thanks On Wed, May 11, 2011 at 10:28 AM, Erol Akarsu <eakarsu(a)gmail.com> wrote: > I am filtering one big xml db that 800Mb stored into basex db already. > > When I write filtered data into a file, I am getting out of memory. > > I know basex is generating result filtered document in memory before > writing and facing memory error. > > Can basex write results block by block? > > Thanks > > > On Wed, May 4, 2011 at 9:38 AM, Erol Akarsu <eakarsu(a)gmail.com> wrote: > >> I tried to delete some nodes with "delete nodes .." xquery update command. >> It actually did what was requested. >> >> I checked the database size that is still same as previous one. I know the >> nodes deleted has a lot of data and I think database indexes would be >> adjusted accordingly. >> >> Then, I exported database as xml file and recreated db. I can see it has >> real size. >> >> My question is why DB is not adjusting indexes when nodes deleted? >> >> Thanks >> >> Erol Akarsu >> >> >> On Fri, Apr 29, 2011 at 9:23 AM, Erol Akarsu <eakarsu(a)gmail.com> wrote: >> >>> Hi, >>> >>> Have we thought on clustering basex servers so we can partition xml >>> documents? >>> >>> Here, I am only interested in a global partitioning: >>> >>> Let's say if we have xml document like this, I would like to partition >>> RECORDS content so that each host will have equal number of RECORD elements. >>> Then, we need to aggregate results of individual hosts. >>> Can we implement this simple clustering framework with Basex? >>> >>> >>> <RECORDS> >>> <RECORD> >>> ..... >>> </RECORD> >>> <RECORD> >>> ..... >>> </RECORD> >>> </RECORDS> >>> >>> On Mon, Apr 11, 2011 at 12:35 PM, Erol Akarsu <eakarsu(a)gmail.com> wrote: >>> >>>> Ok, >>>> >>>> I was able to run full text search with another XML Database. >>>> >>>> I am primarily interested in how Basex will play with big XML file >>>> Wikipedia. >>>> >>>> Actually, Database create of wikipedia is fine. But when I add full tet >>>> search and indexes for it, it always throws out of memory exception error. >>>> >>>> I have changed -Xmx with 6GB that is still not enough to generate >>>> indexes for Wikipedia. >>>> >>>> Can you help me on how to generate indexes with a machine that case 6GB >>>> for Basex process? >>>> >>>> Thanks >>>> >>>> Erol Akarsu >>>> >>>> >>>> >>>> On Sun, Apr 10, 2011 at 4:07 AM, Andreas Weiler < >>>> andreas.weiler(a)uni-konstanz.de> wrote: >>>> >>>>> Hi, >>>>> >>>>> the following query could work for you: >>>>> >>>>> declare namespace w="http://www.mediawiki.org/xml/export-0.5/"; >>>>> for $i in doc("enwiki-latest-pages-articles")//w:sitename >>>>> return $i[. contains text "Wikipedia"]/.. >>>>> >>>>> -- Andreas >>>>> >>>>> Am 09.04.2011 um 20:43 schrieb Erol Akarsu: >>>>> >>>>> Hi >>>>> >>>>> I am having difficulty in running full text operators. This script >>>>> gives siteinfo below >>>>> declare namespace w="http://www.mediawiki.org/xml/export-0.5/"; >>>>> let $d := fn:doc ("enwiki-latest-pages-articles") >>>>> return ($d//w:siteinfo)[1] >>>>> >>>>> But return $d//w:siteinfo[w:sitename contains text 'Wikipedia'] does >>>>> NOT give same node >>>>> Why "contains" ft operator behave incorrectly? I remember it was >>>>> working fine. I just dropped and recreated database and turn all indexes. >>>>> Can you help me? >>>>> Query info is here: >>>>> >>>>> Query: declare namespace w="http://www.mediawiki.org/xml/export-0.5/"; >>>>> Compiling: >>>>> - pre-evaluating fn:doc("enwiki-latest-pages-articles") >>>>> - adding text() step >>>>> - optimizing descendant-or-self step(s) >>>>> - removing path with no index results >>>>> - pre-evaluating (())[1] >>>>> - binding static variable $res >>>>> - pre-evaluating fn:doc("enwiki-latest-pages-articles") >>>>> - binding static variable $d >>>>> - adding text() step >>>>> - optimizing descendant-or-self step(s) >>>>> - removing path with no index results >>>>> - simplifying flwor expression >>>>> Result: () >>>>> Timing: >>>>> - Parsing: 0.46 ms >>>>> - Compiling: 0.42 ms >>>>> - Evaluating: 0.17 ms >>>>> - Printing: 0.1 ms >>>>> - Total Time: 1.15 ms >>>>> Query plan: >>>>> <sequence size="0"/> >>>>> >>>>> >>>>> >>>>> <siteinfo xmlns="http://www.mediawiki.org/xml/export-0.5/" xmlns:xsi=" >>>>> http://www.w3.org/2001/XMLSchema-instance"> >>>>> <sitename>Wikipedia</sitename> >>>>> <base>http://en.wikipedia.org/wiki/Main_Page</base> >>>>> <generator>MediaWiki 1.17wmf1</generator> >>>>> <case>first-letter</case> >>>>> <namespaces> >>>>> <namespace key="-2" case="first-letter">Media</namespace> >>>>> <namespace key="-1" case="first-letter">Special</namespace> >>>>> <namespace key="0" case="first-letter"/> >>>>> <namespace key="1" case="first-letter">Talk</namespace> >>>>> <namespace key="2" case="first-letter">User</namespace> >>>>> <namespace key="3" case="first-letter">User talk</namespace> >>>>> <namespace key="4" case="first-letter">Wikipedia</namespace> >>>>> <namespace key="5" case="first-letter">Wikipedia talk</namespace> >>>>> <namespace key="6" case="first-letter">File</namespace> >>>>> <namespace key="7" case="first-letter">File talk</namespace> >>>>> <namespace key="8" case="first-letter">MediaWiki</namespace> >>>>> <namespace key="9" case="first-letter">MediaWiki talk</namespace> >>>>> <namespace key="10" case="first-letter">Template</namespace> >>>>> <namespace key="11" case="first-letter">Template talk</namespace> >>>>> <namespace key="12" case="first-letter">Help</namespace> >>>>> <namespace key="13" case="first-letter">Help talk</namespace> >>>>> <namespace key="14" case="first-letter">Category</namespace> >>>>> <namespace key="15" case="first-letter">Category talk</namespace> >>>>> <namespace key="100" case="first-letter">Portal</namespace> >>>>> <namespace key="101" case="first-letter">Portal talk</namespace> >>>>> <namespace key="108" case="first-letter">Book</namespace> >>>>> <namespace key="109" case="first-letter">Book talk</namespace> >>>>> </namespaces> >>>>> </siteinfo> >>>>> >>>>> On Mon, Apr 4, 2011 at 7:31 AM, Erol Akarsu <eakarsu(a)gmail.com> wrote: >>>>> >>>>>> I imported wikipedia xml into basex and tried to search it. >>>>>> >>>>>> But searching it takes longer. >>>>>> >>>>>> I tried to search one element that is first child of whole document >>>>>> and it took 52 sec. >>>>>> I know the XML file is very big 31GB. How can I optimize the search? >>>>>> >>>>>> declare namespace w="http://www.mediawiki.org/xml/export-0.5/"; >>>>>> >>>>>> let $d := fn:doc ("enwiki-latest-pages-articles")//w:siteinfo >>>>>> return $d >>>>>> >>>>>> Database info: >>>>>> >>>>>> > open enwiki-latest-pages-articles >>>>>> Database 'enwiki-latest-pages-articles' opened in 778.49 ms. >>>>>> > info database >>>>>> Database Properties >>>>>> Name: enwiki-latest-pages-articles >>>>>> Size: 23356 MB >>>>>> Nodes: 228090153 >>>>>> Height: 6 >>>>>> >>>>>> Database Creation >>>>>> Path: /mnt/hgfs/C/tmp/enwiki-latest-pages-articles.xml >>>>>> Time Stamp: 03.04.2011 12:29:15 >>>>>> Input Size: 30025 MB >>>>>> Encoding: UTF-8 >>>>>> Documents: 1 >>>>>> Whitespace Chopping: ON >>>>>> Entity Parsing: OFF >>>>>> >>>>>> Indexes >>>>>> Up-to-date: true >>>>>> Path Summary: ON >>>>>> Text Index: ON >>>>>> Attribute Index: ON >>>>>> Full-Text Index: OFF >>>>>> > >>>>>> >>>>>> >>>>>> Timing info: >>>>>> >>>>>> Query: declare namespace w="http://www.mediawiki.org/xml/export-0.5/ >>>>>> "; >>>>>> Compiling: >>>>>> - pre-evaluating fn:doc("enwiki-latest-pages-articles") >>>>>> - optimizing descendant-or-self step(s) >>>>>> - binding static variable $d >>>>>> - removing variable $d >>>>>> - simplifying flwor expression >>>>>> Result: element siteinfo { ... } >>>>>> Timing: >>>>>> - Parsing: 1.4 ms >>>>>> - Compiling: 52599.0 ms >>>>>> - Evaluating: 0.28 ms >>>>>> - Printing: 0.62 ms >>>>>> - Total Time: 52601.32 ms >>>>>> Query plan: >>>>>> <DBNode name="enwiki-latest-pages-articles" pre="5"/> >>>>>> >>>>>> >>>>>> >>>>>> Result of query: >>>>>> >>>>>> <siteinfo xmlns="http://www.mediawiki.org/xml/export-0.5/" >>>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> >>>>>> <sitename>Wikipedia</sitename> >>>>>> <base>http://en.wikipedia.org/wiki/Main_Page</base> >>>>>> <generator>MediaWiki 1.17wmf1</generator> >>>>>> <case>first-letter</case> >>>>>> <namespaces> >>>>>> <namespace key="-2" case="first-letter">Media</namespace> >>>>>> <namespace key="-1" case="first-letter">Special</namespace> >>>>>> <namespace key="0" case="first-letter"/> >>>>>> <namespace key="1" case="first-letter">Talk</namespace> >>>>>> <namespace key="2" case="first-letter">User</namespace> >>>>>> <namespace key="3" case="first-letter">User talk</namespace> >>>>>> <namespace key="4" case="first-letter">Wikipedia</namespace> >>>>>> <namespace key="5" case="first-letter">Wikipedia talk</namespace> >>>>>> <namespace key="6" case="first-letter">File</namespace> >>>>>> <namespace key="7" case="first-letter">File talk</namespace> >>>>>> <namespace key="8" case="first-letter">MediaWiki</namespace> >>>>>> <namespace key="9" case="first-letter">MediaWiki talk</namespace> >>>>>> <namespace key="10" case="first-letter">Template</namespace> >>>>>> <namespace key="11" case="first-letter">Template talk</namespace> >>>>>> <namespace key="12" case="first-letter">Help</namespace> >>>>>> <namespace key="13" case="first-letter">Help talk</namespace> >>>>>> <namespace key="14" case="first-letter">Category</namespace> >>>>>> <namespace key="15" case="first-letter">Category talk</namespace> >>>>>> <namespace key="100" case="first-letter">Portal</namespace> >>>>>> <namespace key="101" case="first-letter">Portal talk</namespace> >>>>>> <namespace key="108" case="first-letter">Book</namespace> >>>>>> <namespace key="109" case="first-letter">Book talk</namespace> >>>>>> </namespaces> >>>>>> </siteinfo> >>>>>> >>>>>> >>>>>> >>>>>> Thanks >>>>>> >>>>>> Erol Akarsu >>>>>> >>>>>> >>>>> _______________________________________________ >>>>> BaseX-Talk mailing list >>>>> BaseX-Talk(a)mailman.uni-konstanz.de >>>>> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >>>>> >>>>> >>>>> >>>> >>> >> >

4 8

BaseX 6.6.2 in Debian unstable
by Alexander Holupirek 16 May '11

16 May '11

Hi folks, just a little follow-up to the latest Linuxtag release 6.6.2. Since the beginning of May, BaseX is available via the official Debian GNU/Linux[1] unstable and testing repositories[2]. Th current state of BaseX @ Debian GNU/Linux [3] is: stable - no basex package testing - basex version 6.6.1 [4] unstable - basex version 6.6.2 [5] So, for all familiar with the Debian package system, a simple # aptitude install basex will enrich your system with BaseX and four new commands (including man pages) will be available: * basex .......... Standalone local XML database. Command line interface. * basexgui ....... Standalone local XML database. Graphical user interface. * basexserver .... BaseX XML Database Server. * basexclient .... BaseX XML Database Client. Regarding future BaseX versions, '# aptitude update && aptitude upgrade' will pull in new versions automagically and no further downloads on your side are required. Hooray! Alex PS: If you encounter problems with the Debian basex package or spot unclean integration of BaseX into your Debian system, please file a bug against the basex package using the Debian Bug report system [6]. [1] http://www.debian.org/ [2] http://packages.debian.org/search?keywords=basex [3] http://packages.debian.org/sid/basex [4] http://packages.debian.org/en/source/testing/basex [5] http://packages.debian.org/en/source/sid/basex [6] http://www.debian.org/Bugs/Reporting -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Alexander Holupirek |-- http://www.informatik.uni-konstanz.de/~holupire |-- Database & Information Systems Group, U Konstanz `-- Room E 209, 0049 7531 88 4449 (phone) 3577 (fax)

1 0

Two Questions
by José Angel 14 May '11

14 May '11

Hi peole, i have two questions, i don't know if you can help me. First: Which file describes the grammar of XQuery in BaseX?. Im trying to extend it and i need to modify the grammar. Second: I created a new type called xs:truth, i need to modify the casting rules from this type with other types like xs:boolean or xs:decimal, which files should i modify for this? Thanks for your time!. -- José Angel Labbad Estudiante de Ingeniería de la Computación Universidad Simón Bolívar.

3 5

Problem with omit-xml-declaration during update operation
by David Reichle 13 May '11

13 May '11

I'm trying to do an update operation on a file using standalone cmdline basex. The xml-declaration get printed to stdout instead of to the updated file. $cat test.xml <?xml version="1.0" encoding="UTF-8"?> <root> <test/> </root> $cat test.xq declare option output:omit-xml-declaration "no"; let $root := doc("test.xml")/root return insert node <test/> into $root $basex -u test.xq $cat test.xml <root> <test/> <test/> </root> The declaration gets removed :<

3 5

out of memory with file:write
by Erol Akarsu 11 May '11

11 May '11

I am filtering one big xml db that 800Mb stored into basex db already. When I write filtered data into a file, I am getting out of memory. I know basex is generating result filtered document in memory before writing and facing memory error. Can basex write results block by block? Thanks On Wed, May 4, 2011 at 9:38 AM, Erol Akarsu <eakarsu(a)gmail.com> wrote: > I tried to delete some nodes with "delete nodes .." xquery update command. > It actually did what was requested. > > I checked the database size that is still same as previous one. I know the > nodes deleted has a lot of data and I think database indexes would be > adjusted accordingly. > > Then, I exported database as xml file and recreated db. I can see it has > real size. > > My question is why DB is not adjusting indexes when nodes deleted? > > Thanks > > Erol Akarsu > > > On Fri, Apr 29, 2011 at 9:23 AM, Erol Akarsu <eakarsu(a)gmail.com> wrote: > >> Hi, >> >> Have we thought on clustering basex servers so we can partition xml >> documents? >> >> Here, I am only interested in a global partitioning: >> >> Let's say if we have xml document like this, I would like to partition >> RECORDS content so that each host will have equal number of RECORD elements. >> Then, we need to aggregate results of individual hosts. >> Can we implement this simple clustering framework with Basex? >> >> >> <RECORDS> >> <RECORD> >> ..... >> </RECORD> >> <RECORD> >> ..... >> </RECORD> >> </RECORDS> >> >> On Mon, Apr 11, 2011 at 12:35 PM, Erol Akarsu <eakarsu(a)gmail.com> wrote: >> >>> Ok, >>> >>> I was able to run full text search with another XML Database. >>> >>> I am primarily interested in how Basex will play with big XML file >>> Wikipedia. >>> >>> Actually, Database create of wikipedia is fine. But when I add full tet >>> search and indexes for it, it always throws out of memory exception error. >>> >>> I have changed -Xmx with 6GB that is still not enough to generate indexes >>> for Wikipedia. >>> >>> Can you help me on how to generate indexes with a machine that case 6GB >>> for Basex process? >>> >>> Thanks >>> >>> Erol Akarsu >>> >>> >>> >>> On Sun, Apr 10, 2011 at 4:07 AM, Andreas Weiler < >>> andreas.weiler(a)uni-konstanz.de> wrote: >>> >>>> Hi, >>>> >>>> the following query could work for you: >>>> >>>> declare namespace w="http://www.mediawiki.org/xml/export-0.5/"; >>>> for $i in doc("enwiki-latest-pages-articles")//w:sitename >>>> return $i[. contains text "Wikipedia"]/.. >>>> >>>> -- Andreas >>>> >>>> Am 09.04.2011 um 20:43 schrieb Erol Akarsu: >>>> >>>> Hi >>>> >>>> I am having difficulty in running full text operators. This script gives >>>> siteinfo below >>>> declare namespace w="http://www.mediawiki.org/xml/export-0.5/"; >>>> let $d := fn:doc ("enwiki-latest-pages-articles") >>>> return ($d//w:siteinfo)[1] >>>> >>>> But return $d//w:siteinfo[w:sitename contains text 'Wikipedia'] does >>>> NOT give same node >>>> Why "contains" ft operator behave incorrectly? I remember it was working >>>> fine. I just dropped and recreated database and turn all indexes. Can you >>>> help me? >>>> Query info is here: >>>> >>>> Query: declare namespace w="http://www.mediawiki.org/xml/export-0.5/"; >>>> Compiling: >>>> - pre-evaluating fn:doc("enwiki-latest-pages-articles") >>>> - adding text() step >>>> - optimizing descendant-or-self step(s) >>>> - removing path with no index results >>>> - pre-evaluating (())[1] >>>> - binding static variable $res >>>> - pre-evaluating fn:doc("enwiki-latest-pages-articles") >>>> - binding static variable $d >>>> - adding text() step >>>> - optimizing descendant-or-self step(s) >>>> - removing path with no index results >>>> - simplifying flwor expression >>>> Result: () >>>> Timing: >>>> - Parsing: 0.46 ms >>>> - Compiling: 0.42 ms >>>> - Evaluating: 0.17 ms >>>> - Printing: 0.1 ms >>>> - Total Time: 1.15 ms >>>> Query plan: >>>> <sequence size="0"/> >>>> >>>> >>>> >>>> <siteinfo xmlns="http://www.mediawiki.org/xml/export-0.5/" xmlns:xsi=" >>>> http://www.w3.org/2001/XMLSchema-instance"> >>>> <sitename>Wikipedia</sitename> >>>> <base>http://en.wikipedia.org/wiki/Main_Page</base> >>>> <generator>MediaWiki 1.17wmf1</generator> >>>> <case>first-letter</case> >>>> <namespaces> >>>> <namespace key="-2" case="first-letter">Media</namespace> >>>> <namespace key="-1" case="first-letter">Special</namespace> >>>> <namespace key="0" case="first-letter"/> >>>> <namespace key="1" case="first-letter">Talk</namespace> >>>> <namespace key="2" case="first-letter">User</namespace> >>>> <namespace key="3" case="first-letter">User talk</namespace> >>>> <namespace key="4" case="first-letter">Wikipedia</namespace> >>>> <namespace key="5" case="first-letter">Wikipedia talk</namespace> >>>> <namespace key="6" case="first-letter">File</namespace> >>>> <namespace key="7" case="first-letter">File talk</namespace> >>>> <namespace key="8" case="first-letter">MediaWiki</namespace> >>>> <namespace key="9" case="first-letter">MediaWiki talk</namespace> >>>> <namespace key="10" case="first-letter">Template</namespace> >>>> <namespace key="11" case="first-letter">Template talk</namespace> >>>> <namespace key="12" case="first-letter">Help</namespace> >>>> <namespace key="13" case="first-letter">Help talk</namespace> >>>> <namespace key="14" case="first-letter">Category</namespace> >>>> <namespace key="15" case="first-letter">Category talk</namespace> >>>> <namespace key="100" case="first-letter">Portal</namespace> >>>> <namespace key="101" case="first-letter">Portal talk</namespace> >>>> <namespace key="108" case="first-letter">Book</namespace> >>>> <namespace key="109" case="first-letter">Book talk</namespace> >>>> </namespaces> >>>> </siteinfo> >>>> >>>> On Mon, Apr 4, 2011 at 7:31 AM, Erol Akarsu <eakarsu(a)gmail.com> wrote: >>>> >>>>> I imported wikipedia xml into basex and tried to search it. >>>>> >>>>> But searching it takes longer. >>>>> >>>>> I tried to search one element that is first child of whole document and >>>>> it took 52 sec. >>>>> I know the XML file is very big 31GB. How can I optimize the search? >>>>> >>>>> declare namespace w="http://www.mediawiki.org/xml/export-0.5/"; >>>>> >>>>> let $d := fn:doc ("enwiki-latest-pages-articles")//w:siteinfo >>>>> return $d >>>>> >>>>> Database info: >>>>> >>>>> > open enwiki-latest-pages-articles >>>>> Database 'enwiki-latest-pages-articles' opened in 778.49 ms. >>>>> > info database >>>>> Database Properties >>>>> Name: enwiki-latest-pages-articles >>>>> Size: 23356 MB >>>>> Nodes: 228090153 >>>>> Height: 6 >>>>> >>>>> Database Creation >>>>> Path: /mnt/hgfs/C/tmp/enwiki-latest-pages-articles.xml >>>>> Time Stamp: 03.04.2011 12:29:15 >>>>> Input Size: 30025 MB >>>>> Encoding: UTF-8 >>>>> Documents: 1 >>>>> Whitespace Chopping: ON >>>>> Entity Parsing: OFF >>>>> >>>>> Indexes >>>>> Up-to-date: true >>>>> Path Summary: ON >>>>> Text Index: ON >>>>> Attribute Index: ON >>>>> Full-Text Index: OFF >>>>> > >>>>> >>>>> >>>>> Timing info: >>>>> >>>>> Query: declare namespace w="http://www.mediawiki.org/xml/export-0.5/"; >>>>> Compiling: >>>>> - pre-evaluating fn:doc("enwiki-latest-pages-articles") >>>>> - optimizing descendant-or-self step(s) >>>>> - binding static variable $d >>>>> - removing variable $d >>>>> - simplifying flwor expression >>>>> Result: element siteinfo { ... } >>>>> Timing: >>>>> - Parsing: 1.4 ms >>>>> - Compiling: 52599.0 ms >>>>> - Evaluating: 0.28 ms >>>>> - Printing: 0.62 ms >>>>> - Total Time: 52601.32 ms >>>>> Query plan: >>>>> <DBNode name="enwiki-latest-pages-articles" pre="5"/> >>>>> >>>>> >>>>> >>>>> Result of query: >>>>> >>>>> <siteinfo xmlns="http://www.mediawiki.org/xml/export-0.5/" xmlns:xsi=" >>>>> http://www.w3.org/2001/XMLSchema-instance"> >>>>> <sitename>Wikipedia</sitename> >>>>> <base>http://en.wikipedia.org/wiki/Main_Page</base> >>>>> <generator>MediaWiki 1.17wmf1</generator> >>>>> <case>first-letter</case> >>>>> <namespaces> >>>>> <namespace key="-2" case="first-letter">Media</namespace> >>>>> <namespace key="-1" case="first-letter">Special</namespace> >>>>> <namespace key="0" case="first-letter"/> >>>>> <namespace key="1" case="first-letter">Talk</namespace> >>>>> <namespace key="2" case="first-letter">User</namespace> >>>>> <namespace key="3" case="first-letter">User talk</namespace> >>>>> <namespace key="4" case="first-letter">Wikipedia</namespace> >>>>> <namespace key="5" case="first-letter">Wikipedia talk</namespace> >>>>> <namespace key="6" case="first-letter">File</namespace> >>>>> <namespace key="7" case="first-letter">File talk</namespace> >>>>> <namespace key="8" case="first-letter">MediaWiki</namespace> >>>>> <namespace key="9" case="first-letter">MediaWiki talk</namespace> >>>>> <namespace key="10" case="first-letter">Template</namespace> >>>>> <namespace key="11" case="first-letter">Template talk</namespace> >>>>> <namespace key="12" case="first-letter">Help</namespace> >>>>> <namespace key="13" case="first-letter">Help talk</namespace> >>>>> <namespace key="14" case="first-letter">Category</namespace> >>>>> <namespace key="15" case="first-letter">Category talk</namespace> >>>>> <namespace key="100" case="first-letter">Portal</namespace> >>>>> <namespace key="101" case="first-letter">Portal talk</namespace> >>>>> <namespace key="108" case="first-letter">Book</namespace> >>>>> <namespace key="109" case="first-letter">Book talk</namespace> >>>>> </namespaces> >>>>> </siteinfo> >>>>> >>>>> >>>>> >>>>> Thanks >>>>> >>>>> Erol Akarsu >>>>> >>>>> >>>> _______________________________________________ >>>> BaseX-Talk mailing list >>>> BaseX-Talk(a)mailman.uni-konstanz.de >>>> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >>>> >>>> >>>> >>> >> >

2 1

Incorrect implementation of XQUF?
by Computer Software Developer 11 May '11

11 May '11

Hi, I have a collection MyData/Test and another collection MyData/Real. I have the following XML occurring about five times in total, 4 times in collection MyData/Test and once in MyData/Real: <APPLICATION> <APPLICATION_ID>1</APPLICATION_ID> </APPLICATION> When I seek to delete this application only from MyData/Test using updating xquery like so: xquery version "1.0"; declare namespace fn="http://www.w3.org/2005/xpath-functions"; let $dataSet := 'Test' let $databaseName := 'MyData' let $applicationID := '1' let $finalURL := fn:concat($databaseName, "/",$dataSet) let $applicationsModified := <APP-DATA-ROOT xmlns:xforms="http://www.w3.org/2002/xforms"> <APPLICATION> <APPLICATION_ID>2</APPLICATION_ID> </APPLICATION> </APP-DATA-ROOT> for $all in fn:collection($finalURL) for $anApp in $all/APPLICATION[APPLICATION_ID=$applicationID] return ( delete nodes $anApp ) The application gets deleted from MyData/Real collection as well! Moreover, an insert statement to insert an APPLICATION element in the return block above, such insert statement placed after the deletion statement above, does not appear to insert anything.

2 4

Expected usage of map:map in BaseX 6.6.2
by Jan Vlčinský (CAD) 09 May '11

09 May '11

Hi Nice to have again new update of BaseX. In past I had some performance problems, when I had to process one document, enriching the elements by data from another database. I have a traffic-feed document, containing elements loc-id, referencing to detailed location description. Detailed location description is located in another document, which we call PredefinedLocationSet. In some cases we have about 11000 locations or even more, total size of open PredefinedLocationSet document is about 8 MB. Traffic feed can in some cases be of similar nature (the same number of "records" and the same size). My task was to return (not to modify) traffic feed with detailed location description embedded. All my xqueries, trying to accomplish something like that, seemed to me rather slow, regardless of my attempts to find any sort of optimization. I wonder, if map:map approach is something, what has a chance to be faster. Any technical background, hints or ideas are welcome. My idea is to start my xquery by building up map from PredefinedLocationSet (using loc-id as the key) and then run through traffic-feed to get loc-id, find related location details and return enriched "record". With best regards Jan Vlcinsky *Ing. Jan Vlčinský* CAD programy Slunečnicová 338/3, 734 01 Karviná Ráj, Czech Republic tel: +420-597 602 024; mob: +420-608 979 040 skype: janvlcinsky; GoogleTalk: jan.vlcinsky(a)gmail.com http://cz.linkedin.com/in/vlcinsky 2011/5/9 Christian Grün <christian.gruen(a)gmail.com> > Dear all, > > XQuery: > [ADD] map expressions and functions added: > http://docs.basex.org/wiki/Map_Functions >

1 0

BaseX 6.6.2: LinuxTag Release
by Christian Grün 09 May '11

09 May '11

Dear all, once more we are glad to release a new version of BaseX, aligned with the LinuxTag Event in Berlin/Germany, which offers the following features: API: [ADD] JAX-RX API now supports basic user authentication: http://docs.basex.org/wiki/JAX-RX_API [ADD] The COPY creates identical database copies: http://docs.basex.org/wiki/Commands [ADD] The OPTIMIZE ALL command minimizes all database structures: http://docs.basex.org/wiki/Commands XQuery: [ADD] map expressions and functions added: http://docs.basex.org/wiki/Map_Functions [MOD] File module aligned with latest EXPath specification: http://docs.basex.org/wiki/File_Functions [MOD] Speedup of full-text queries with keyword lists. Example: $x contains text { 'a', 'b', 'c', ...} [MOD] XQuery Update optimizations for replacing nodes; tree-aware updates. [MOD] XQuery optimizations to avoid materialization of sequences. GUI: [ADD] Multiple editor tabs added [ADD] Database management: copy databases Core: [ADD] Internal XML parser: HTML entities added [FIX] Glob syntax: support for multiple file suffixes Your feedback is welcome as usual; have fun, Christian BaseX Team

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk