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

parse-xml removes CDATA in text content
by Erdal Karaca 25 Oct '13

25 Oct '13

Hi all, When using parse-xml(-fragment), wrapping CDATA sections are removed and the text content within the original CDATA is returned. For example: parse-xml-fragment("<newNode><data><![CDATA[{cdata}]]></data></newNode>") returns <newNode> <data>{cdata}</data> </newNode> But I need this: <newNode> <data><![CDATA[{cdata}]]></data> </newNode> Do I miss something? Thanks!

3 6

Full Text Module - ft:search function
by John Best 25 Oct '13

25 Oct '13

Dear Christian, The syntax of the ft:search is - *ft:search($db as xs:string, $terms as item()*, $options as item()) as text()** In the $options part, I have seen various options like - Any Word, All Words, Phrase (for Exact Phrase), fuzzy and wildcards. These are really very good features. I am using them extensively. But one thing, I think, is missing and that is the Window/Distance Options for proximity search. Can these options be implemented.. ?? -- Have a nice day JBest

3 5

Re: [basex-talk] suppressing pre-evaluating information in evaluate-chapter in query-info window of BaseX-GUI
by Christian Grün 25 Oct '13

25 Oct '13

Hi Rob, looking forward to your demo (..so this only occur when you are running a large code base?), Christian 2013/10/25 Rob Stapper <r.stapper(a)lijbrandt.nl>: > Hi Christian, > > 1) I just downloaded the latest 7.8 beta release and this issue also occurs > in this version. > 2) The issue also occurs even if I don't interrupt the program. > 3) I'll see if I can reproduce this issue in a demo-program which I'll send > you later. The program where this occurs is about 200 kB including modules. > Maybe this is why the issue occurs. > > Btw. I do like the map:serialize instruction in 7.8 version. I sure helps my > debugging this 200kB monster. However a good debugger would help much more > ;-)) ( sorry, old cow but I couldn't resist ) > > Regards, > Rob > > -----Oorspronkelijk bericht----- > Van: Christian Grün [mailto:christian.gruen@gmail.com] > Verzonden: vrijdag 25 oktober 2013 10:53 > Aan: Rob Stapper > CC: BaseX > Onderwerp: Re: [basex-talk] suppressing pre-evaluating information in > evaluate-chapter in query-info window of BaseX-GUI > > Hi Rob, > >> When using a trace-instruction, like this: let $dum := trace( >> $local:programName, 'programmaNaam: '), in a Xquery program in the >> BaseX-GUI >> >> I get pre-evaluating information of some functions mixed with my trace >> output in the Query-Info-window, see below. > > The Info View will always return both the evaluation and compilation info. > However, the output should be clearly separated: > _________________________________ > > Interrupted. > Evaluating: > - programmaNaam: D03084 > > Compiling: > - pre-evaluating function($911 as element(when)) as map(*) { ... > _________________________________ > > Did the mixup occur with the latest version or snapshot? And does the > problem also occur when you don’t interrupt the query. And my last > question: could you provide us with a little sample query that demonstrates > the issue (you can use prof:sleep(...) to delay the output)? > > Thanks, > Christian > > > >> To be able to follow the programflow, I only want to see my >> trace-output, in this case the programName. >> >> Can I suppress this extra pre-evaluating query info? >> >> >> >> This for your reply in advance. >> >> >> >> Kind regards , >> >> Rob Stapper >> >> ====================================================================== >> ====================================================================== >> == >> >> QUERY INFO WINDOW >> >> Error: >> >> Interrupted. >> >> Evaluating: >> >> - programmaNaam: D03084 >> >> - pre-evaluating function($911 as element(when)) as map(*) { >> function($evaluateStatement.valuedBranche as element(when)) as map(*) >> { >> cobol:selection.valuedBranche.constructor(db:node-id($evaluateStatemen >> t.valuedBranche), >> koopa:evaluateStatement.object.Value($evaluateStatement.valuedBranche) >> , >> $nestedStatements.processor($evaluateStatement.valuedBranche/nestedSta >> tements)) >> }($911) } >> >> - pre-evaluating function($912 as element(when)) as map(*) { >> function($evaluateStatement.valuedBranche as element(when)) as map(*) >> { >> cobol:selection.valuedBranche.constructor(db:node-id($evaluateStatemen >> t.valuedBranche), >> koopa:evaluateStatement.object.Value($evaluateStatement.valuedBranche) >> , >> $nestedStatements.processor($evaluateStatement.valuedBranche/nestedSta >> tements)) >> }($912) } >> >> - pre-evaluating function($913 as element(when)) as map(*) { >> function($evaluateStatement.valuedBranche as element(when)) as map(*) >> { >> cobol:selection.valuedBranche.constructor(db:node-id($evaluateStatemen >> t.valuedBranche), >> koopa:evaluateStatement.object.Value($evaluateStatement.valuedBranche) >> , >> $nestedStatements >> >> >> >> >> _______________________________________________ >> BaseX-Talk mailing list >> BaseX-Talk(a)mailman.uni-konstanz.de >> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >> >

1 0

suppressing pre-evaluating information in evaluate-chapter in query-info window of BaseX-GUI
by Rob Stapper 25 Oct '13

25 Oct '13

Hello, When using a trace-instruction, like this: let $dum := trace( $local:programName, 'programmaNaam: '), in a Xquery program in the BaseX-GUI I get pre-evaluating information of some functions mixed with my trace output in the Query-Info-window, see below. To be able to follow the programflow, I only want to see my trace-output, in this case the programName. Can I suppress this extra pre-evaluating query info? This for your reply in advance. Kind regards , Rob Stapper ============================================================================ ================================================================== QUERY INFO WINDOW Error: Interrupted. Evaluating: - programmaNaam: D03084 - pre-evaluating function($911 as element(when)) as map(*) { function($evaluateStatement.valuedBranche as element(when)) as map(*) { cobol:selection.valuedBranche.constructor(db:node-id($evaluateStatement.valu edBranche), koopa:evaluateStatement.object.Value($evaluateStatement.valuedBranche), $nestedStatements.processor($evaluateStatement.valuedBranche/nestedStatement s)) }($911) } - pre-evaluating function($912 as element(when)) as map(*) { function($evaluateStatement.valuedBranche as element(when)) as map(*) { cobol:selection.valuedBranche.constructor(db:node-id($evaluateStatement.valu edBranche), koopa:evaluateStatement.object.Value($evaluateStatement.valuedBranche), $nestedStatements.processor($evaluateStatement.valuedBranche/nestedStatement s)) }($912) } - pre-evaluating function($913 as element(when)) as map(*) { function($evaluateStatement.valuedBranche as element(when)) as map(*) { cobol:selection.valuedBranche.constructor(db:node-id($evaluateStatement.valu edBranche), koopa:evaluateStatement.object.Value($evaluateStatement.valuedBranche), $nestedStatements

2 1

Basex with Multithreading
by Erol Akarsu 24 Oct '13

24 Oct '13

I am working on crawling data. I can see it is taking a lot of time because xquery is pulling web pages one by one. But popular crawlers like apache Nutch has multithreading support so it can open multiple socket connections to multiple sites so that it can crawl very fast. Can we make add multithreading support basex? So it can run multiple xquery functions in parallel and then merge results? Initially, merging results can be done manually. At least, if we can distribute loads to different xquery functions, that would be great. Erol Akarsu

2 4

do not interpret text nodes as embedded expressions (Expecting '}' but found...)
by Erdal Karaca 23 Oct '13

23 Oct '13

Hi all, How can I process this query in basex: let $x := doc(<a>main(){int i = 0;}</a>) return replace value of node $x with "" There are text contents that contain, for example, c code with curly braces which I do not want to be interpreted as embeded expressions. As a workaround I could escape the curly braces, But, is there a better way/option to suppress interpreting text contents that look like embedded expressions? Thanks!

3 4

Out Of Main Memory error while creating BaseX DB
by elangovan MuthuSwamy 23 Oct '13

23 Oct '13

Hi All, I am using BaseX to evaluate Xpaths (Xqueries) for larger size of XML files. I have created BaseX database initially using *CreateDB*.execute(ctx) API. And every time when I need to evaluate Xpath I open database using Open("database name") API and get a context. Using this context I evaluate the xpath. Once I complete my evaluation I close the context using Close.execute(ctx) API. My application is running without any issues. If the server runs for few weeks, I have observed "Out Of Main memory error" while updating the BaseX database. Could any one please help me in this issue. Is there any possibility of memory leak in BaseX in my work flow? Note: I am using same CreateDB(...) API to update / overwrite the existing Database. XML file Size may vary from 3Mb to 10 Mb. -- Regards, Elango.

2 1

Cache compiled expressions for use with QueryProcessor
by Erdal Karaca 22 Oct '13

22 Oct '13

Hi all, We have lots of non dynamic (i.e. do not change at run-time) queries/expressions that are always parsed/compiled using a new QueryProcessor instance. How to cache compiled expressions for use with QueryProcessor? Or can we just cache QueryProcessor instances? If yes, are QueryProcessor instances thread-safe? Thanks!

2 4

java.nio.channels.OverlappingFileLockException
by EV Narasimham 21 Oct '13

21 Oct '13

Hi, I have 3 application modules. One module, creates the xml database, the second/third module execute queries on the database (no updates are being performed on the database). When the second and the third module try accessing the database, once module is able to query the database while the other module ends up with the below exception. org.basex.core.BaseXException: Improper use? Potential bug? Your feedback is welcome: Contact: basex-talk(a)mailman.uni-konstanz.de Version: BaseX 7.8 beta Java: Oracle Corporation, 1.7.0_25 OS: Linux, amd64 Stack Trace: java.nio.channels.OverlappingFileLockException at sun.nio.ch.SharedFileLockTable.checkList(FileLockTable.java:255) at sun.nio.ch.SharedFileLockTable.add(FileLockTable.java:152) at sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:1017) at org.basex.io.random.TableDiskAccess.lck(TableDiskAccess.java:183) at org.basex.io.random.TableDiskAccess.sharedLock(TableDiskAccess.java:170) at org.basex.io.random.TableDiskAccess.<init>(TableDiskAccess.java:83) at org.basex.data.DiskData.init(DiskData.java:122) at org.basex.data.DiskData.<init>(DiskData.java:92) at org.basex.core.cmd.Open.open(Open.java:68) at org.basex.core.cmd.Open.run(Open.java:35) at org.basex.core.Command.run(Command.java:344) at org.basex.core.Command.exec(Command.java:320) at org.basex.core.Command.execute(Command.java:77) at org.basex.core.Command.execute(Command.java:89) Below are the options being set: context.globalopts.set(GlobalOptions.GLOBALLOCK, false) ; context.globalopts.set(GlobalOptions.PARALLEL, 1) ; //After referring to https://github.com/BaseXdb/basex/issues/574<https://github.com/BaseXdb/basex/issues/574> When the same exercise is being undertaken on a windows machine, the above behavior does not occur. Regards Narasimham <https://github.com/BaseXdb/basex/issues/574>

2 2

Prefetch DOM root node (no lazy loading) using QueryProcessor command
by Erdal Karaca 19 Oct '13

19 Oct '13

Hi all, When querying a DOM Node (from DB on file system, i.e. no in memory DB) using QueryProcessor command: will the whole Node be fetched from the database or will parts of the Node's children still access the file system if not loaded yet? Thanks!

2 3