BaseX-Talk

basex-talk@mailman.uni-konstanz.de

6 participants
5250 discussions

New map syntax issue
by Daniël Knippers 18 Sep '13

18 Sep '13

Hi, Using the new map syntax of BaseX 7.7.1, I ran into this: let $m := { 'key':'val' } return $m('key') [XPST0003] Invalid key, simple expression expected. As it turns out, a space is required after the closing quote of the key. That is, the above example works fine when replacing 'key':'val' by 'key'<SPACE>:'val' This is not the case when using an integer key, i.e. this works fine: let $m := { 1:'val' } return $m(1) I'm not sure if this behavior is intentional, but I would guess it is not :-) Regards, Daniël

2 1

Re: [basex-talk] (no subject)
by Christian Grün 18 Sep '13

18 Sep '13

Hi Anand (cc @ basex-talk), > Yesterday, in the mailing list you have mentioned certain NEW fixes for > 7.7.1. > I am more concerned about > > CORE > ? OutOfMemory exceptions are avoided when building large databases > > > Can you explain it in details? I mean the size of "large databases"... John Best was so kind to point me to a bug in BaseX 7.7, which hindered the creation of index structures of larger databases (i.e., those document instances the size of which exceeded the system’s main memory). This error occurred whenever a newly built index structure was too large to fit in main memory. In this case, a partial index is written to disk, and the subsequent memory check was too strict and stopped further indexing. Hope this helps, Christian

1 0

fn:format-number()#2 possible bug
by alxarch 18 Sep '13

18 Sep '13

There seems to be an unexpected behaviour whem using fn:format-number() while having declared a default element namespace in the prologue. Example: > declare default element namespace "http://foo.bar"; > format-number(1234, "0000") Throws an [FODF1280] 'Unknown decimal format: Q{http://foo.bar}' Am i missing something or is this a bug in the 2 argument form of fn:format-number? Thanks, Alex

2 1

BaseX 7.7.1, refactored project structure
by Christian Grün 16 Sep '13

16 Sep '13

Dear all, you are invited to check out our minor 7.7.1 release, which contains the following patches and fixes: XQUERY • we have switched to the new map syntax (example: {'key':'value'}) • tail call optimization is now also applied to dynamic functions • fn:subsequence() calls and sequence casts are better optimized • original options are preserved when calling db:optimize() WEBDAV • non-breakable spaces are returned as   CORE • OutOfMemory exceptions are avoided when building large databases The new release can be found at: http://basex.org Next, we have refactored our project structure: all basex repositories have been merged into one single basex repository: https://github.com/basexdb/basex Your feedback is welcome! Have fun, Christian BaseX Team, 2013

1 0

Adding non ".xml" file extension XML files
by Joe Templeman 14 Sep '13

14 Sep '13

I'm trying to add a collection of files which are all valid XML but when I'm doing the add with this command: db:add("db", "/data/xml/docs/", "docs") where /data/xml/docs contains a number of XML files with a .s9ml file extension, nothing gets added to the database, however if I rename that file.xml, it works. Is there somewhere I can set what file extensions should be used? I can't seem to find anything in any of the docs about this. Thanks, Joe

2 1

Exception when using replace - UPDINDEX problem?
by James Ball 14 Sep '13

14 Sep '13

Hello, I've got a collection with about 1.4 million small XML files in it. I can load all these through the GUI with no problems. However really I need to be loading them, a few at a time, through PHP and have code to do this. Because the process involves add, query, add and so on I have set UPDINDEX to true on the database. In most instances everything works fine but sometimes I get the error below (it's not on particular documents, a second run will give the error in different places). Once this error has been received it seems the OPTIMIZE doesn't work properly on the database - giving an array out of range error. I don't understand the stack trace enough to know what the most likely cause is. Can anyone provide me with some guidance? Many thanks, James exception 'Exception' with message 'Improper use? Potential bug? Your feedback is welcome: Contact: basex-talk(a)mailman.uni-konstanz.de Version: BaseX 7.7 Java: Apple Inc., 1.6.0_51 OS: Mac OS X, x86_64 Stack Trace: java.lang.IllegalStateException: Key should not exist at org.basex.index.value.UpdatableDiskValues.index(UpdatableDiskValues.java:79) at org.basex.data.DiskData.indexEnd(DiskData.java:356) at org.basex.data.Data.insert(Data.java:817) at org.basex.core.cmd.Add.run(Add.java:107) at org.basex.core.Command.run(Command.java:345) at org.basex.core.Command.run(Command.java:117) at org.basex.core.cmd.Replace.run(Replace.java:68) at org.basex.core.Command.run(Command.java:345) at org.basex.core.Command.exec(Command.java:321) at org.basex.core.Command.execute(Command.java:78) at org.basex.core.Command.execute(Command.java:90) at org.basex.server.ClientListener.execute(ClientListener.java:386) at org.basex.server.ClientListener.replace(ClientListener.java:365) at org.basex.server.ClientListener.run(ClientListener.java:106) ' in /Library/WebServer/Documents/ISIS/BaseXClient.php:101 Stack trace: #0 /Library/WebServer/Documents/ISIS/BaseXClient.php(60): Session->sendCmd(12, 'ISIS_IND_BIO/IW...', '<?xml version="...') #1 /Library/WebServer/Documents/ISIS/uploadBioCli.php(79): Session->replace('ISIS_IND_BIO/IW...', '<?xml version="...') #2 {main}Processing file 358 /Users/jb8748/Documents/Data Auditing/ISIS_IND_BIO/IWF/-9458-.xml

3 3

DB ~webdav
by France Baril 14 Sep '13

14 Sep '13

Hi, I deleted the ~webdav DB by error, and now I am getting an Unexpector error with this trace: DB org.basex.core.BaseXException: Database '~webdav' was not found. Doh! Is there a place I can download a copy of this DB? Or can you provide the parameters I should use to recreate it? Thanks, -- France Baril Architecte documentaire / Documentation architect france.baril(a)architextus.com (514) 572-0341

3 3

Query document metadata
by Bodo Hüsemann 14 Sep '13

14 Sep '13

Hi, do we have any means in XQuery or with the Base-X API to query the age of a document? E.g. let's assume we add documents like this: mySession.add(inDocumentRef, new ByteArrayInputStream(inDocument)); Is there any way to query metadata when this document was added to the database (or other metadata, e.g. the size, too)? The background is that I access external content dynamically and I want to refresh data in the DB according to some defined update strategy (e.g. when the document is older than x-days). I want to apply the strategy based on metadata and not on content, so I don't want to query some document specific elements or attributes. Many thanks in advance! Bodo Hüsemann

2 1

BaseX 7.7 error in working with EQNames
by Dimitre Novatchev 11 Sep '13

11 Sep '13

Hi, Given this XML document (in file example.xml): Freude, schöner Götterfunken, Tochter aus Elysium, Wir betreten feuertrunken, Himmlische, dein Heiligtum. This XQuery expression (in file TesQNametExpression.xquery, in the same directory): let $doc := doc('example.xml') return string-length($doc/Q{ http://example.com/one}p[1]/@Q{http://www.w3.org/XML/1998/namespace}lang) produces: 0 However the correct result (which I get with Saxon 9.5.01) is: 1 Here is the "Query Info" from the BaseX UI: Compiling: - pre-evaluating fn:doc("example.xml") - binding static variable $doc - removing unknown element/attribute Q{http://example.com/one}p - pre-evaluating fn:string-length(()) - removing variable $doc - simplifying flwor expression Query: let $doc := doc('example.xml') return string-length($doc/Q{ http://example.com/one}p[1]/@Q{http://www.w3.org/XML/1998/namespace}lang) Optimized Query: 0 Hope that this information would be useful for identifying and fixing the issue. -- Cheers, Dimitre Novatchev --------------------------------------- Truly great madness cannot be achieved without significant intelligence. --------------------------------------- To invent, you need a good imagination and a pile of junk ------------------------------------- Never fight an inanimate object ------------------------------------- To avoid situations in which you might make mistakes may be the biggest mistake of all ------------------------------------ Quality means doing it right when no one is looking. ------------------------------------- You've achieved success in your field when you don't know whether what you're doing is work or play ------------------------------------- Facts do not cease to exist because they are ignored. ------------------------------------- Typing monkeys will write all Shakespeare's works in 200yrs.Will they write all patents, too? :) ------------------------------------- I finally figured out the only reason to be alive is to enjoy it.

2 2

XML results file saving
by rdepery＠mscgva.ch 10 Sep '13

10 Sep '13

Hello there, This is my first post to this list, and I’d like first thanks everyone involved in this project. I have a problem of xml saving right now, and it seems it is not related to baseX itself, but might be something else I need to find out. I have queries I run against one or two db, the result is quite big and appear “chopped”. For a long time, using the save button, saved the result (the complete or “chopped” file I was seeing in output window…(text). Since a few time, when I save, only a few nodes are saved or almost nothing… Sometime not even the result in showed in “text”. File is saved, but instead of saving 3 or 5 Mb it saves 55Ko sometime more, sometime less. Could someone tell me if it is rather a memory, java, variable, query or anything else problem? I reinstalled java (jre6, jre7….), went from basex 7.7 to 7.5, rebooted several times. Note: First time you do the query and save, it works fine (ie. on colleague’s computer), the next, it doesn’t. Thanks for your suggestions. Richard This message and any associated files (together the “Contents”) are intended solely for the addressee(s). The Contents are confidential and may contain private information or information that is subject to copyright or is a trade secret or which is privileged. Views or opinions expressed herein do not necessarily represent views or opinions of MSC Mediterranean Shipping Company, its agents or their affiliated companies and may only be the view or opinion of the author. If you are not the intended recipient of this email, you must not use, print, copy, store, forward, or disclose it or act in reliance of the Contents. Please destroy all copies of the message and any associated files and notify the sender immediately that you have received it in error. Thank you for your cooperation. ------MSC LEGAL DISCLAIMER

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk