BaseX-Talk March 2015

basex-talk@mailman.uni-konstanz.de

36 participants
58 discussions

GUI feature request "Add as import"
by Andy Bunce 03 Jan '16

03 Jan '16

Hi, I often find myself adding module imports in the GUI and I wonder if the following suggestion might speed up that process. Add a new menu item to the filelist right click context menu "Add as import" when the file selection is a XQuery module. The action would be to add a line to the current edit window source with import module namespace {$prefix} = '{$namespace}' at {$path}; Where $prefix and $namespace} are read from the source of the selected file, and $path is calculated from the relative path from the edit file source to the selected filelist source. The line would be inserted at a suitable place in the prologue or at the current location if that is too tricky. /Andy

2 4

Slow query
by Menashè Eliezer 03 Aug '15

03 Aug '15

Hello, I wonder if the attached query can be optimised. I'm attaching all relevant information. Basex 7.9, Debian, powerful server. This is just an example. The queries will be built based on a compilation of a search form. So reordering the conditions for having smaller subset right from the begging isn't relevant. Any help would be appreciated. 40 seconds are not acceptable. -- With kind regards, Menashè

2 45

Position of matched tokens in a full-text query
by Javier Couto 22 May '15

22 May '15

Hi, Sorry if this is too basic, but I’m trying to get the positions of the matched tokens in a full-text query, and I can’t find the way to do it. I imagine something like: for $sentence in //sentence where $sentence[text() contains text { ‘DNA', ‘oxidation' }] return <positions>ft:SOME-FUNCTION-FOR-TOKENS-POSITIONS($sentence[text() contains text { ‘DNA', ‘oxidation' }])</positions> Is this possible? Thank you in advance, Javier

3 10

Bug in declare base-uri
by Hans-Juergen Rennau 18 May '15

18 May '15

Dear BaseX team, I think there is a bug in the determination of the static base URI in the special case that a base URI declaration contains a relative URI equal to or starting with "..". Consider this declaration:declare base-uri ".."; The effect should be that relative URIs are resolved against the PARENT directory of the directory containing the query. If the query is located at, say, file:///a/b/c/query.xq, I would expect the static base-uri to be /a/b/, so that a URI like "abc.xml" would be resolved to file:///a/b/abc.xml. However, the static base URI as determined by BaseX in this case misses the trailing /, it is: file:///a/bThe effect is that a URI like "abc.xml" would be resolved to file:///a/abc.xmlIn other words: URIs are resolved against the "GRAND-PARENT" directory of the query. Final remark: the effect of resolving URIs against the parent directory of the query is achieved by the surprising base URI declaration: declare base-uri "."; which is not what I would expect. Conclusion: the way to achieve a resolving of relative URIs against the parent directory of the query should be achieved by the base URI declaration ".." - and no other value. Kind regards,Hans-Juergen Full example:Query ( file file:///projects/infospace/pcol/test.xq); declare base-uri ".."; declare variable $uri external; string-join(( 'query-file: file:///projects/infospace/pcol/test.xq', concat('static-base-uri: ', static-base-uri()), concat('resolve-uri("try.xml")=', resolve-uri("try.xml")) ), '
') Output:query-file: file:///projects/infospace/pcol/test.xq static-base-uri: file:///C:/projects/infospace resolve-uri("try.xml")=file:/C:/projects/try.xml

2 4

BaseX under JBoss 6.2
by Bondeson, Carl 07 Apr '15

07 Apr '15

I have a deployment that is using 2 instances of BaseX. The first is using the default ports, then second is using alternate ports. Deploying the war goes smoothly, and both instances get along. When attempting to disable the deployment using the management console the process never completes. In looking at the log file the following error was noted. 10:00:31.159 SERVER admin OK Server was started. 10:02:19.876 SERVER admin Error: File 'C:/Users/DPHPIL~1/AppData/Local/Temp/BaseXServer1984' could not be deleted. It seems that even though the second instance is using 1982 as the port, the default port is being in this transaction. The versions in use are 7.6 and 7.9. Is there something from a configuration standpoint that needs to be set in order for the shutdown process to use the correct, non-default port? Carl R Bondeson Systems Developer Department of Public Health Data Processing 410 Capitol Ave Hartford, CT 06134 Phone: 860-509-7434 carl.bondeson(a)ct.gov<mailto:carl.bondeson@ct.gov> [Description: DPH Logo - Keeping CT Healthy]<http://www.ct.gov/dph>

2 4

Used memory value
by Joseph 07 Apr '15

07 Apr '15

Hi, When I open Basex 8.3 GUI, the value of the used memory keeps growing up/changing fast, even though I do not do anything. Since this does not happen with Basex 7.9, is this due to Java? (I run Java 1.8.X) Thanks, Joseph

4 5

%unit:ignore broken since 8.0?
by Marc van Grootel 07 Apr '15

07 Apr '15

Hi, Could it be that %unit:ignore("message") is broken since 8.0. Whenever I use a message in the annotation my tests fail with this error message: <error line="149" column="21" type="bxerr:BASX0006"> <info>%unit:ignore: 1 argument supplied.</info> </error> When ("mesage") is removed the test is ok. Documentation let's me believe %unit:ignore("message") is still supported. --Marc

3 4

Truncated results
by Joseph 07 Apr '15

07 Apr '15

Hi, I have noticed that when using the update facility, for example the replace expression, results for a long file may be cut off. This however does not happen if I use the non-updating expression (copy/modify): does this make sense to you? Thanks. Joseph

2 2

xqdoc and basex system modules
by Andy Bunce 07 Apr '15

07 Apr '15

I am looking to generate documentation from the system module stubs in etc/modules.zip. I have two issues 1) There is an issue with inspect.xqm declare namespace xqdoc="http://www.xqdoc.org/1.0"; let $a:=inspect:xqdoc("inspect.xqm")//xqdoc:function[xqdoc:name='inspect:xqdoc']//xqdoc:description return parse-xml-fragment($a) Errors And xqdoc:description looks like <xqdoc:description xmlns:xqdoc="http://www.xqdoc.org/1.0"></code> and end with <code></code> , and tags start with <code>@</code> . xqDoc comments can be specified for main and library modules and variable and function declarations. <p>We have slightly extended the xqDoc conventions to do justice to the current status of XQuery (Schema: <a href=" http://files.basex.org/etc/xqdoc-1.1.30052013.xsd ">xqdoc-1.1.30052013.xsd</a>): </p> <ul> <li> an <code>&lt;xqdoc:annotations/&gt;</code> node is added to each variable or function that uses annotations. The xqdoc:annotation child nodes may have additional <code>xqdoc:literal</code> elements with <code>type</code> attributes (xs:string, xs:integer, xs:decimal, xs:double) and values. </li> <li> a single <code>&lt;xqdoc:namespaces/&gt;</code> node is added to the root element, which summarizes all prefixes and namespace URIs used or declared in the module. </li> <li> name and type elements are added to variables </li> </ul></xqdoc:description> A comment parsing/escaping issue? 2) inspect:xqdoc("array.xqm") and the same with map.xqm Function 'array:size' is in reserved namespace. I guess this is to be expected and maybe I should just ignore any modules in namespaces http://www.w3.org/... I guess it is a result of the code being compiled rather than just documented? /Andy

2 3

require performance improvement suggestion for large size xml
by ankit kumar 31 Mar '15

31 Mar '15

Hi , I am using BaseX for my XML base application. In my application user provides various data filtration criteria. After passing the data through all the filters resultant data is processed for evaluation. For each filter we have created corresponding xquery and output of each filter is passed as input to the next filter for further filtration. What I notice is query execution time except for the first query is very high. From query plan I observed that for the first query indexing was being applied but not for the rest. This may be the case as the subsequent queries where getting fired on the data(sequence created by preceding query) passed on by the previous filter. This was not observed when the xml file was of smaller size , but as I increased the size of xml to 300 MB each query started taking times in minutes. I tried following thing I fired all the filter queries on the database to take advantage of indexing and after every filter execution , I took intersection of output sequence generated by each filter to keep track of final filtered data. The problem with above solution is , intersection query between larger sequence of data started tacking time large amount of time. Is there a way I can increase the performance. Thanks, Ankit

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk March 2015