BaseX-Talk

basex-talk@mailman.uni-konstanz.de

1 participants
5252 discussions

Configuration File for Basexclient Connection Details?
by Eliot Kimber 25 Mar '15

25 Mar '15

Looking through the docs and trying to tests locally, it appears that the basexclient command does not use the USER or PASSWORD fields in .basex when run. That is, given this in my ~/.basex file: USER = admin PASSWORD = admin The basexclient command still prompts me for my credentials. Is this correct or am I missing a configuration option somewhere? What I'm looking for is the ability to call the basexclient command from git hooks without those scripts having to maintain their own configuration file for the connection details. Thanks, Eliot ————— Eliot Kimber, Owner Contrext, LLC http://contrext.com

2 4

Re: [basex-talk] Simple xQuery functions do not work as expected
by Goetz Heller 25 Mar '15

25 Mar '15

Hi Christian, the issue showed up again, this time outside of a function. The computer was only moderately charged, but the change of behavior occurred after I loaded a 25MB text file into Notepad++. Should I change something in the JVM settings? Kind regards, Goetz -----Ursprüngliche Nachricht----- Von: Christian Grün [mailto:christian.gruen@gmail.com] Gesendet: Mittwoch, 25. März 2015 11:27 An: Goetz Heller Betreff: Re: [basex-talk] Simple xQuery functions do not work as expected > P.S.: Please make sure that our conversation appears at BaseX-Talk since I'm receiving mails from other members of the community who do appear to not be informed about the current status. I continued to write directly to you, because your second e-mail was not directed to the list anymore. It makes perfectly sense to include the list as well. > > > -----Ursprüngliche Nachricht----- > Von: Christian Grün [mailto:christian.gruen@gmail.com] > Gesendet: Mittwoch, 25. März 2015 09:38 > An: Goetz Heller > Betreff: Re: [basex-talk] Simple xQuery functions do not work as > expected > >> However, I would not consider this issue as resolved. > > Obviously yes. > >> For me it is a hint that under heavy load (memory), such misbehavior might occur, and therefore some investigations make sense in my opinion. > > I was surprised to hear that a restart of your machine solved the problem, because the GUI is nothing else than a plain JVM instance with a low memory footprint (at least for queries like the one you sent to me). > > As I cannot remember to have encountered a similar problem, we rely on your feedback. Feel free to send us some more examples if the problem should decide to haunt you. > > Best, > Christian > > >> >> Kind regards, >> >> Goetz >> >> -----Ursprüngliche Nachricht----- >> Von: Christian Grün [mailto:christian.gruen@gmail.com] >> Gesendet: Dienstag, 24. März 2015 17:12 >> An: Goetz Heller >> Betreff: Re: [basex-talk] Simple xQuery functions do not work as >> expected >> >> I am using Windows as well. >> >> Does the problem also happen with the latest snapshot? Could you try the zip distribution? >> >> http://files.basex.org/releases/latest/ >> >> >> >> On Tue, Mar 24, 2015 at 5:07 PM, Goetz Heller <heller(a)hellerim.de> wrote: >>> Did you try it on the Windows platform already? Maybe there was a mistake when packaging. >>> >>> Kind regards, >>> >>> Goetz >>> >>> -----Ursprüngliche Nachricht----- >>> Von: Christian Grün [mailto:christian.gruen@gmail.com] >>> Gesendet: Dienstag, 24. März 2015 16:50 >>> An: Goetz Heller >>> Betreff: Re: [basex-talk] Simple xQuery functions do not work as >>> expected >>> >>> Strange. Do you possibly have an empty or out-dated database named "labels"? If yes, could you try to back up and delete it, and run the query again? >>> >>> >>> On Tue, Mar 24, 2015 at 4:45 PM, Goetz Heller <heller(a)hellerim.de> wrote: >>>> Hi Christian, >>>> >>>> here ist he complete output. Apparently, it's over-optimized: >>>> >>>> Result: >>>> >>>> <r>et | </r> >>>> >>>> >>>> Compiling: >>>> - pre-evaluating doc("C:\test\labels.xml") >>>> - applying attribute index for $key_0 >>>> - applying attribute index for "_and" >>>> - inlining local:getLabel#2 >>>> - removing redundant $key_4 as xs:string* cast. >>>> - removing redundant $lang_5 as xs:string* cast. >>>> - inlining $key_4 >>>> - inlining $lang_5 >>>> - removing unknown element/attribute TERM >>>> - pre-evaluating db:attribute("Labels", >>>> "_and")/self::*:label/parent::*:LABEL/()/text() >>>> - pre-evaluating ((: xs:string*, true :) ()) >>>> - simplifying flwor expression >>>> - inlining $retVal1_2 >>>> - inlining $retVal2_3 >>>> - simplifying flwor expression >>>> >>>> >>>> >>>> Query: >>>> declare variable $labels := doc('C:\test\labels.xml'); declare >>>> function local:getLabel( $key as xs:string*, $lang as xs:string* ) >>>> as >>>> xs:string* { $labels/LABELS/LABEL[@label = $key]/TERM[@LG = >>>> $lang]/text() }; let $retVal1 := $labels/LABELS/LABEL[@label = >>>> '_and']/TERM[@LG = 'FR']/text() let $retVal2 := >>>> local:getLabel('_and', >>>> 'FR') return <r>{$retVal1} | {$retVal2}</r> >>>> >>>> >>>> >>>> Optimized Query: >>>> element r { (db:attribute("Labels", >>>> "_and")/self::*:label/parent::*:LABEL/*:TERM[(@*:LG = "FR")]/text(), " >>>> | ", ()) } >>>> >>>> >>>> Result: >>>> - Hit(s): 1 Item >>>> - Updated: 0 Items >>>> - Printed: 12 Bytes >>>> - Read Locking: global >>>> - Write Locking: none >>>> >>>> >>>> Timing: >>>> - Parsing: 1.32 ms >>>> - Compiling: 154.5 ms >>>> - Evaluating: 0.43 ms >>>> - Printing: 0.01 ms >>>> - Total Time: 156.26 ms >>>> >>>> >>>> Query plan: >>>> <QueryPlan compiled="true"> >>>> <CElem> >>>> <QNm value="r" type="xs:QName"/> >>>> <IterPath> >>>> <ValueAccess data="Labels" type="ATTRIBUTE"> >>>> <Str value="_and" type="xs:string"/> >>>> </ValueAccess> >>>> <IterStep axis="self" test="*:label"/> >>>> <IterStep axis="parent" test="*:LABEL"/> >>>> <IterStep axis="child" test="*:TERM"> >>>> <CmpG op="="> >>>> <CachedPath> >>>> <IterStep axis="attribute" test="*:LG"/> >>>> </CachedPath> >>>> <Str value="FR" type="xs:string"/> >>>> </CmpG> >>>> </IterStep> >>>> <IterStep axis="child" test="text()"/> >>>> </IterPath> >>>> <Str value=" | " type="xs:string"/> >>>> <Empty size="0"/> >>>> </CElem> >>>> </QueryPlan> >>>> >>>> Kind regards, >>>> >>>> Goetz >>>> >>> >> >

3 6

Facing Problem With Max()
by ankit kumar 25 Mar '15

25 Mar '15

Hi, I am trying to get max value for a sequence of nodes using max(). I have a query which gives me a set of element and after that i get its max value. let $elements := (<date>10-02-2012</date>,<date>12-02-2012<date>); return max($element) I am expecting that it gives me 10-02-2012, while it is giving error "cannot cast to double '10-02-2012'. Thanks Ankit

2 1

Simple xQuery functions do not work as expected
by Goetz Heller 25 Mar '15

25 Mar '15

I tried to implement a simple Xml-based dictionary. Here is a fragment of the Xml data I’m using: <?xml version="1.0" encoding="utf-8"?> <LABELS> <LABEL label="_and"> <TERM LG="EN">and</TERM> <TERM LG="FR">et</TERM> <TERM LG="DE">und</TERM> <TERM LG="BG">и</TERM> <TERM LG="CS">a</TERM> <TERM LG="DA">og</TERM> <TERM LG="EL">και</TERM> <TERM LG="ES">y</TERM> <TERM LG="ET">ja</TERM> <TERM LG="FI">ja</TERM> <TERM LG="HU">és</TERM> <TERM LG="IT">e</TERM> <TERM LG="LT">ir</TERM> <TERM LG="LV">līdz</TERM> <TERM LG="MT">u</TERM> <TERM LG="NL">en</TERM> <TERM LG="PL">i</TERM> <TERM LG="PT">e</TERM> <TERM LG="RO">şi</TERM> <TERM LG="SK">a</TERM> <TERM LG="SL">in</TERM> <TERM LG="SV">och</TERM> </LABEL> </LABELS> Say it’s saved on C:\test\labels.xml. Now, I defined the following module: BEGIN_CODE>>> (:: default language:) declare variable $lang as xs:string := 'DE'; (:: dictionary :) declare variable $labels := doc('C:\test\Labels.xml'); (:: get localized label (default language) :) declare function local:getLabel( $key as xs:string* ) as xs:string* { $labels/LABELS/LABEL[compare(@label, $key) = 0]/TERM[compare(@LG, $lang) = 0]/text() }; (:: get localized label (specific language) :) declare function local:getLabel( $key as xs:string*, $lang as xs:string* ) as xs:string* { $labels/LABELS/LABEL[compare(@label, $key) = 0]/TERM[compare(@LG, $lang) = 0]/text() }; (:: get localized label (specific language) - debug version :) declare function local:getLabelDebug( $key as xs:string*, $lang as xs:string* ) { let $terms := $labels/LABELS/LABEL[compare(@label, $key) = 0]/TERM for $t in ($terms) return <t>{xs:string($t/@LG)}: {$t/text()} (comparison: {$t/@LG = $lang})</t> }; (: does not work as I expect: let $retVal := local:getLabel('_and', 'FR') because it returns nothing :) (: using "for $t in ($terms[compare(@LG, $lang) = 0])" yields empty result :) let $retVal := local:getLabelDebug('_and', 'FR') return <r>{$retVal}</r> <<<END_CODE The first function appears to work as expected. However, instead of “[@LG = $lang]” I had to use [compare(@LG, $lang) = 0]” – I don’t know why, but otherwise, it does not return any results. On the other hand, using “[@label = $key]” on the same line worked. The second function does not return anything at all. The debug version of the latter shows that all the needed information is in place. Obviously, usage of the same variable name globally and locally is not an issue (I’ve tried it out). What’s wrong with the code? Is there an issue with the current version (8.0.3)? My installation runs on a Windows 8.1 machine. Some help is appreciated. Kind regards, Goetz

3 2

GUI suggestion: no trace output when running tests
by Marc van Grootel 24 Mar '15

24 Mar '15

Hi, When running tests from the GUI I sometimes insert debugging code to figure out which tests fails or why. The current behavior of the GUI makes this impossible though because when tests are run this info is printed to the Query Info window but immediately after tests are run it prints the test summary overwriting the debugging info (such as trace output). Currently I then go to the command-line but it might be an idea to somehow keep the output generated during test run visible. Cheers, --Marc

2 1

Running basexclient Command From a Bash Script
by Eliot Kimber 24 Mar '15

24 Mar '15

I'm trying to implement agit commit hook that updates a BaseX database with updates committed to the git repo (the BaseX database is being used for search and link management). My script is here: https://github.com/dita-for-small-teams/dfst-git-commit-hooks/blob/develop/ post-commit The important code is: ---------- addOrUpdate="git diff HEAD^ HEAD --name-only --diff-filter=AM" # echo "Adding/Updating files:" for line in `${addOrUpdate}`; do cmd="basexclient -c \"OPEN ${basexDatabase};REPLACE ${line} ${topDir}/${line};EXIT\" ${basexOptions}" echo "Running cmd: ${cmd}" $($cmd) done --------- When I run the script I'm getting this response: Contrext01:docs ekimber$ ../../dita-for-small-teams/commit-hooks/git/post-commit Running cmd: basexclient -c "OPEN sample-project;REPLACE docs/topic-01.dita /Users/ekimber/workspace-dfst/dfst-sample-project/docs/docs/topic-01.dita;E XIT" -U admin -P admin -p 1984 -n localhost Stopped at , 1/6: Unknown command: "OPEN. Did you mean 'OPEN'? Contrext01:docs ekimber$ If I copy the command from the message and run it directly from the command line it works as expected. There must be some subtlety of using base in this context but my bash fu is weak and I have no idea what I'm doing wrong--I can't see any obvious user error but there must be one. Can anyone tell me what my bash scripting mistake is? Is there a better way to do this sort of scripted interaction with basex? It didn't appear that BaseX scripts provided a way to take parameters--if they could then I'd just call a .bxs script with the relevant parameters. Short of generating the script and then running it, I couldn't think of a simpler way to do what I want that just using the -c option on the basexclient command. Thanks, Eliot ————— Eliot Kimber, Owner Contrext, LLC http://contrext.com

3 4

get-current-user()
by Marc van Grootel 24 Mar '15

24 Mar '15

Hi, Maybe I'm missing something but I cannot find the XQuery way to get access to the logged in user from a web application using RESTXQ. The servlet request object has getRemoteUser and Exist, for example, has xmldb:get-current-user and Marklogic has xdmp:get-current-user. I don't need to know intricate user details just need the handle on the logged in / authenticated user (possibly from the servlet request object?) --Marc

2 3

BaseX GUI minor bug with Preferences dialog in v8.0.3
by Amanda Galtman 24 Mar '15

24 Mar '15

Hi, Here are reproduction steps for a bug I'm seeing in v8.0.3 on win64. The issue was present in v7.9, but not in 7.7.2. Those are the versions I happen to have installed; I don't know the exact version that introduced the issue. 1. Select Database > Open & Manage, select a database, and open it. 2. Select Options > Preferences. 3. Put the cursor in the Database Path edit field and type something. Your *first* keystroke is accepted, and then the Preferences dialog closes. The database that you opened in step 1 also seems to get closed. If you close the database before doing step 2, the issue does not occur. Amanda

2 2

Re: [basex-talk] Query Execution Taking Too Long...
by Leonard Wörteler 24 Mar '15

24 Mar '15

Hi Ankit (CC mailing list), Am 24.03.2015 um 06:57 schrieb ankit kumar: > We could have used distinct-values() But, in our case we would like to > distinguish on the basis of attributes values. also distinct-values() > will be treating values of <a>1</a> and <a>01</a> as different. . > For the later case will be using custom node-correspond function instead > of deep-equal which will be doing comparison between two nodes. the general problem is that grouping a set of elements where all you have is an equivalence predicate is always expensive to compute (i.e. quadratic in the size of the set). In order to speed up your use case you should therefore try to find some way to expose more information about the nodes to compare. If it is possible to generate an identifier for each node that can be used for comparisons, then efficient hash-based algorithms can be used (e.g. those in `group by` or `distinct-values(...)`). You could for example have a function `my:id($node)` so that `my:id($n1) eq my:id($n2)` holds iff `node-correspond($n1, $n2)` does. Then you can rewrite your query to run in linear time: declare namespace p="a:b:c"; declare namespace my="my://namespace"; declare function my:id($n) { (: your code here :) $n/string() }; for $start in /products/p:category/start group by $id := my:id($start) return $start[1] If you cannot generate such an ID, you can also use sorting to reduce running time. If you can define a comparison function `my:less-than($n1, $n2)` that sorts the nodes into an order where equivalent items are next to each other, you can first sort the sequence in O(n log n) time (e.g. using `hof:sort-with($seq, my:less-than#2)` in BaseX) and then merge the runs of equivalent nodes in linear time. Hope that helps, Leo

1 0

gui folder view delete
by Andy Bunce 24 Mar '15

24 Mar '15

Hi, In the GUI folder view I can delete nodes by selecting and using right click. But if I select a top level document name entry the UI prompts for delete confirmation but no delete occurs. /Andy

2 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk