BaseX-Talk July 2018

basex-talk@mailman.uni-konstanz.de

25 participants
37 discussions

serialize vs csv:serialize
by Giuseppe Celano 20 Jul '18

20 Jul '18

Hi All, I am not sure whether the serialize function is working properly (the first example works, the second does not, because instead of tabs I get commas, and there is no way to specify to add the header) <csv> <record> <a>f</a> <b>f</b> <c>f</c> <d>f</d> <e>f</e> <f>f</f> </record> </csv> => csv:serialize(map{"header":"yes", "separator": " "}) return a b c d e f f f f f f f <csv> <record> <a>f</a> <b>f</b> <c>f</c> <d>f</d> <e>f</e> <f>f</f> </record> </csv> => serialize(map{"method":"csv", "item-separator": " "}) f,f,f,f,f,f Thanks! Giuseppe

2 1

Re Re Add line-number function
by Павел Павлов 16 Jul '18

16 Jul '18

Hi! Users send to us xml files according published xsd scheme. And they can use any software: any xml editor or special editors, developed by third companies, with textbox'es for fill business objects. So, our application does not have a graphical interface. Our software' main goal is to validate xml files by some business logic rules written in xquery language. Result of such validation is xml file with text that is all OK or there are errors. Errors are explained by xpath to error node and text description with some text for example "Line 100: The quantity of cows must be greater than 0". Result send to users as answer. And users want to see line numbers... >Hi Pavel, > >What kind of editor are your users using? If they use an XML editor >proper, there will probably be a means to jump to a location specified >by an XPath expression. > >If they are using an ordinary text editor, how do you prevent them from >messing up the XML in the first place? Ordinary, non-IT users tend to >render XML moot if left without appropriate tooling. > >If you are a visual editor that hides the tags, it should be easier to >insert error feedback by XPath location than by line number. > >Maybe you want to create an HTML rendering of the input where you >highlight the errors (using their XPath locations). Then the users have >enough context to locate the erroneous piece in the original XML input. > >I?m just thinking of workarounds since I assume that the notion of line >numbers is not something that can easily be added to the BaseX storage >layout. As someone who often deals with non-indented XML files that >consist of a single line or with XML that is formatted&indented with >varying line lengths, I have come to avoid relying on line number >information altogether. > >Gerrit > > >On 16.07.2018 08:45, ????? ?????? wrote: >> Thanks for the detailed answer. >> >> Our software is developed in .NET. And we use BaseX as a Xquery processor. >> We use fn:path and return path to error element to user. But it's not >> enough. >> Our users are ordinary people, not IT, and they want to see in which >> lines of xml files there are mistakes. >> Now after execution of xquery by BaseX our application load xml file (in >> memory to XDocument object from .NET XML) with specified flag >> SetLineInfo. Then we execute returned xpath to select node in loaded xml >> file and get line number of selected node. Then we return line number to >> user. >> That is, we have to load the file by .NET only to get the line number. >> If BaseX could do it itself we wouldn't have to load xml file at all. It >> would be a great benefit for us. >> >> Is it possible to add some _mode_ in BaseX to store line numbers even >> with additional memory and undefined line numbers on changed or updated >> xml nodes? >> >> ???????, 6 ???? 2018, 15:24 +07:00 ?? Christian Gr?n >> < christian.gruen(a)gmail.com >: >> >> Hi Symantis, >> >> The original line numbers are not stored in XML databases (they may >> change after updated, and would consume additional memory), so you >> won?t be able to retrieve them with XQuery. >> >> As far as I know, this does not work in eXist-db either; the eXist >> link you referenced gives you the line of the util:line-number >> expression in your XQuery module. As Fabrice pointed out (thanks!), >> this could also be realized with $err:line-number. >> >> With Saxon, it works indeed. However, you?ll need you use the -l >> command line option (otherwise, due to performance considerations, >> line numbers will be discarded as well). >> >> On query/database level, there are two ways to get a direct reference: >> ? With fn:path, you get an XPath expression that points to your node. >> ? With db:node-pre [1], you get a direct reference to the node in a >> database. >> >> Best, >> Christian >> >> [1] http://docs.basex.org/wiki/Database_Module#db:node-id >> >> > >-- >Gerrit Imsieke >Gesch?ftsf?hrer / Managing Director >le-tex publishing services GmbH >Weissenfelser Str. 84, 04229 Leipzig, Germany >Phone +49 341 355356 110 , Fax +49 341 355356 510 >gerrit.imsieke(a)le-tex.de, http://www.le-tex.de > >Registergericht / Commercial Register: Amtsgericht Leipzig >Registernummer / Registration Number: HRB 24930 > >Gesch?ftsf?hrer / Managing Directors: >Gerrit Imsieke, Svea Jelonek, Thomas Schmidt

3 2

Add line-number function
by Павел Павлов 16 Jul '18

16 Jul '18

> >Hello, could the $err:line-number [1] variable help you ? > >[1] http://docs.basex.org/wiki/XQuery_3.0#Try.2FCatch > >Best regards, > >Fabrice ETANCHAUD >cerfrancepch No, $err:line-number show line number of xquery file. I want this: Example.xml -> 1: <root> 2: <child> 3: <grandchild>text1</grandchild> 4: <grandchild>text2</grandchild> 5: <grandchild>text3</grandchild> 6: <grandchild>text4</grandchild> 7: </child> 8: </root> Xquery -> let $f := doc("example.xml") let $e := $f/root/child[1]/grandchild[3] let $line := line-number($e) And I want get $line = 5 !

5 9

<rest:response> - unclear strategy of setting header during serialization
by Bogdan Bogucki 14 Jul '18

14 Jul '18

Hello, I encountered strange behavior during HTTP response. I need to set custom header Access-Control-Allow-Origin:*. To do that I am using custom response. Following code is working and set required header: declare %rest:POST("{$json}") %rest:path("/ping") function drpg:ping( $json as xs:string ) as element()* { <rest:response> <http:response status="200" message="OK"> <http:header name="Access-Control-Allow-Origin" value="*"/> <http:header name="Content-Type" value="text/html"/> </http:response> </rest:response>, let $p := json:parse($json) return ($p/json/data/_/_/_)[last()] }; Response header: Access-Control-Allow-Origin * Content-Length 11 Content-Type text/html;charset=utf-8 Date Sat, 14 Jul 2018 09:17:18 GMT Server Jetty(9.4.9.v20180320) I want to return plain text, so when I change return parameter to xs:string* and add data function header from <rest:response> is overwritten. Response header: Content-Length 6 Content-Type application/xml; charset=UTF-8 Date Sat, 14 Jul 2018 09:26:59 GMT Server Jetty(9.4.9.v20180320) Example code: declare %rest:POST("{$json}") %rest:path("/drpg/ping") function drpg:ping( $json as xs:string ) as xs:string* { <rest:response> <http:response status="200" message="OK"> <http:header name="Access-Control-Allow-Origin" value="*"/> <http:header name="Content-Type" value="text/html"/> </http:response> </rest:response>, let $p := json:parse($json) return data(($p/json/data/_/_/_)[last()]) }; Why does header is overwritten ? I think if header is set explicitly it shouldn't be overwritten. Best Regards Bogdan Bogucki

2 4

Re: [basex-talk] BaseX, Java 9: Improved macOS support
by James Ball 13 Jul '18

13 Jul '18

As a very regular BaseX user on the Mac I’m very grateful for the work done to keep BaseX running well on macOS - so thank you. I’ve downloaded the new snapshot - are there any particular areas that you’d particularly like feedback about? Kindest regards, James > Date: Thu, 12 Jul 2018 23:50:40 +0200 > From: Christian Gr?n <christian.gruen(a)gmail.com> > To: BaseX Support <basex-talk(a)mailman.uni-konstanz.de>, Alexander > Holupirek <ah(a)basex.org> > Subject: [basex-talk] BaseX, Java 9: Improved macOS support > Message-ID: > <CAP94bnMqTkHXhz2C8xvUTEBa-a8TODvDRM-EGXH8U=ixeqBfmA(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi all, > > Our team member Alex has spent valuable time to improve BaseX GUI > compatibility with recent versions of macOS and Java. While the final > version is still under way, we invite you to give early feedback on our > latest stable snapshot [1]. > > Have fun everyone, > Christian > > [1] http://files.basex.org/releases/latest/ >

1 0

maps
by Giuseppe Celano 13 Jul '18

13 Jul '18

Hi Is it possible to preserve the order of the keys in a map when the map is returned?: map{"b": 2, "c": 2, "a": 3} return map { "a": 3, "b": 2, "c": 2 } Thanks! Giuseppe

2 5

BaseX, Java 9: Improved macOS support
by Christian Grün 13 Jul '18

13 Jul '18

Hi all, Our team member Alex has spent valuable time to improve BaseX GUI compatibility with recent versions of macOS and Java. While the final version is still under way, we invite you to give early feedback on our latest stable snapshot [1]. Have fun everyone, Christian [1] http://files.basex.org/releases/latest/

2 1

http:send-request - problem with form data
by Bogdan Bogucki 13 Jul '18

13 Jul '18

Hello, I have problem with http:send-request. I want to send post method request with form data but I encountered problem with characters encoding. Example: Request: for $x in http:send-request( <http:request method='post' href='http://localhost:3333'> <http:header name="User-Agent" value="Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36"/> <http:body media-type='application/x-www-form-urlencoded; charset=UTF-8'> <![CDATA[start=0&length=100&sort=date_type&page=0&size=100]]> </http:body> </http:request> )[2]/json/data/results/content return $x Optimized Query: util:item-at(http:send-request(element Q{http://expath.org/ns/http-client}request { (attribute method { ("post") }, attribute href { ("http://localhost:3333") }, element Q{http://expath.org/ns/http-client}header { (attribute name { ("User-Agent") }, attribute value { ("Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36") }) }, element Q{http://expath.org/ns/http-client}body { (attribute media-type { ("application/x-www-form-urlencoded; charset=UTF-8") }, "
 start=0&length=100&sort=date_type&page=0&size=100
 ") }) }), 2)/json/data/results/content Request send: POST / HTTP/1.1 User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Content-Type: application/x-www-form-urlencoded; charset=UTF-8 Host: copart.com:3333 Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection: keep-alive Content-Length: 75 start=0&length=100&sort=date_type&page=0&size=100 Payload is not correctly encoded it should be: start=0&length=100&sort=date_type&page=0&size=100 How can I force function http:send-request to serialize CDATA without escaping ? Best Regards Bogdan Bogucki

3 10

Re: [basex-talk] Number of Databases in BaseX
by Christian Grün 12 Jul '18

12 Jul '18

Hi Martin (cc to the mailing list), The max. number of allowed databases depends on the directory limit of your operating system. In practice, it’s advisable to find a good ratio between size and number of databases, because your file system may require too much time to open a particular database if you have created too many instances. Best, Christian Martin Lourduswamy <martin.louis(a)gmail.com> schrieb am Fr., 13. Juli 2018 00:56: > Hi, > I know each DB is a actually a path in BaseX, > Is there a limit on the number of Databases a single Basex instance can > host, > Please let me know when you have sometime, > > Thanks, > Regards > Martin Lourduswamy >

1 0

slash operator in Basex 9.0.2
by Giuseppe Celano 06 Jul '18

06 Jul '18

I have noticed that in BaseX 9.0.2 a query like <j>fgrtu</j>/data(.)/replace(., "g", "h") gets evaluated (returning "fhrtu"), while in BaseX 8.x, Exist, and Zorba I get an error message (since, as expected, replace() is preceded not by a node but a string). Is this a bug? Ciao, Giuseppe

2 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk July 2018