Re: [basex-talk] Position of matched tokens in a full-text query

2014-11-27 Thread Javier Couto
Hi Christian, Yes, it helps, tank you! I will try this approach. Two last questions: 1. The ft:tokenize function tokenizes on-the-fly or tokens are stored in the full text index ? It seems that they are stored for the whole document, but for each text element ? I’m wondering if I can speed up

[basex-talk] Windows startup script problems

2014-11-27 Thread Marc van Grootel
Hi, I just downloaded the latest snapshot and on Windows I got a problem with the startup scripts. I saw that compared to earlier the way to set JVM options has changed. In my case this was causing problems. When I started the default basexhttp.bat I got: Invalid maximum heap size:

Re: [basex-talk] Position of matched tokens in a full-text query

2014-11-27 Thread Christian Grün
Hi Javier, 1. The ft:tokenize function tokenizes on-the-fly or tokens are stored in the full text index? Tokenization is done on-the-fly. It would actually take much longer to find the correspondent tokens for a text in the index. Moreover, you can tokenize arbitrary input strings. The

[basex-talk] unexpected behaviour

2014-11-27 Thread Rob Stapper
Hi, I'm playing with the new XQuery 3.1 functions amongst which the JSON-serilization. I would expect all three snippets below to result in the same output but all three give a different result. Snippet 1: === declare option output:method 'json'; serialize( atest/a )

Re: [basex-talk] Windows startup script problems

2014-11-27 Thread Christian Grün
Marc, thanks for the hint. I have updated the startup scripts in question. Best, Christian On Thu, Nov 27, 2014 at 10:45 AM, Marc van Grootel marc.van.groo...@gmail.com wrote: Hi, I just downloaded the latest snapshot and on Windows I got a problem with the startup scripts. I saw that

Re: [basex-talk] unexpected behaviour

2014-11-27 Thread Christian Grün
Hi Rob the behavior is correct: declare option output:method 'json'; serialize( atest/a ) The result is: atest/a …as specified in [1]. serialize( atest/a , map{ 'method' : 'json'} ) The result is: lt;agt;testlt;/agt; The node will first be serialized to a string, and

Re: [basex-talk] unexpected behaviour

2014-11-27 Thread Rob Stapper
Hi Christian, Thanx for the quick response. I get it. In my case I want the result of the first snippet but then in a xquery-module. I can't use the: declare option . in a module. Can you give me a suggestion how to realize this? Thanx in advance, Rob -Oorspronkelijk bericht-

Re: [basex-talk] unexpected behaviour

2014-11-27 Thread Christian Grün
Can you give me a suggestion how to realize this? It depends on how you retrieve your results. Do you use RESTXQ, BaseX as standalone, or any other API? Christian

Re: [basex-talk] Reg : NegativeArraySizeException

2014-11-27 Thread Christian Grün
Hi ChandraSekhar, We have received your mail (see [1]). To guide you, we need more information. Do you have documents that allow us to reproduce the issue? Have you interrupted running update operations? What output does the BaseX INSPECT command give you? Christian [1]

Re: [basex-talk] CSV : escape character feature

2014-11-27 Thread Christian Grün
Hi Fabrice, my first escaping solution was a bit shortsighted. I have now added a new BACKSLASHES option, which allows you (and everyone else in this little XQuery world) to explicitly turn on backslash escaping [1]. This works both for parsing and serializing CSV. The new snapshot is available