BaseX-Talk March 2015

basex-talk@mailman.uni-konstanz.de

36 participants
58 discussions

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

Query Execution Taking Too Long...
by ankit kumar 23 Mar '15

23 Mar '15

Hi, I am trying to get all distinct start element '/products/p:category/start' nodes of a big file. I have written a query which is given below. It is taking to long to get the result. I am attaching the query info and the xml file. After Running couple of minutes, I stopped the execution. Query is trying to get all the distinct start elements There are 3 lac category elements. declare namespace functx = "http://www.functx.com"; declare namespace p="a:b:c"; declare function functx:is-node-in-sequence( $node as node()? , $seq as node()* ) as xs:boolean {some $nodeInSeq in $seq satisfies deep-equal($nodeInSeq,$node)}; declare function functx:distinct-nodes( $nodes as node()* large.xml <https://docs.google.com/file/d/0B_pB7l14skhVLWxvZGNyMnFwc0k/edit?usp=drive_…> ) as node()* {for $seq in (1 to count($nodes))return $nodes[$seq][not(functx:is-node-in-sequence(.,$nodes[position() < $seq]))]} ; let $diff_starts := functx:distinct-nodes(/products/p:category/start) return $diff_starts Please let me know if you require further details.

2 1

Issues posting/putting JSON content with markup in it via http module.
by James Wright 23 Mar '15

23 Mar '15

Hello everyone, First, I want to say that I really like the JSON improvements in BaseX 8.0. Great job. I am however having an issue when posting JSON with markup in it. For example: let $out := map { name: 'myView', markup: "<div name='value'>Some other stuff</div>" } http:send-request(<http:request method="POST" />, uri, $out) The issue is that the resulting JSON body being posted has the 'markup' property xml escaped. IE: { "name": "myView", "markup": "<div name='value'>Some other ..... " } I had a similar issue with file:write but resolved that by using file:write-string. I have tried calling json:serialize on $out manually as well as declaring the option output:method to 'json'. I even tried changing the request object by inserting a http:body. IE: <http:request method="GET"> <http:body content-type="application/json"> {json:serialize($out)} </http> </http> Lastly, I have tried declaring the cdata-section option: declare option output:cdata-section-elements 'http:body'; Still no go... Is this not possible? One option would be to serialize the content using file:write and then call curl. This is a workaround I have used in the past however I was hoping I was behind that now with the latest improvements to XQuery 3.1. Maybe I need to send the http:request object as a map instead of an xml node? Thanks again for your time on all of this. - James

2 2

Bug in evaluating conditionals? Not short-circuiting?
by Marc van Grootel 23 Mar '15

23 Mar '15

Hi, I think I found a bug in 8.0.3 (and earlier) declare function local:shortcircuit($a) { if ($a castable as xs:double and xs:double($a) gt 0) then $a else () }; local:shortcircuit('foo') => [FORG0001] Cannot cast to xs:double: "foo". In http://www.w3.org/TR/xpath/#booleans "An and expression is evaluated by evaluating each operand and converting its value to a boolean as if by a call to the boolean function. The result is true if both values are true and false otherwise. The right operand is not evaluated if the left operand evaluates to false." Haven't tested it for other conditionals. --Marc

2 1

My BaseX GUI shows huge font and icons after upgrade
by Kristian Kankainen 21 Mar '15

21 Mar '15

Hello! After updating BaseX I got a strange looking GUI. Most fonts and icons are huge as can be seen from the screen shot. I use Fedora 21 and the package from your OpenSUSE repo. Could it be some missing fonts or other depending packages? My package information: Installed Packages Name : basex Arch : noarch Version : 8.0.2 Release : 1.1 Size : 2.8 M Repo : installed From repo : home_basex_opensuse And the repo file is the following (as you provide) [home_basex_opensuse] name=BaseX openSUSE Build (Fedora_20) type=rpm-md baseurl=http://download.opensuse.org/repositories/home:/basex:/opensuse/Fed… gpgcheck=1 gpgkey=http://download.opensuse.org/repositories/home:/basex:/opensuse/Fedo… enabled=1 /etc/yum.repos.d/home_basex_opensuse.repo (END) Best regards Kristian K

1 0

Reading standard input
by Hans-Juergen Rennau 19 Mar '15

19 Mar '15

Dear BaseX team, if I understand the documentation correctly, the processing of standard input is currently restricted to "-i-", that is, reading standard input as an XML document providing the context item, e.g. so: myCmd | basex -i- -q //foo Nice, but how about standard input which corresponds, for example, to a JSON document or a CSV document? Wouldn't it be useful to be able to apply functions to standard input,. e.g. json:parse, csv:parse or simple fn:unparsed-text? Example use case: NAGIOS commands piping the output of a command into BaseX. Whereas the context item can have any item type, the command line option -i accepts only documents, and that is the problem. I experimented with the "declare context item" declaration, but it did not work. And, at any rate, I would appreciate the conciseness of using an atomic context item without having to add the "declare context item" declaration. One solution were a new command line option (e.g. -j) which represents the context item as xs:untypedAtomic, and which also understands "-" to denote standard input. Then one could do this: myCmd | basex -j- json:parse(.)//foo That would be very nice and broaden the scope of BaseX again by a meter or two. Cheers,Hans-Jürgen

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk March 2015