Re: [basex-talk] Server protocol bug?

I missed the obvious part of option 'suboptions' I fixed the parsing in basex-stream and now `query.options()` returns an object in v0.1.2.

[basex-talk] Server protocol bug?

Hi, While testing for basex-stream i encountered a weird behavior in the OPTIONS query command. After creating the query ```xquery declare option output:method json; declare option output:json lax; json type=object/ ``` the response of OPTIONS was: `json=lax=true,method=json` Which seems

Re: [basex-talk] New BaseX client for nodejs

Hi Andy, Thanks, I just fixed events monitoring too (v0.1.1). It appears that using node's Transform stream classes and combining them via pipes allows much cleaner code overall. I am new to Literate CoffeeScript also but using it in this package helped me understand the way my code would work

Re: [basex-talk] New BaseX client for nodejs

Hi all, I released my new BaseX client for nodeJS https://www.npmjs.com/package/basex-stream It's currently in a usable state. I need to document and test some more. The source is in Literate CoffeeScript so documentation is visible in-place in github. The functionality will expand as new

[basex-talk] New BaseX client for nodejs

Hi all, I am making a new BaseX client for nodejs. It focuses on utilising node streams in order to be able to pipe data to/from BaseX directly. (i.e. pipe request body to an ADD command or pipe XQuery output to a response). It also uses promises for more code flow flexibility. Features: -

[basex-talk] Bug in XQuery archive module

Hi, I stumbled upon a bug in the archive module on BaseX 8.0. The zip files created by the archive module are not valid. ``` let $found := file:list(/tmp/test/media/) return file:write-binary(/tmp/test.zip, archive:create( $found, $found ! file:read-binary( /tmp/test/media/ || .) , map {

[basex-talk] Namespace conflict in XQuery update

While trying to transform an xhtml document I ran into this general case: copy $ul := ul xmlns=http://www.w3.org/1999/xhtml; liitem/li liitem/li /ul modify ( rename node $ul as QName(http://www.w3.org/1999/xhtml,ol;), insert node attribute class {a} into $ul ) return $ul which throws an

[basex-talk] fn:format-number()#2 possible bug

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, ) Throws an [FODF1280] 'Unknown decimal format: Q{http://foo.bar}'