BaseX-Talk November 2014

basex-talk@mailman.uni-konstanz.de

35 participants
59 discussions

Embedded Mode performance too poor
by dicker24 07 Nov '14

07 Nov '14

Hi, I am new here, I tried to integrate baseX in my Java program, but the performance is very poor in comparison with GUI. I also tried to declare to use the internal parser, but it makes no difference. Would anyone tell me what I did wrong here? Many thanks. Dicker Von Samsung Mobile gesendet

3 2

Feature Request: serializable functions
by Marco Lettere 07 Nov '14

07 Nov '14

Hello all, just out of curiosity, would it be too hard to have a serialization tool for functions that does more or less the inverse of inspect:functions i. e. given a function item returns the full function code? The use case is that I want to send out a client:execute request that is a XQuery script where functions can be attached at runtime selecting them out of a "toolbox" xqm module. And of course I don't want to manually parse the xqm to cut out the required function which could be done but is not very elegant. Example: declare function local:f($i as xs:integer) as xs:integer{ $i + 1 }; inspect:serialize(local:f#1) would yield the string "declare function local:f($i as xs:integer) as xs:integer{ $i + 1 };" I've seen that even if it is not possible to serialize or cast to string a function item, if the function is assigned to a map, calling map:serialize yields something similar to the full function code. So I thought maybe the serialization mechanism is already in place and would just need a bit of generalization. Regards, Marco.

3 6

Re: [basex-talk] Feature Request: serializable functions
by Christian Grün 06 Nov '14

06 Nov '14

Hi Carl, In the BaseX query parser, tokenization and parsing is a joint operation. in the past, we thought about splitting these steps, as the tokens could also be used in the GUI to provide better highlighting. However, we'd probably need some more coders interested in making that happen.. However, thanks for the suggestion, Christian On Thu, Nov 6, 2014 at 3:12 PM, Carl Leitner <litlfred(a)gmail.com> wrote: > On a somewhat related note, I assume that when compiling xquery you are > creating some kind of token stream. Would it be possible to add a function > like > xquery:tokenize ($query as xs:string) as item()* > which takes as input an xquery string and output the token string. > > Presumably this could be another route used to meet the use case discussed > below to select functions from a toolbox module. > > Here is an example of similar functionality in PHP: > http://php.net/manual/en/function.token-get-all.php > > Cheers, > -carl > > > On Nov 6, 2014, at 8:26 AM, Christian Grün <christian.gruen(a)gmail.com> > wrote: > > Hi Marco, > > You may be surprised (or not) that I thought about a similar > functionality. Indeed I wondered if we could allow function items as > input for client:query and xquery:evaluate. > > I like your idea of providing an explicit serialization function. For > several reasons, we cannot guarantee that the serialized > representation of an XQuery expression will always be executable. In > some case, it's even not possible because the optimizer creates new > expressions that have no counterpart in the original XQuery language. > If we provide an explicit function for serializing function code, > however, we'd be able to point this out. > > I have added a new GitHub issue [1]. > > Christian > > [1] https://github.com/BaseXdb/basex/issues/1021 > > > On Wed, Nov 5, 2014 at 3:23 PM, Marco Lettere <marco.lettere(a)dedalus.eu> > wrote: > > Hello all, > just out of curiosity, would it be too hard to have a serialization tool for > functions that does more or less the inverse of inspect:functions i. e. > given a function item returns the full function code? > The use case is that I want to send out a client:execute request that is a > XQuery script where functions can be attached at runtime selecting them out > of a "toolbox" xqm module. And of course I don't want to manually parse the > xqm to cut out the required function which could be done but is not very > elegant. > > Example: > > declare function local:f($i as xs:integer) as xs:integer{ $i + 1 }; > > inspect:serialize(local:f#1) > > would yield the string "declare function local:f($i as xs:integer) as > xs:integer{ $i + 1 };" > > I've seen that even if it is not possible to serialize or cast to string a > function item, if the function is assigned to a map, calling map:serialize > yields something similar to the full function code. So I thought maybe the > serialization mechanism is already in place and would just need a bit of > generalization. > Regards, > Marco. > >

1 0

Fwd: Preventing unescaping of entities
by Christian Grün 06 Nov '14

06 Nov '14

Hi James, Beforehand: Please send your mails to basex-talk(a)mailman.uni-konstanz.de; otherwise, they won't be directed to everyone. Currently, there is no way to prevent the unescaping the entities (the XML and XQuery specifications do not foresee this). One way to enforce the escaping of certain Unicode characters could be to provide character maps when serializing data [2]. Christian [1] http://www.w3.org/TR/xquery-31/#id-serialization [2] http://www.w3.org/TR/xslt-xquery-serialization-30/#XML_USE-CHARACTER-MAPS ____________________________________ On Wed, Nov 5, 2014 at 5:47 PM, James Sears <james.hn.sears(a)gmail.com> wrote: > How can I prevent unescaping of entities? Such that when I import an element > whose value is expressed in hexadecimal - i.e. ® - I do not want an > BaseXClient.Query result containing the non hexadecimal representation - > i.e. ®. > > What I'd like out is what I imported in :-)

1 0

Type of context in remote queries
by Marco Lettere 04 Nov '14

04 Nov '14

Hi all, I'm not able to provide myself an answer to the fact that the first query returns an exception (cannot cast string to node) whereas the second works perfectly. client:connect("localhost", 1984, "admin", "admin") ! client:query(., "declare context item as node() external; .", {"" := <a/>}) client:connect("localhost", 1984, "admin", "admin") ! client:query(., "declare variable $x as node() external; $x", {"x" := <a/>}) I understand that the context is serialized as a string but isn't it the possibility to pass the type information along with the query and avoid explicit serialization on the client and deserialization on the remote server as it happens with variables? Thanks, Marco.

2 5

Feature request
by Pieter Masereeuw 04 Nov '14

04 Nov '14

Hi! It would be nice if there were a feature that basex could skip certain directories during the import. Now I have great trouble to remove (and later restore) all .svn-folders (Subversion) because I don't want them to be imported when I create a database. Perhaps this is already a feature, but then I could not find it. In that case, perhaps a more conspicuous place in the documentation would be a good idea. Thank you for an excellent product! Pieter Masereeuw

4 3

WAR distribution
by Paul Swennenhuis 03 Nov '14

03 Nov '14

Hi, Last weekend I managed to deploy the BaseX WAR on the Amazon Web Services platform, as an 'Elastic Beanstalk' application. Now I want to create and manage databases and run queries via the REST interface. However, I am lost as how to do that. First, the BaseX pages tell me that the WAR distribution is 'deprecated'. (page http://docs.basex.org/wiki/Startup, remark "the WAR Application can be embedded in existing Java web servers (deprecated)." Why is the WAR distribution deprecated? Should I not use it anymore? And if so, how can I make a WAR out of the JAR distribution? Elastic Beanstalk can only deploy WAR files. Second, where to put the files? I can ssh into the application and transfer files, but where do I put database files I already created with the Windows version of BaseX? And where the .xq files? Paul

3 2

Upcoming: XMLPrague 2015
by Christian Grün 01 Nov '14

01 Nov '14

Dear all, In around three months, the next edition of XMLPrague will take place, and it will be the fourth time that we'll be organizing a Pre-Conference Meeting on Friday, February 13. As you all do so many exciting things with BaseX, we would be more than interested to have some of you as speakers! We are very thankful to those of you who have already talked on one of our previous meetings; it has been your contributions that made the past event so awesome! Please don't hesitate and tell us if you are interested in presenting your work to the members of the community. If you have talked before, you are of course invited as well. More to come, Christian

1 0

Bug in 7.9: REMOVE over WebDAV not working
by Andreas Jung 01 Nov '14

01 Nov '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, removing a folder/collection over WebDAV does not work. The problem can be easily reproduced by creating a folder/collection using 'cadaver' and then trying to remove it. I was also able to reproduce the problem using Python and a Python webdav driver. - -- Regards Andreas Jung andreas(a)andreas-jung.com about.me/andreasjung -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQGUBAEBAgAGBQJUVMa/AAoJEADcfz7u4AZjxVQLwMx+ZK++Q77dK9axdfVb2noz HMz3AJgd294hOFFH5ifJBhUwTai2C5v2gEfZ3xzDHfa9oLA2U241devfYDqioyJY 81aenfoOhY9fJOfI65h89sWYDgIFGZgzS+nyzXpLJtxwCgtbuGpRqStIlFrx8xky nqWC9Lq5UuxhhbF/MGWtwLtTps74XwNYuNMu5e2rq1W3D+UdqK7TlRUVu0kWbV+v ULBCZLIBd0NGeyCMXvdB4R6CGTtAAPx47U5N+/xxEBEpFf8UiZfhCz47fhqtsqrs v7hY1vatFr7d7uru5UtpHBQASlGfqopJAQ1gGELlBJrDNPsXCpjMx/4tDLbPaPAZ P3/ABdZJ25m2kMJpq9IChtIK5A/f+u75V0OLkpPeDLcO3r/zOjmKFmPfAfti3hU6 q7xomemCuKMO6ZeUetMsXJ3WQo3NKDaFHZXpkWkmADpT1y07nO+PuYj7lMZXdXyE Sd2s3YpamA2wBUBGdAJjQwvfEa3t/6A= =tyfN -----END PGP SIGNATURE-----

2 5

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk November 2014