BaseX-Talk

basex-talk@mailman.uni-konstanz.de

8 participants
5240 discussions

Re: [basex-talk] BaseX db questions
by Christian Grün 28 Jan '10

28 Jan '10

Dear Aleks, > Adding a flag would be great , this will helps out so that we can sync database changes into xml file in one call. I've added the flag which allows updates files to be written back to disk. Note that, currently, all files of a modified database will be written back to disk after an update operation has been completed. Note that this is experimental; you're invited to test the latest version of the sources, which you find in our Subversion repository. The flag can be activated via the SET command in BaseX: Command Line: set writeback on; create db input.xml; xquery delete node //text() BaseX API: Context ctx = new Context(); new Set("WRITEBACK", true).execute(ctx); new CreateDB("input.xml").execute(ctx); new XQuery("xquery delete node //text()").execute(ctx); > We are getting the following exception while performing query against database : > Main.notexpected(Object...) line: 205 > TableDiskAccess.cursor(int) line: 326 > [...] > Can you shade some light why would this happen ? this problem happens randomly. This exception might (but need not) indicate an inconsistency in the data storage. It would be great if you could try to create a reproducible example – although I guess this might not be easy if the issue occurs only randomly. > We currently create a single Context object for every open database and keep passing this context for every call, do you think this will cause the problem ? That should be fine. Do you close the database/context – data.close() / context.close() – after all updates have been processed? All the best, Christian

1 0

Issue with Add using XML string
by J Gager 28 Jan '10

28 Jan '10

Sorry for the repeat posts on my last question. I was expecting a confirmation from the web page that the mail was sent - I should know better than to keep clicking :) As stated in my previous question (subject: Issues with XQuery insert), we have tried different methods to add new XML documents to a collection using the Java API. One such approach is to use the Add command, supplying the document content as the XML string. When doing so, the process will fail when there are double quotes used in the attribute values. For example, the following string; <s:test xmlns:s="abc" xmlns:x="def">hello</s:test> yields this error; (Line 1): Open quote is expected for attribute "{1}" associated with an element type "xmlns:s". Alternatively this string; <s:test xmlns:s='abc' xmlns:x='def'>hello</s:test> is not an issue. The double quotes are also not an issue when the argument to the Add command points to a file. Has anyone else encountered this issue? We could of course replace the double quotes with single quotes - however this is not desirable since some of the content of our XML file may contain double quotes that we would not want to change. Thanks, J Gager

2 1

Issues with XQuery insert
by j.gager＠metadatatechnology.com 28 Jan '10

28 Jan '10

Hello We are using BaseX6 to manage a local repository of XML artifacts in a Java based application. We initially start with an empty collection, and add documents as they are needed. We have tried a number of approaches to this (more to come on this in a separate email). One such approach is to insert the documents as nodes into the container using XQuery. Example: insert nodes document {<t:test xmlns:t='xyz' xmlns:s='def'>good <s:test>bye</s:test></t:test>} into collection('MyCollection') It seems to me that only the first namespace declaration is retrained. If I follow this insertion with the following query: declare namespace x ="xyz"; declare namespace y ="def"; collection('MyCollection')/x:test I get the following result: <t:test xmlns:t="xyz">good <s:test xmlns:s="">bye</s:test></t:test> Notice that the namespace for the prefix s is now empty. Further, if I reverse the order of the namespace declarations in the insert query: <t:test xmlns:s='def' xmlns:t='xyz'>good <s:test>bye</s:test></t:test> The query used above will not return a result (presumably because the xyz namespace has been dropped). Has anyone else encountered such issues? Currently we are working around this by saving the XML content to a file and using the Add process - which seems to work as expected. If possible, we would prefer to avoid this extra step of saving the XML to a temporary file before adding it to our BaseX database. Thanks, J Gager

2 1

BaseX db questions
by aleks＠narus.com 27 Jan '10

27 Jan '10

Hello, I'm evaluating baseX database and trying to figure out few details: 1) What is the concept of the Context ? Do I need to create a new context for every database operation or same context should be used within open database ? 2) Is it true that I have to open and close database every time I run query or I can keep database open. 3) How does commit occur, with basex6 it seems like data being committed to disk with some delay? Thanks a lot in advance!! --Aleks

3 6

Issues with XQuery insert
by J Gager 27 Jan '10

27 Jan '10

1 0

Issues with XQuery insert
by j.gager＠metadatatechnology.com 27 Jan '10

27 Jan '10

1 0

Issues with XQuery insert
by j.gager＠metadatatechnology.com 27 Jan '10

27 Jan '10

1 0

BaseX was successfully LISTED on FreeVistaFiles.com
by FreeVistaFiles.com 24 Jan '10

24 Jan '10

Hello DBIS Group, University of Konstanz, we just let you know that your software BaseX was successfully listed on FreeVistaFiles.com. Because we are listing quality software only, you may display our Listing image on any page. Here is the HTML code you could use to your Web page: <a href="http://www.freevistafiles.com/DBIS-Group-University-of-Konstanz+BaseX.html"><img src="http://www.freevistafiles.com/images/freevistafiles_listed_160x80.png" style="border:none;" width="160" height="80" alt="BaseX for Vista"></a> (you can download a copy of this image to keep it in your local web directory, and change the HTML fragment above to reference your local image rather than the one on our server) For current product BaseX update you should use this URL: http://www.freevistafiles.com/update-pad/DBIS-Group-University-of-Konstanz+… (we recommend you bookmark this URL for easiest future updates). And for others use this submission page: http://www.freevistafiles.com/submit/ Thank you, FreeVistaFiles.com Team. http://www.freevistafiles.com/

1 0

how to change storage location of basex database
by Travis Webb 24 Jan '10

24 Jan '10

I've looked through the documentation but cannot find out how to do this. How do I change the path in which to store the basex files for a particular database? For example, if I create this database, create db test.xml test the basex files are, by default, stored in ~/BaseXData. How do I change this? -tjw

2 1

XML database
by Steve Xu 22 Jan '10

22 Jan '10

Hello, I would like to know the usage of BaseX in industry and it's stability. It looks great! Regards, Steve Xu 647-747-6170(work) 416-564-7801(bb) 206AD74F(pin) steve.xu(a)rci.rogers.com steve.xu(a)rogers.blackberry.net This e-mail (and attachment(s)) is confidential, proprietary, may be subject to copyright and legal privilege and no related rights are waived. If you are not the intended recipient or its agent, any review, dissemination, distribution or copying of this e-mail or any of its content is strictly prohibited and may be unlawful. All messages may be monitored as permitted by applicable law and regulations and our policies to protect our business. E-mails are not secure and you are deemed to have accepted any risk if you communicate with us by e-mail. If received in error, please notify us immediately and delete the e-mail (and any attachments) from any computer or any storage medium without printing a copy. Ce courriel (ainsi que ses pièces jointes) est confidentiel, exclusif, et peut faire l’objet de droit d’auteur et de privilège juridique; aucun droit connexe n’est exclu. Si vous n’êtes pas le destinataire visé ou son représentant, toute étude, diffusion, transmission ou copie de ce courriel en tout ou en partie, est strictement interdite et peut être illégale. Tous les messages peuvent être surveillés, selon les lois et règlements applicables et les politiques de protection de notre entreprise. Les courriels ne sont pas sécurisés et vous êtes réputés avoir accepté tous les risques qui y sont liés si vous choisissez de communiquer avec nous par ce moyen. Si vous avez reçu ce message par erreur, veuillez nous en aviser immédiatement et supprimer ce courriel (ainsi que toutes ses pièces jointes) de tout ordinateur ou support de données sans en imprimer une copie.

3 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk