BaseX-Talk

basex-talk@mailman.uni-konstanz.de

6 participants
5270 discussions

Problem with RunQueries.java example!!
by Anand Chiney (AIR) 07 Jul '12

07 Jul '12

Dear BaseX Team, The method iterate() which is used to convert the XML result to its Java representation is retuning [null]. I tried this code with the default query and also with 2-3 more XML files. All are giving same, [null] output..!! Have a nice day :) Regards Anand Chiney

2 1

Re: [basex-talk] Empty Initial Document Inconsistencies
by Dave Glick 07 Jul '12

07 Jul '12

Christian, Thanks again for this! I still haven't had a chance to do any rigorous testing, but in my initial use everything looks great (and all my unit tests still pass). I think more importantly, this resolves an undocumented inconsistency for users of the low-level API - with the guarantee that the database will behave the same way regardless of state, a lot of conditional code can now be removed. Proof that good things come to those who wait :). Dave -----Original message----- From: "Christian Grün" <christian.gruen(a)gmail.com> To: Dave Glick <dglick(a)dracorp.com> Cc: BaseX <basex-talk(a)mailman.uni-konstanz.de> Sent: Tue, Jul 3, 2012 00:13:58 GMT+00:00 Subject: Re: [basex-talk] Empty Initial Document Inconsistencies Hi Dave, here's finally some public feedback for your outstanding feature request: I've rewritten our internal database structures, such that an empty database will now really be empty (i.e., contain no dummy document node anymore). As a result, some convenience methods have disappeared from the Data class (Data.isEmpty(), Data.single()), as they were only offered to hide the former inconsistency. The changes have now been merged into the BaseX master branch. While I believe that we have tested the changes quite well, I am always glad for any feedback. Christian ___________________________ On Thu, Dec 29, 2011 at 4:36 PM, Dave Glick <dglick(a)dracorp.com> wrote: > Hello again, > > I've noticed some inconsistencies with regard to the initial document in an empty database. I understand that it is often treated as an indication that the database is "empty". I.e., if the database has only one node and it's a document at the first pre value, then Data.empty() returns true. The problem arises because the database isn't actually empty - it contains one empty document - and some commands/methods view it as an empty database while others treat it as a database with one empty document. Several examples: > > - The method Data.doc(name) will return -1 (indicating the document doesn't exist) while Data.docs() will return an array of size 1 with the first value a 0 (indicating there is one document at pre value 0). This is actually my own problem because the API I'm writing relies on these two methods being internally consistent - I can't have one telling me there is one document called "XYZ" but then have the other refuse to give me a pre value for the "XYZ" document I was just told exists. > - The GUI shows a single doc node in the tree view but issuing the command "list [database name]" shows the database as having no resources. > - I can evaluate the query "insert node 'text' into doc('[initial document name]')" and it executes. I can see the new text node under the initial document in the GUI tree view. Now when I issue the command "list [database name]" I see 1 resource. Having the list command report different numbers of resources before and after a XQuery insertion seems odd. > - If I issue the command "ADD TO newdoc <xyz/>", I can see the new doc("newdoc") node with the child <xyz> element in the GUI but the previously empty document is now gone. This also seems odd - I'm not sure how I feel about an ADD command removing data from the database (even if it was just intended to be a placeholder). > > In the end, I think BaseX should support the notion of a database with one empty document as being valid - there are probably cases where one might want to start their session in that state. I'm not sure what the solution is or should be (or if it's even something that is worth or needs solving). My own preference would be for the internal indication of an empty database to use a different node kind dedicated for that purpose so there is no confusion whether the single node at pre 0 is an empty initial document or an indication of an empty database. > > At the very least, I think the inconsistencies above should be corrected - if a single empty document node is intended to signify an empty database and is not actually intended to be part of the database, then you should not see it in the GUI, not be allowed to insert content to it, etc. > > Dave > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk(a)mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk

4 12

Performance regression from 7.2 to 7.3 ?
by Nicolas Labrot 07 Jul '12

07 Jul '12

Hello, I have upgraded BaseX from 7.2 to 7.3 but I have a severe performance drop on my query. My query is in 2 parts : - The first part extracts values from an xpath and store them in a map (the map contains 40000 entries) - The second part extracts values from an xpath and test if they are contains in the map (xpath return around 30000 entries). On 7.2 a typical query run on 2s and on 7.3 I have no result after 10 minutes Is there modification on BaseX 7.3 which can explain this performance drop ? Thanks for your help, Regards, Nicolas

2 6

Empty Initial Document Inconsistencies
by Dave Glick 05 Jul '12

05 Jul '12

Hello again, I've noticed some inconsistencies with regard to the initial document in an empty database. I understand that it is often treated as an indication that the database is "empty". I.e., if the database has only one node and it's a document at the first pre value, then Data.empty() returns true. The problem arises because the database isn't actually empty - it contains one empty document - and some commands/methods view it as an empty database while others treat it as a database with one empty document. Several examples: - The method Data.doc(name) will return -1 (indicating the document doesn't exist) while Data.docs() will return an array of size 1 with the first value a 0 (indicating there is one document at pre value 0). This is actually my own problem because the API I'm writing relies on these two methods being internally consistent - I can't have one telling me there is one document called "XYZ" but then have the other refuse to give me a pre value for the "XYZ" document I was just told exists. - The GUI shows a single doc node in the tree view but issuing the command "list [database name]" shows the database as having no resources. - I can evaluate the query "insert node 'text' into doc('[initial document name]')" and it executes. I can see the new text node under the initial document in the GUI tree view. Now when I issue the command "list [database name]" I see 1 resource. Having the list command report different numbers of resources before and after a XQuery insertion seems odd. - If I issue the command "ADD TO newdoc <xyz/>", I can see the new doc("newdoc") node with the child <xyz> element in the GUI but the previously empty document is now gone. This also seems odd - I'm not sure how I feel about an ADD command removing data from the database (even if it was just intended to be a placeholder). In the end, I think BaseX should support the notion of a database with one empty document as being valid - there are probably cases where one might want to start their session in that state. I'm not sure what the solution is or should be (or if it's even something that is worth or needs solving). My own preference would be for the internal indication of an empty database to use a different node kind dedicated for that purpose so there is no confusion whether the single node at pre 0 is an empty initial document or an indication of an empty database. At the very least, I think the inconsistencies above should be corrected - if a single empty document node is intended to signify an empty database and is not actually intended to be part of the database, then you should not see it in the GUI, not be allowed to insert content to it, etc. Dave

4 7

XML command syntax and options
by Andy Bunce 05 Jul '12

05 Jul '12

I am looking at the new 7.3 XML format commands and some things that are not clear to me in the documentation. My particular goal is to create a new database ensuring CHOP is off. There is a Rest syntax example that is exactly what I want at http://docs.basex.org/wiki/REST *<command xmlns="http://basex.org/rest">* * <text>create db test http://files.basex.org/xml/xmark.xml</text>* * <option name='chop' value='false'/>* *</command>* except I want to use the client module http://docs.basex.org/wiki/Client_Module. Can client:execute module use the XML syntax? And if so does the XML syntax <create-db name='...'> Have a way to specify options? Or should I use multiple commands starting with <set option='CHOP'>OFF</set> These links http://docs.basex.org/wiki/Commands#XML_Syntax http://docs.basex.org/wiki/Commands#CREATE_DB are not making it completely clear to me. /Andy

2 1

Chic Bridal Party Dresses
by mltailor.com 04 Jul '12

04 Jul '12

1 0

Radiant like a star
by mltailor.com 04 Jul '12

04 Jul '12

1 0

FW: Empty Initial Document Inconsistencies
by Fabrice Etanchaud 03 Jul '12

03 Jul '12

Dear all at BaseX, Dear Christian, Does that mean that current databases will not work anymore with the next releases ? Best regards, Fabrice -----Original Message----- From: Christian Grün [mailto:christian.gruen@gmail.com] Sent: mardi 3 juillet 2012 02:13 To: Dave Glick Cc: BaseX Subject: Re: [basex-talk] Empty Initial Document Inconsistencies Hi Dave, here's finally some public feedback for your outstanding feature request: I've rewritten our internal database structures, such that an empty database will now really be empty (i.e., contain no dummy document node anymore). As a result, some convenience methods have disappeared from the Data class (Data.isEmpty(), Data.single()), as they were only offered to hide the former inconsistency. The changes have now been merged into the BaseX master branch. While I believe that we have tested the changes quite well, I am always glad for any feedback. Christian ___________________________ On Thu, Dec 29, 2011 at 4:36 PM, Dave Glick <dglick(a)dracorp.com> wrote: > Hello again, > > I've noticed some inconsistencies with regard to the initial document in an empty database. I understand that it is often treated as an indication that the database is "empty". I.e., if the database has only one node and it's a document at the first pre value, then Data.empty() returns true. The problem arises because the database isn't actually empty - it contains one empty document - and some commands/methods view it as an empty database while others treat it as a database with one empty document. Several examples: > > - The method Data.doc(name) will return -1 (indicating the document doesn't exist) while Data.docs() will return an array of size 1 with the first value a 0 (indicating there is one document at pre value 0). This is actually my own problem because the API I'm writing relies on these two methods being internally consistent - I can't have one telling me there is one document called "XYZ" but then have the other refuse to give me a pre value for the "XYZ" document I was just told exists. > - The GUI shows a single doc node in the tree view but issuing the command "list [database name]" shows the database as having no resources. > - I can evaluate the query "insert node 'text' into doc('[initial document name]')" and it executes. I can see the new text node under the initial document in the GUI tree view. Now when I issue the command "list [database name]" I see 1 resource. Having the list command report different numbers of resources before and after a XQuery insertion seems odd. > - If I issue the command "ADD TO newdoc <xyz/>", I can see the new doc("newdoc") node with the child <xyz> element in the GUI but the previously empty document is now gone. This also seems odd - I'm not sure how I feel about an ADD command removing data from the database (even if it was just intended to be a placeholder). > > In the end, I think BaseX should support the notion of a database with one empty document as being valid - there are probably cases where one might want to start their session in that state. I'm not sure what the solution is or should be (or if it's even something that is worth or needs solving). My own preference would be for the internal indication of an empty database to use a different node kind dedicated for that purpose so there is no confusion whether the single node at pre 0 is an empty initial document or an indication of an empty database. > > At the very least, I think the inconsistencies above should be corrected - if a single empty document node is intended to signify an empty database and is not actually intended to be part of the database, then you should not see it in the GUI, not be allowed to insert content to it, etc. > > Dave > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk(a)mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk

2 1

REST service problems - 401-Header sent‏
by MyNew EMail 02 Jul '12

02 Jul '12

Hi again, > What do you exactly mean with "long XQuery request"? Could you provide > us with an example that demonstrates the problem (I didn't manage to > track it down locally)?I'm using PHP with cURL to call the REST service (with standard username and password [admin, admin] for testing). Furthermore I'm using the BaseX HTTP Server (basexhttp.bat).Here is some code summary (first example works well): <?php//... $query = 'let $x := <abc> <aaa>Test</aaa> <aaa>Test</aaa> <aaa>Test</aaa> <aaa>Test</aaa> <aaa>Test</aaa> <aaa>Test</aaa> <aaa>Test</aaa> <bb test="123"><a>test</a></bb> <bb test="123"><a>test</a></bb> <bb test="123"><a>test</a></bb> </abc> return insert node $x as last into //test'; $fullQuery = '<query xmlns="http://basex.org/rest">'; $fullQuery .= '<text><![CDATA[ '.$query.']]></text>'; $fullQuery .= '</query>';//...//set authorization stuff//set Content-Type header to application/xml and send a POST request to http://localhost:8984/rest/MyDb/test.xml with $fullQuery in body.//This works. Example XML will be inserted.?> But if the XML part (let $x := ...) or the XQuery part is longer I get this response (and I'm authorized the same way as in the first example): HTTP/1.1 401 Unauthorized WWW-Authenticate: BasicContent-Length: 31 Server: Jetty(6.1.26) This example does'nt work:<?php $query = 'let $x := <abc> <aaa>Test</aaa> <aaa>Test</aaa> <aaa>Test</aaa> <aaa>Test</aaa> <aaa>Test</aaa> <aaa>Test</aaa> <aaa>Test</aaa> <aaa>Test</aaa> <aaa>Test</aaa> <aaa>Test</aaa> <aaa>Test</aaa> <aaa>Test</aaa> <aaa>Test</aaa> <aaa>Test</aaa> <aaa>Test</aaa> <aaa>Test</aaa> <bb test="123"><a>test</a></bb> <bb test="123"><a>test</a></bb> <bb test="123"><a>test</a></bb> <bb test="123"><a>test</a></bb> <bb test="123"><a>test</a></bb> <bb test="123"><a>test</a></bb> <bb test="123"><a>test</a></bb> <bb test="123"><a>test</a></bb> <bb test="123"><a>test</a></bb> <bb test="123"><a>test</a></bb> <bb test="123"><a>test</a></bb> <bb test="123"><a>test</a></bb> <bb test="123"><a>test</a></bb> <bb test="123"><a>test</a></bb> <bb test="123"><a>test</a></bb> <bb test="123"><a>test</a></bb> <bb test="123"><a>test</a></bb> <bb test="123"><a>test</a></bb> <bb test="123"><a>test</a></bb> <bb test="123"><a>test</a></bb> </abc> return insert node $x as last into //test'; $fullQuery = '<query xmlns="http://basex.org/rest">'; $fullQuery .= '<text><![CDATA[ '.$query.']]></text>'; $fullQuery .= '</query>'; //...?> Removing whitespaces makes it possible to send a request which is a bit longer, but not very much. Is there a solution to send requests like this, maybe in a different way? It is important to make bigger updates on my XML data with REST. Greetings @all

2 1

Sending DELETE request through HTTP Module
by Seenivasan Gunabalan 02 Jul '12

02 Jul '12

hi, My objective is to delete the collections/files through the DELETE request using HTTP module. The DELETE operation does fine, when I ran it from BasexGUI. But if i put the same query inside delete.xq and invoke it by http://localhost:8984/rest?run=delete.xq, The request never returns any response and possibly got hanged. I need to restart the database to make the database to function. I am enclosing the xq i used, import module namespace http='http://expath.org/ns/http-client'; declare function local:cleanlist() { ('sample/record1','sample/record2','sample/record3') }; declare function local:cleandb() { try { for $cl in local:cleanlist() return http:send-request(<http:request method="DELETE" href="http://localhost:8984/rest/{$cl}" status-only = "true" username = "admin" password = "admin" send-authorization="true"> </http:request>) } catch err { err:description } }; <cleandb>{ local:cleandb() }</cleandb>

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk