BaseX-Talk February 2012

basex-talk@mailman.uni-konstanz.de

38 participants
52 discussions

gui vs. server
by Cerstin Mahlow 13 Feb '12

13 Feb '12

Hi, when displaying search results, I would like to show more or less following and preceding nodes depending on the fond node name. This works fine in the GUI using this XQuery: for $i at $p in //*[text() contains text ('Kopf' ftand 'Sand' ftand 'stecken')][self::*:p or self::*:l] let $pre := $i/preceding-sibling::*[position()<8] let $suc := $i/following-sibling::*[position()<8] return <div> {if (string(fn:node-name($i)) = "l") then $pre else "P"} {ft:mark($i [text() contains text ('Kopf' ftand 'Sand' ftand 'stecken')]) } {if (string(fn:node-name($i)) = "l") then $suc else "P"} </div> For "l"-nodes I get preceding and following nodes, for "p" nodes the "P" will be printed. However, when running the same on the server using a perl client (applying quoting for variables), I get the "P" for p-nodes but nothing for "l"-nodes. The conditional expression is correct, if I replace then $pre with then <p>LLL</p> everything works fine, "<p>LLL</p>" will be printed. If I skip the condition and allow preceding and following nodes for every $i, I get preceding and following nodes for "p"-nodes only, but not for "l"-nodes -- there is simple nothing. Is there any difference between GUI and Server? I use BaseX 7.1 beta, but I got the same effect with the BaseX 7.1 stable. Best regards Cerstin -- Dr. phil. Cerstin Mahlow Universität Basel Deutsches Seminar Nadelberg 4 4051 Basel Schweiz Tel: +41 61 267 07 65 Fax: +41 61 267 34 40 Mail: cerstin.mahlow(a)unibas.ch Web: http://www.oldphras.net

1 1

Problem in GUI BaseX 7.1
by Isidre Guixà 13 Feb '12

13 Feb '12

Hello I see the GUI 7.1 does not allow add and remove documents!!! I attach images clearer Thanks! Isidre

2 1

Problem with XMLDB in BaseX 7.0.2 and 7.1.1
by Isidre Guixà 11 Feb '12

11 Feb '12

Hello I'm trying examples XMLDB to access BaseX and none of the 3 (XMLDBCreate, XMLDBInsert, XMLDBQuery) work ok. All have the same error: Exception in thread "main" java.lang.AbstractMethodError: org.basex.api.xmldb.BXDatabase.getNames()[Ljava/lang/String; at org.xmldb.api.DatabaseManager.registerDatabase(Unknown Source) at proves.XMLDBCreate.main(XMLDBCreate.java:31) I tried it in 7.0.2 and 7.1.1 versions. Is there any solution? I found the same error reported on March 2011 for BaseX users and the response of Michael Seiferlein https://mailman.uni-konstanz.de/pipermail/basex-talk/2011-March/001395.html I am a Catalan teacher of computer science and I am writing a book on native XML DB access, among other products, and I intend to submit the BaseX local API and also XMLDB and XQJ. For the moment, it seems XMLDB is not possible? Kind Regards, Isidre Guixà

2 2

letting you wait
by Christian Grün 11 Feb '12

11 Feb '12

Hi everyone, thanks for all the great feedback reg. BaseX 7.1 - and sorry for the pending questions in the list, which will be answered as soon as we're back from XMLPrague. All the best, Christian

1 0

Collections and Documents
by J Gager 08 Feb '12

08 Feb '12

Hello BaseX Team, In reading the documentation and mail archives, it seems to me that BaseX does not support documents in terms of having a single URI referring to a single document node. For example, if I add a document using the db:add function: db:add("DB", document { <a/> }, "doc.xml") And subsequently attempt to retrieve it using the doc function: fn:doc("doc.xml") I get a FODC0002 error. This is discussed in the mail archives, and so far as I can tell this is because BaseX only works with collections. It does not really address the concept of a documents (excuse me if I am over simplifying the issue here). In other words, I am free to add more document nodes under the name "doc.xml" therefore it is technically a collection as opposed to a document. Is this correct? A fairly early mailing list thread from 2010-07 addresses a similar and suggests an alternative approach where one might retrieve a document in a collection as follows: for $doc in collection('DB') where matches(document-uri($doc), 'doc.xml') return $doc But, doesn't this run afoul of the W3C recommendation which states for the fn:docucument-uri function that: "In the case of a document node $D returned by the fn:doc function, or a document node at the root of a tree containing a node returned by the fn:collection function, it will always be true that either fn:document-uri($D) returns the empty sequence, or that the following expression is true: fn:doc(fn:document-uri($D)) is $D. It is implementation-defined whether this guarantee also holds for document nodes obtained by other means, for example a document node passed as the initial context node of a query or transformation." In other words, if document-uri is returning 'doc.xml' for a node in collection('DB') then I should be able to get that same document node using the doc function. I ask these questions because we are interested in being able to maintain XML artifacts as singular documents, and using the collection hierarchy to do things such as storing temporary and archived version of these artifacts. The approach we are taking right now assumes that there is only one document-node under each 'document'. I want to understand the limitations of the collection and document implementation in BaseX so that I don't make any wrong assumptions (as I think I already have). Finally, assuming the interpretations are correct, are there plans to make any changes in the implementation to support something more in line with the hierarchy of db->collection->document? I have seen in previous threads that you were seeking feedback on this, and I am curious to know if you still are. Is there a major drawback you see to this model that perhaps I have not considered? Any feedback is appreciated. Thanks, Jack Gager Metadata Technology

2 4

BaseX has been updated on Filecluster.com
by FileCluster Support 08 Feb '12

08 Feb '12

Dear Developer, You have received this email because we have updated BaseX and this was the contact email for the application. Your application update status BaseX has been updated on FileCluster.com to the 7.1 version. You can check out your application on our site at: http://www.filecluster.com/Business-Office/Database-Management/Download-Bas… If you want to let your users know about your software page on FileCluster.com, to rate it and review it, you can also use this banner to link it: Promote your software As a software website, it`s our duty to help the developers promote their software. Fortunatelly, our software promotions are cost free, for more informations please visit our promotion page. Submit your press releases We are also accepting press releases from software developers. All you have to do is to submit your press release and we will take care of the rest. Useful developer links All the essential links you need as a developer on FileCluster.com: Link to us - download banners or text links for linking to FileCluster.com Submit your software - Submit your software via PAD or manually Submit your press release - submit your press releases using our online form Contact Us - contact our editors Promote your software - our promotions page If you do not wish to receive any further notifications or confirmations from FileCluster.com, please send us an email and request a contact removal (email removal). Keep in mind that this means you will not receive ANY contact from us, including: software promotions, update confirmations or security alerts (antivirus and spyware test results). Regards, Renta Cezar - Senior Editor FileCluster Labs www.filecluster.com

1 0

Using the GUI to see a database created with Java
by Johann LEGAYE 08 Feb '12

08 Feb '12

Hello everyone, I have created and populated a database in my JAVA app by using it : BaseXClient session = new BaseXClient("localhost", 1984, "admin", "admin"); session.execute("CREATE DB mydb input.xml"); *I would like to see my database through the baseX GUI...* What have I to do ? If I click on Open, I don't see my database or I know it is well created : session.execute("SHOW DATABASES") ** Show Databases ** 1 opened database(s): - mydb (1x) Thanks for your help, Johann

2 2

Use db:add from module. no updating expression allowed.
by andy 08 Feb '12

08 Feb '12

Hi! If there is a module: xquery version "1.0"; module namespace m="http://www.host.ru/xquery/m"; declare variable $m:db := "mydb"; declare function m:up() as xs:string { let $new-doc := <root-element><item>1</item></root-element> let $update := db:add($m:db, document { $new-doc }, "id1.xml") return "Result string" }; and I use it from python API or basexclient utility. Use as: xquery import module namespace m="http://www.host.ru/xquery/m" at "/tmp/test.xqy"; m:up() I get an error: Stopped at line 8, column 4 in /tmp/test.xqy: [XUST0001] Let expression: no updating expression allowed. What could be the problem? -- REGARDS, Andrey Ganyushkin

2 2

BaseX 7.1: The XMLPrague 2012 Edition
by Christian Grün 07 Feb '12

07 Feb '12

Dear all, three months have passed, and we are now proud to release BaseX 7.1, a.k.a. the XMLPrague 2012 Edition! These are some of the new exciting features (a full list is attached below): * GUI: the management of your databases, documents & binary files and index structure has got easier than ever before! * JSON: import, query and export your JSON data via XQuery, REST, or on command line! * Incremental Indexing: update your text and attributes index in realtime! * Enhanced Path Statistics: retrieve distinct values of location paths in constant time! * New XQuery functions to simplify database, full-text, index, and repository access * New XQuery 3.0 Features: support for EQNames, namespace constructors, etc. * Revised Command-Line API: process multiple inputs or commands in one run * Document Index: improved update performance We hope you have fun with our latest release, and we're looking forward to your feedback and seeing some of you in Prague, Christian BaseX Team _____________________________________________ BaseX 7.1 Feature List: GUI * improved document management: hierarchical view of databases resource * easier index creation/removal and database optimization * JSON/JsonML parser added * editor: updated and reopened files are reverted from disk REST * automatic XML conversion of popular content types (JSON/JsonML, CSV, HTML) XQUERY * new index module for directly accessing database index structures * new repository module to manage EXPath packages via XQuery * db:list-details() returns information on the database resources * db:content-type() retrieves the content-type of a specific database resource * ft:tokens() returns full-text tokens stored in the index * ft:tokenize() tokenizes a given input string * util:path() returns the path to the (currently executed) query file * util:time() prints the time needed to evaluate a given expression * util:mem() prints the allocated memory for evaluating a given expression * expanded QNames, computed namespace constructors COMMAND-LINE * multiple query files and -c/-i/-q flags can now be specified INDEXING * ID/Pre mapping, incremental indexing of value index structures * document index fix: correct replacement of existing documents * document index: faster updates OPTIONS * ADDRAW: add new resources as raw files if not filtered by CREATEFILTLER * MAXLEN: max. length of strings to be added to the index structures * MAXCATS: max. number of distinct values stored in statistics * UPDINDEX: turn on incremental index updates for value indexes * improved BINDINGS option CLIENT/SERVER * improved log output if query iterator is used * new ActionScript API (thanks to Manfred Knobloch!) SERIALIZATION * a project specific "newline" parameter specifies the type of newline to be used COMMANDS * modified KILL command accepts IP:port combination to specify target TRANSLATIONS * Bahasa Indonesian: thanks to Andria Arisal! * Mongolian: thanks to Tuguldur Jamiyansharav!

1 0

export xml using xquery in php
by Nafiz Al Naharul Islam Grameenphone IT Ltd. 03 Feb '12

03 Feb '12

Dear all, I need help to export xml file using xquery in php. Regards, Nafiz -Al Naharul Islam ________________________________ The information contained in this email and any attachment(s) to this email are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient and have received this email and/or its attachment(s) in error, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this email and/or its attachment(s) is strictly prohibited. Please notify the sender immediately and delete this email and any attachments. WARNING: Computer viruses can be transmitted via email. Although GPIT has taken reasonable precautions to ensure no viruses are present in this email and/or its attachment(s), GPIT does not guarantee that this email and/or its attachments are secure or error-free. The recipient should check this email and any attachment(s) for the presence of viruses. GPIT shall accept no liability whatsoever for any loss or damage arising from the use of this email and/or its attachment(s).

4 8

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk February 2012