BaseX-Talk April 2014

basex-talk@mailman.uni-konstanz.de

40 participants
53 discussions

XQuery comments in Return clause?
by Hondros, Constantine (ELS-AMS) 09 Apr '14

09 Apr '14

Hi all, I can't tell if this is a bug or not. I commented out a line in my Return clause so that I could test performance. To my surprise, the comment was interpreted as part of the literal response, and the expression within the commented line was evaluated. If this is expected behaviour, is there a workaround? return <dup> <pii>{ $val }</pii> (: {/results/dataset/item[pii = $val]/dbpath} :) </dup> ---------------------- Result: ---------------------- <dup> <pii>0022-0728(92)80265-6</pii> (: <dbpath>SCODAT00000000001/15726657/v336i1-2/0022072892802657/main.xml</dbpath> <dbpath>SCODAT00000000002/15726657/v336i1-2/0022072892802656/main.xml</dbpath> :) </dup> <dup> ________________________________ Elsevier B.V. Registered Office: Radarweg 29, 1043 NX Amsterdam, The Netherlands, Registration No. 33156677, Registered in The Netherlands.

2 2

Efficient query for duplicates
by Hondros, Constantine (ELS-AMS) 09 Apr '14

09 Apr '14

I'm running out of memory (1.5 GB allocated) when querying for duplicate node values over a fairly flat XML database of approximately 450 MB. Can anyone suggest a more memory-efficient approach to framing this query than iterating over distinct-values as I do below? I'm hoping that there are some Basex tips and tricks to help out here. for $val in distinct-values(/dataset/item/pii) let $cnt := count(/dataset/item/pii[. = $val]) return if ($cnt > 1) then <duplicate>{$val}</duplicate> else null Thanks in advance, Constantine ________________________________ Elsevier B.V. Registered Office: Radarweg 29, 1043 NX Amsterdam, The Netherlands, Registration No. 33156677, Registered in The Netherlands.

3 4

Bulk Processing of JSON
by Shaun Flynn 09 Apr '14

09 Apr '14

Hello there, I am working in a project to work with train schedules. Sadly, the data is given to me as a series of JSON objects which need to be read in line by line. Is there a way of batch processing JSON, or do I have to submit line by line? Shaun

2 2

BaseX 7.8.2 Update - Soft-Files.com
by Soft-Files Team 08 Apr '14

08 Apr '14

Dear Developer, Your product BaseX 7.8.2 has been updated. Your product review page is located at: http://www.soft-files.com/basex_72311.html. Sincerely, The Soft-Files Team

1 0

Contribution
by Christian Baune 08 Apr '14

08 Apr '14

Hi, I made the begining of a Golang implementation for BaseX : https://github.com/programaths/go-basex Kind regards, Christian

2 1

Re: [basex-talk] JSON serialization via REST API
by Dirk Kirsten 08 Apr '14

08 Apr '14

Hi Florent, > I have some data in XML format with daily updates. I don't control > this data, they come to me as XML, I don't want to convert them and > make some mistakes, so I want to use a XML database. If I just add a > <json/> element as root, I fix nothing about the string/integer > conversion so I don't understand in what this is useful. And if XML > only has strings there's no problem to go to JSON, they become strings > in JSON ! While this might be true in your _specific_ case, it is not true in general. Even if you only have strings and don't care about numbers, other people do very much care about that. So we need to provide a mapping. Also the <json objects="json" /> element already adds mapping information, as it also could be <json arrays="json"/>. In the first case you get back an JSON object, in the latter one an array. How could we be able to determine that without any mapping information? You will never be able to do a totally automatical lossless JSON<>XML conversion. However, you are able to write your own mapping functions which are useful for your specific use case > I have seen RestXQ which is probably excellent but it can't help me, > because I just want a REST interface with JSON, so I can change my > backend without frontend modificiation if needed. I don't really get your argument here. RestXQ enables you to build a REST interface and you can in fact change your backend without any frontend modifications. In fact, it is much better at this job than the REST interface. As you already discovered, sometimes parameters in newer versions of BaseX change. Using REST you will have to update all REST calls in your frontend. Using RestXQ, you simply adopt your backend code. Also, you would not need all the format information in each and every REST call, as they would be defined in your backend RestXQ code. I agree with you that the new options syntax for JSON output might be more verbose in this case. But it also gives much more flexibility and is much easier to handle especially in a RestXQ context and I am very happy we have this new syntax. Please also keep in mind that the majority of our users are using RestXQ rather than REST. As I already indicated I personally don't see many good reasons to use REST instead of RestXQ for application development. Hence, I very much doubt that we will switch back to the old method=jsonml syntax. Cheers, Dirk -- Dirk Kirsten, BaseX GmbH, http://basex.org |-- Firmensitz: Blarerstrasse 56, 78462 Konstanz |-- Registergericht Freiburg, HRB: 708285, Geschäftsführer: | Dr. Christian Grün, Dr. Alexander Holupirek, Michael Seiferle `-- Phone: 0049 7531 28 28 676, Fax: 0049 7531 20 05 22

3 3

setting global options
by Jason Ricles 08 Apr '14

08 Apr '14

To whom it may concern, Is there any way to set the globaloptions of basex such as globallock? Since I currently keep executing *context.globalopts.set(GlobalOptions.GLOBALLOCK, true) ;* *System.out.println(context.globalopts.GLOBALLOCK);* and when the print statement executes, it says that globallock = false, even though I have set it to true. Sincerely, Jason R

2 1

Creating a Basex database directly from tarred XML?
by Hondros, Constantine (ELS-AMS) 08 Apr '14

08 Apr '14

Hello all, Is there a known workaround for creating a db from tarred XML using the Database -> New menu? I can always untar the tarfile first, but it would be sort-of nice just to point at the tarfile and load. TIA, Constantine ________________________________ Elsevier B.V. Registered Office: Radarweg 29, 1043 NX Amsterdam, The Netherlands, Registration No. 33156677, Registered in The Netherlands.

3 7

Re: [basex-talk] JSON serialization via REST API
by Florent Gallaire 08 Apr '14

08 Apr '14

Hello, > For me "json" serialization of XML (i.e. XML->JSON) is a false problem > because you don't lose informations, so the format=json should always > work. If you want to stay backward compatible, maybe a new value for > the format parameter like format=djson for dirtyjson could be useful ? I just realize that : "Version 7.8 Removed: json:parse-ml, json:serialize-ml Updated: json:parse now returns a document node instead of an element, or an XQuery map if format is set to map. Version 7.7.2 Updated: $options argument added to json:parse and json:serialize Updated: json:parse-ml and json:serialize-ml are now deprecated" So BaseX 7.7.2 and the depreciated method=jsonml is just working fine and doing what I want. http://localhost:8984/rest/factbook?query=//city/name&wrap=yes&method=jsonml Really, why have you removed that ? Because there is the new options argument...it's more complex but ok if knew how to use it with REST API, please help me ^^ : http://localhost:8984/rest/factbook?query=//city/name&wrap=yes&method=json&… Cheers Florent > Cheers > > Florent > > >> On 07/04/14 17:41, Florent Gallaire wrote: >>> Hello, >>> >>> I'm new in the XML databases world, evaluating BaseX and eXist-db for >>> a new project. >>> >>> BaseX seems really clean and lightweight. >>> >>> I would like to use it via the REST API and with a json output. >>> >>> I test with the factbook.xml example database and the method parameter >>> set to "json" : >>> http://localhost:8984/rest/factbook?query=//city/name&wrap=yes >>> works fine but >>> http://localhost:8984/rest/factbook?query=//city/name&wrap=yes&method=json >>> returns [BXJS0002] JSON serializer: <json> expected as root node. >>> >>> I don't understand why. I need json serialization whatever is the XML >>> returned by the query. >>> >>> And I don't understand how to use the json options via the REST API. >>> http://docs.basex.org/wiki/JSON_Module >>> An example could be fine to help. >>> >>> Best regards >>> >>> Florent >>> >> >> -- >> Dirk Kirsten, BaseX GmbH, http://basex.org >> |-- Firmensitz: Blarerstrasse 56, 78462 Konstanz >> |-- Registergericht Freiburg, HRB: 708285, Geschäftsführer: >> | Dr. Christian Grün, Dr. Alexander Holupirek, Michael Seiferle >> `-- Phone: 0049 7531 28 28 676, Fax: 0049 7531 20 05 22 > > > > -- > FLOSS Engineer & Lawyer -- FLOSS Engineer & Lawyer

1 1

April 4th release and WebDAV access = Data Access out of bound.
by France Baril 07 Apr '14

07 Apr '14

Hi, I get these errors with every DB access from XML Oxygen (through WebDAV). BaseX 7.8.2 [Server] Server was started (port: 1984) HTTP Server was started (port: 8984) Data Access out of bounds: - pre value: 51 - #used blocks: 1 - #total locks: 1 - access: 0 (1 > 0] com.bradmcevoy.http.exceptions.BadRequestException Data Access out of bounds: - pre value: 51 - #used blocks: 1 - #total locks: 1 - access: 0 (1 > 0] com.bradmcevoy.http.exceptions.BadRequestException Data Access out of bounds: - pre value: 51 - #used blocks: 1 - #total locks: 1 - access: 0 (1 > 0] com.bradmcevoy.http.exceptions.BadRequestException -- France Baril Architecte documentaire / Documentation architect france.baril(a)architextus.com (514) 572-0341

2 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk April 2014