[basex-talk] csv-parser

Hi all When importing CSV files, it seems that BaseX is parsing fields for balanced bracketing and quotes (a single quote or bracket causes trouble). Is it possible to turn that off, so that files are processed based only on delimiter? I couldn't find any information in the documentation. All the

Re: [basex-talk] csv-parser

Hi Lars, > When importing CSV files, it seems that BaseX is parsing fields for balanced > bracketing and quotes (a single quote or bracket causes trouble). Is it > possible to turn that off, so that files are processed based only on > delimiter? I couldn't find any information in the documentation

[basex-talk] some questions over the profile module

Hello Christian, I have some small questions over the profile module. 1) The following code declare function local:sequence($nb){for $i in 1 to xs:integer($nb) return $i}; prof:time(fn:count(local:sequence(100))) return 4.94 ms. It means that you lazy evaluate the query "{for $i

[basex-talk] BaseX Failing After a Number of Requests

Hi Guys, We have implemented BaseX to provide a REST API to access specific information out of the database. Databases range in size from hundreds to 6000+ XML files, and the APIs use the attribute index to quickly locate nodes and return information about them. We have been noticing that BaseX h

Re: [basex-talk] Error while adding a document.

Thanks for the reply ! Unluckily (or luckily), I dropped the database and created a new one, and now it works fine. But I shall send the data if I can reproduce the problem. 2013/12/3 Christian Grün > Hi Toko, > > thanks for your mail. Is the NBS database empty? Could you provide us > with th

Re: [basex-talk] some questions over the profile module

Hi Jean-Marc, > 1) The following code > declare function local:sequence($nb){for $i in 1 to xs:integer($nb) return > $i}; > prof:time(fn:count(local:sequence(100))) > return 4.94 ms. the InfoView will give you some hints what’s going on. The reason is that your code is compiled an

Re: [basex-talk] csv-parser

Fabulous, that fixed it! The lines with a single quote " in them are fine, as well as those with a single left parenthesis (. The data come from a SQL database with human entered data in freetext fields, so things aren't always in balance. The new file browser with the editor is nice too! Best,

[basex-talk] Serializing unescaped xml to string

Hi all, Is there a way to output unescaped XML to a string for debugging purposes? In unittests we would like to output the XML returned when a test fails, here is my example: declare %unit:test function elementinfo-test:test-element-info() { let $cases := Failed input input

Re: [basex-talk] Serializing unescaped xml to string

On Wed, 2013-12-04 at 19:59 -0800, Joe Templeman wrote: > Hi all, > > Is there a way to output unescaped XML to a string for debugging purposes? > In unittests we would like to output the XML returned when a test fails, > here is my example: [...] > || " Got: " || fn:seria