[basex-talk] FW: Empty Initial Document Inconsistencies

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.gr...@gmail.com] Sent: mardi 3 juillet 2012 02:13 To: Dave Glick Cc: BaseX Subject: R

Re: [basex-talk] FW: Empty Initial Document Inconsistencies

Hi Fabrice, > Does that mean that current databases will not work anymore with the next > releases ? no worries, the database format will only (potentially) in an upcoming major release (BaseX 8 or 9). The only change is that formerly empty databases will now contain a single, empty document. B

Re: [basex-talk] Empty Initial Document Inconsistencies

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 t

[basex-talk] BaseX as a log msg store?

Hello, this is a general question as to whether in a given scenario BaseX might be an appropriate instrument. Per second approximately 1000 XML log messages must be stored and thus made available for querying. The messages are expected to be <= 1MB. The log messages may be sent by any number

Re: [basex-talk] BaseX as a log msg store?

Hello Hans-Juergen, here are some details about my use case, which is similar to yours. I'm using BaseX to insert the live public Twitter Stream into databases (see Wiki Entry [1]). One Twitter message is around 4 kb of size and i'm able to insert about 2000 of them per second using single XQue

[basex-talk] XML command syntax and options

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 *http://basex.org/rest";

[basex-talk] text / csv ouput - extra white space padding

All: Anyone has a little xquery / basex tip in getting rid of the extra white space that shows up at the beginning of each line after the first in the following xquery for $i in 1 to 10 return concat("x"," ") which in the UI returns x x x x x Just need a text output going to csv but this extra

Re: [basex-talk] BaseX as a log msg store?

Hello Andreas, thank you very much for these informations! Indeed, the use-cases are similar. I try to understand how exactly you stored the messages. The Wiki says: "the initial database just contained a root node ". So my understanding is that the messages are inserted as child elements int

Re: [basex-talk] text / csv ouput - extra white space padding

Hi Pascal, you can either create a new, single string via the fn:string-join() function… string-join(for $i in 1 to 10 return "x"," ") …or use the "output:separator" option of BaseX: declare option output:separator '\n'; (1 to 10) ! "x" The second option, or a variation of it, may eventu

Re: [basex-talk] text / csv ouput - extra white space padding

Hi Pascal, if you use BaseX inside a shell script or as a command line xquery processing tool, you may also use the -L flag: $ basex -h 2>&1 | grep L Usage: basex [-bcdiLosuvVwxz] [query] -L Append newlines to query results $ basex -L 'for $i in 1 to 10 return $i' 1 2 3 ... All the