July 2012 - BaseX-Talk - mailman.uni-konstanz.de

Does CREATing a DB OPEN it?
by Godmar Back 26 Jul '12

26 Jul '12

I'm still seeing this problem (Database 'PUB_feed_libx_dot_editions_at_gmail...' is currently opened by another client). I was able to connect via org.basex.BaseXClient to the database and saw, via 'SHOW SESSIONS', that the database in question was listed like so: > SHOW SESSIONS 3 session(s): - admin [127.0.0.1:35515]: ts_20120725_dot_213235_dot_723_feed_libx_dot_editions_at_gmail_dot_com_core - admin [127.0.0.1:37210] - admin [127.0.0.1:44610]: PUB_feed_libx_dot_editions_at_gmail_dot_com_core >From the code in Sessions.java/Context.java, I inferred that the db in question ('PUB_feed_libx_dot_editions_at_gmail_dot_com_core') was the 'current data reference' of session :44610. How can that be? As a reminder, I'm not using any 'OPEN' commands... So I've examined the logs when this db became the 'current' database of that session, and that, apparently, happened when it was created: 13:58:21.113 [127.0.0.1:44610]: ts_20120725_dot_135820_dot_723_feed_libx_dot_editions_at_gmail_dot_com_core CREATE DB PUB_feed_libx_dot_editions_at_gmail_dot_com_core [...] 13:58:21.164 [127.0.0.1:44610]: PUB_feed_libx_dot_editions_at_gmail_dot_com_core OK 50.95 ms Is this an undocumented side-effect of 'CREATE DB'? Is it necessary to follow every 'CREATE DB...' statement with a 'CLOSE' statement to avoid that the session in which the db was created keeps it open? It is not mentioned here: http://docs.basex.org/wiki/Commands#CREATE_DB If true, I find this rather unusual - and certainly unexpected - it would be as if a 'CREATE DATABASE' statement in SQL automatically issued a 'USE'... command. - Godmar

3 6

Re: [basex-talk] Does CREATing a DB OPEN it?
by Michael Seiferle 26 Jul '12

26 Jul '12

Am 26.07.2012 um 16:15 schrieb Michael Seiferle: > Hi Godmar, > Am 26.07.2012 um 15:47 schrieb Godmar Back: > >> Ok - you want your users to guess what weird design decisions you made, and document them. Unusual request. > thank you for your feedback. > http://docs.basex.org/wiki/Commands#CREATE_DB >> Creates the database [name] with an optional [input] and opens it. > Sorry this is not clearly stated on the Server’s documentation page, as Christian said writing documentation is a lot of work, feel free to improve when you feel something is missing. > > Thanks. :-) > > Michael whoops, I just saw Christian added this just before. Still, feel free to ask or improve the documentation yourself. Michael

1 0

Re: [basex-talk] xslt:transform, spaces and mixed content
by Andy Bunce 26 Jul '12

26 Jul '12

>I already have that, along with the boundary-space option. >declare boundary-space preserve; >declare option db:chop 'no'; I have the same problem with RESTXQ I guess this is relevant https://github.com/BaseXdb/basex/issues/548 But I believe this problem has not always been there with RESTXQ. Using the API (via Node) without these declares I do not get the problem. Surely special declarations should not be required to, for example, get<spaces/>here for html o/p? /Andy

1 0

add to database basexclient - skip non-well formed xml files
by Jarosław Kowalewski 25 Jul '12

25 Jul '12

Hi, how can I skip non-well formed xml files in command line import. Basexclient add. With basexgui it's possible. thx Jarek

2 4

namespace bug in BaseX 7.3 - produces invalid XML
by Godmar Back 24 Jul '12

24 Jul '12

After upgrading to 7.3, our application broke. BaseX returns this (ill-formed) XML: <result-extract> <libx:body xmlns:libx="http://libx.org/xml/libx2" xmlns=" http://www.w3.org/2005/Atom">... that searches by ISBN */ var cue = new libx.cues.CatalogCue('i', tuple.isbn); cue.insertBefore(tuple.position); cue.image.setAttribute('width', '16'...</libx:body> </result-extract> resulting in: [Fatal Error] :61:237: Attribute "xmlns" bound to namespace " http://www.w3.org/2005/Atom/" was already specified for element "mark". The wrong XML appears numerous times inside tag. A element should not have more than one xmlns= attribute (why it has any, btw, I don't understand). The ill-formed output appears to be produced by the 'ft:extract()' function; here's an excerpt from the XQuery: for $extract in $entry/descendant::*[text() contains text "ISBN"] return <result-extract>{ft:extract($extract[text() contains text "ISBN"])}</result-extract> This is a show stopper that prevents us from upgrading to 7.3, obviously - let me know if you can fix this with the information provided, or if you need a complete test case. Is this issue fixed in the last snapshot? - Godmar

3 9

Validation using xs:include
by Huib Verweij 24 Jul '12

24 Jul '12

Hi, I am trying to use the excellent validation function. It used to work great, however, recently we added a xs:include statement. Now the validator can't find the included schema (that is located in the same directory as the including schema). I think the validator is missing a ResourceResolver. It works fine though if I include an absolute path. But absolute paths tend to only work on one machine. Any help is much appreciated. Hartelijke groet, Huib Verweij. Verstuurd vanaf mijn iPhone

2 3

Context node required problem
by John Morin 24 Jul '12

24 Jul '12

Hi I am trying to pass a string to my XQuery as a parameter, $input below. It seems that the string is not being interpreted as XML as I get the following message when I run the query from my .Net client: Stopped at line 14, column 68: [XPTY0019] Context node required for sglines; xs:string found. I believe I don't have the syntax of "declare context item as element(sglines) := document {$input/sglines};" quite right, and maybe " for $i in //line" The XML I am passing in as a parameter is: <sglines> <line lineId="41" note="1064"/> <line lineId="3" note="0"/> <line lineId="5" note="0"/> <line lineId="7" note="0"/> <line lineId="11" note="0"/> <line lineId="12" note="0"/> <line lineId="33" note="0"/> <line lineId="80" note="0"/> <line lineId="34" note="0"/> <line lineId="50" note="0"/> <line lineId="51" note="0"/> <line lineId="52" note="0"/> <line lineId="60" note="0"/> <line lineId="61" note="0"/> <line lineId="80" note="0"/> </sglines> Help would be much appreciated. Thanks Best regards John Morin declare namespace dp = "http://www.autodata.ltd.uk/namespaces/content-aggregation"; declare namespace ad = "http://autodata.ltd.uk/technical_topic"; (: return a deep copy of the element withouth namespaces :) declare namespace xf = "http://tempuri.org/vijfhuizen/com/myMessage/"; declare variable $input external; declare context item as element(sglines) := document {$input/sglines}; declare function xf:strip-namespace($e as element()) as element() { element { xs:QName(local-name($e)) } { for $child in $e/(@*,node()) return if ($child instance of element()) then xf:strip-namespace($child) else $child } }; let $sgline := $input return <aggregation> { for $i in //line let $id := $i/@lineId let $note := $i/@note let $elm := //dp:aggregation let $data := $elm/dp:content[@dataLineId=$id and @noteNumber=$note] return if(fn:empty($data)) then "" else xf:strip-namespace($data) } </aggregation> IMPORTANT NOTICE: This email and any attachments are confidential and are protected by copyright and/or database rights and are intended for the addressee only. If you are not the named recipient, you must not use, disclose, reproduce, copy or distribute the contents of this communication. If you have received this in error, please contact the sender and then delete this email from your system. The integrity of email across the Internet cannot be guaranteed. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of email transmission. Although Autodata Limited has taken precautions to ensure no viruses are present in this email or any attachments, the company cannot accept any responsibility for any loss or damage arising from the use of this email or attachments. Autodata Limited, Priors Way, Maidenhead Berkshire, SL6 2HP, England, UK. Registered as a limited company in England, UK. Registration number 1062717. VAT number GB 208 4782 54 000.

2 3

EXPath File Module
by Christian Grün 23 Jul '12

23 Jul '12

Hi all, the most recent version of the File Module has now been published on EXPath: http://expath.org/spec/file You may be interested to hear that the EXPath Project is now an official W3 Community Group: http://www.w3.org/community/expath/ This increases the chance that other XQuery Processors will also implement this and forthcoming modules: All the best, Christian PS: BaseX 7.4 can be expected in August or September.

1 0

Question concerning querying cyclic network xml-structure.
by Rob 20 Jul '12

20 Jul '12

Hi, Can you please help me solving a challenge I have with a specific type XML-query? Ive a bunch of XML-files that are referencing each other. So, a XML-file can reference to multiple XML-files and a XML-file can be referenced to by multiple XML-files. This whole reference-structure could be cyclic. Actually an m:n relationship between XML-files with possible cyclic structure. The standard solution would be to build a recursive-routine for processing an XML-file that, before actually processing the XML-file, checks in some way, for example with some sort of file-in-process-buffer, if the XML-file isnt already being processed. If not store the name in this buffer, processes the XML-file and initiate the recursive routine for the referenced XML-files. A structure like this (not real code (at all)): ============================================================== INSTANTIATE Guard FROM COLLECTION PROCESS-RECURSIVELY( XML-fileName) { PROCESS( XML-fileName) ITERATE Called-XML-file THROUGH XML-file//call-ELEMENT { IF NOT ( Guard.EXISTS( Called-XML-file.NAME) { Guard.ADD( Called-XML-file.NAME) PROCESS-RESURSIVELY(Called-XML-file.NAME) } } } PROCESS-RESURSIVELY(start-file) ============================================================= I found out that, but I could be mistaken, that the standard W3C-XML-tooling (XPATH, XQUERY, XLST) cant handle this situation because of their declarative nature. Recursiveness is possible with these tools but only in a linear way not in an iterative way. That is why Im looking for alternatives. Hopefully BaseX can help me out here. Ive BaseX and the JAVA-examples in eclipse running. Im b.t.w. nor a JAVA- nor an eclipse-expert so it was a bit of a struggle, but I managed. My question: What is the best way to approach this challenge? Can you give me some tips? Kind regards, Rob Stapper Meine frage ist in English weil mein Deutsch nicht so gut is wie mein Englisch. Enschuldigung dafür. ;-) _____ I am using the Free version of SPAMfighter <http://www.spamfighter.com/len> . SPAMfighter has removed 501 of my spam emails to date. Do you have a slow PC? <http://www.spamfighter.com/SLOW-PCfighter?cid=sigen> Try free scan!

5 11

Single restxq call, multiple db:replace. Second one always fail, but the error message seems unrelated.
by France Baril 18 Jul '12

18 Jul '12

Hi, I have a process where for each input file, I must create 2 output files. For some reason, I seem to be unable to use more than 1 db:replace in the same function. I have tried pieces of code separately to ensure that every individual piece works. They do work. For your information, I have included my tests as comments after the function. (: param $lang is the desired target language of the translation :) declare %rest:path("/admin/convert-to-xliff") %rest:GET %rest:query-param("lang", "{$lang}", '') updating function admin:convert-to-xliff($lang as xs:string){ (: Src language is assumed to always be en-us as per business rules:) let $src-lang := "en-us" for $x in app:open-db($src-lang) let $xliff-stylesheet := app:get-translation-xliff-to-xsl() let $skeleton-stylesheet := app:get-translation-xliff-skeleton-xsl() let $params := map {"lang-to" := $lang} let $target-uri := replace(base-uri($x), $src-lang, $lang) let $target-skeleton-uri := replace($target-uri, '.xml', '_xliffskeleton.xml') let $xliff-doc := xslt:transform($x, $xliff-stylesheet, $params) let $xliff-skeleton := xslt:transform($x, $skeleton-stylesheet) return db:replace("Translated-units", $target-uri, document{$ xliff-doc}), db:replace("Translated-units", $target-skeleton-uri, document { $xliff-skeleton}) }; (: db:replace("Translated-units", $target-uri, document{$xliff-doc}) --- Creates the expected files in the expected location :) (: db:replace("Translated-units", $target-skeleton-uri, document {$xliff-skeleton}) --- Creates the expected files in the expected location :) (: concat($target-uri, ' --- ', $target-skeleton-uri) --- remove decl as updating function to test this, both paths are set :) - I tested the $target-uri and $target-skeleton-uri as strings, and they both get the expected values as string outputs. - The db:replace for each of them works individually. - However, when I try 2 db:replace, the second one return an error: [XPST0008] Undefined variable $target-skeleton-uri. - If I reverse the db:replace, the 'new' second one gets the error: [XPST0008] Undefined variable $target-uri. Therefore, it looks like it has nothing to do with the fact that the variable is undefined. Any clue? Thanks, France Baril P.S. I'm using BaseX 7.2.1 -- France Baril Architecte documentaire / Documentation architect france.baril(a)architextus.com (514) 572-0341

2 2