BaseX-Talk

basex-talk@mailman.uni-konstanz.de

6 participants
5269 discussions

Issue with linebreak using REST since 7.7.1
by Yoann Maingon 25 Sep '13

25 Sep '13

Hi, I've got a simple node move PHP script (sorry for my terrible code, I'm an electronician!) 1. // get the node 2. $xquery = "XQUERY //noteitem[@id='$movedID']"; 3. $saveNode = $session->execute($xquery); 4. 5. // delete the node 6. $xquery = "XQUERY delete node //noteitem[@id='$movedID']"; 7. $content = $session->execute($xquery); 8. // insert the node 9. if ($nextID == 'last') { 10. $xquery = "XQUERY insert node ($saveNode) as last into //meeting[@id='$meetingID']/items " ; 11. $content = $session->execute($xquery); 12. } else { 13. echo $saveNode; 14. $xquery = "XQUERY insert node ($saveNode) before //meeting[@id='$meetingID']/items/noteitem[@id='$nextID'] " ; 15. $content = $session->execute($xquery); 16. } 17. $contentFull = "<MN>$content</MN>"; 18. echo $contentFull; If I look into the content that is saved, deleted and inserted I have the following: <noteitem status="new" commentsCounter="0" created_on="Tue, 24 Sep 13 12:09:29 +0000" modified_on="Tue, 24 Sep 13 12:09:29 +0000" id="MnNo524180f9587c1" genid="MnNo524180f9587c1" owner="1" type="question"> <notecontent>...</notecontent> </noteitem> It worked fine until the latest update. Where apparently the query breaks with the line break. It creates an error saying that the closing </noteitem> tag is missing. Just got back to 7.6 and it works well. any idea? Yoann Maingon CEO - mydatalinx +33664324966

2 1

feature request -- GUI database creation overall progress
by Graydon Saunders 25 Sep '13

25 Sep '13

Hi! Right now, creating a database in the GUI gives a per-file progress, which is accurate but not informative. Any chance of getting, in addition to the per-file progress, the overall progress of creating the database? Thanks! Graydon

2 1

empty tags
by Lars Johnsen 24 Sep '13

24 Sep '13

Hello BaseX developers! When using BaseX scripting to generate HTML, I got a problem with the representation of empty nodes. For example, my code has something like this in it <div> { ... some code...} </div> if ...some code... returns nothing, the div is empty as is labelled <div/>. This causes trouble in HTML, since <div/> is treated as if it was the start tag <div>, and will therefore nest over following divs. Is there a way for BaseX to output <div></div> instead? There is an ad hoc solution which checks if ...some code... is empty and inserts a blank in those cases, preventing the div from collapsing into one tag, but was hoping for a more general solution. All the best, Lars G Johnsen National Library of Norway

2 1

Caching RestXQ responses
by Wendell Piez 24 Sep '13

24 Sep '13

Hi, I'm in over my head on this one, but I have questions about running BaseX behind restXQ, specifically on whether I can have query responses cached. Does this happen already? (How can I determine this?) Does caching responses to queries under restXQ fall outside of BaseX's responsibilities? Is it a Jetty thing? Any advice in general, or links I can go to learn about this? Thanks, Wendell Wendell Piez | http://www.wendellpiez.com XML | XSLT | electronic publishing Eat Your Vegetables _____oo_________o_o___ooooo____ooooooo_^

2 1

Set Operator Examples
by John Best 24 Sep '13

24 Sep '13

Hi all, Where can I find examples using set operators... wrt BaseX. -- Have a nice day JBest

2 1

Snapshoting in baseX
by Simon Görke 23 Sep '13

23 Sep '13

Hi everybody, this is rather a general question than a concrete issue or a bug report: Does baseX provide any snapshoting-alike functionality, i.e. the possibility to automatically save (potentially) affected elements *before* an updating transaction is performed? We have a (existing) GUI which is used to edit data stored in a baseX database. For this GUI, we want to add undo/redo functionality for the user. Snapshoting would be a straightforward approach, but any other hints or ideas are also welcome (maybe using events?). Thanks in advance, Simon

2 1

Uninstall Removes Repo directory!
by James Wright 20 Sep '13

20 Sep '13

AH! Well its my fault. Several weeks of work lost because I uninstalled 7.7 and it removed the repo directory with all my modules! Just wanted to give the fair warning.. Time to get a drink... I was going to put that in Drop Box last week and never got to it!! - James

2 1

Namespace conflict in XQuery update
by alxarch 19 Sep '13

19 Sep '13

While trying to transform an xhtml document I ran into this general case: copy $ul := <ul xmlns="http://www.w3.org/1999/xhtml"> <li>item</li> <li>item</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 "[XUDY0024] New namespaces conflict with each other." error. After reading the XQuery update facility recomendation it wasn't clear to me if this is supposed to happen. Do I *have* to use chained copy statements to achieve both renaming a node an inserting an attribute? Thanks, Alex

2 1

Re: [basex-talk] New map syntax issue
by Daniël Knippers 18 Sep '13

18 Sep '13

Thank you for the swift reply Christian. Please do not feel obligated to let me know once this is fixed, it is not a blocking issue for me and I'm sure you can spend your time in better ways :-) I'm already glad it's been picked up this quickly. -- Daniël On Wed, Sep 18, 2013 at 9:28 PM, Christian Grün <christian.gruen(a)gmail.com>wrote: > Hi Daniël, > > the XQuery 3.1 grammar has not been finalized yet, but I agree that > our implementation is not what one would expect. I have tracked your > observation [1] and will let you know when a fix is available. > > Thanks, > Christian > > [1] https://github.com/BaseXdb/basex/issues/755 > > ___________________________ > > 2013/9/18 Daniël Knippers <dknippers(a)gmail.com>: > > Hi, > > > > Using the new map syntax of BaseX 7.7.1, I ran into this: > > > > let $m := { 'key':'val' } > > return $m('key') > > > > [XPST0003] Invalid key, simple expression expected. > > > > As it turns out, a space is required after the closing quote of the key. > > That is, the above example works fine when replacing 'key':'val' by > > 'key'<SPACE>:'val' > > > > This is not the case when using an integer key, i.e. this works fine: > > > > let $m := { 1:'val' } > > return $m(1) > > > > I'm not sure if this behavior is intentional, but I would guess it is not > > :-) > > > > Regards, > > Daniël > > > > _______________________________________________ > > BaseX-Talk mailing list > > BaseX-Talk(a)mailman.uni-konstanz.de > > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk > > >

2 2

New map syntax issue
by Daniël Knippers 18 Sep '13

18 Sep '13

Hi, Using the new map syntax of BaseX 7.7.1, I ran into this: let $m := { 'key':'val' } return $m('key') [XPST0003] Invalid key, simple expression expected. As it turns out, a space is required after the closing quote of the key. That is, the above example works fine when replacing 'key':'val' by 'key'<SPACE>:'val' This is not the case when using an integer key, i.e. this works fine: let $m := { 1:'val' } return $m(1) I'm not sure if this behavior is intentional, but I would guess it is not :-) Regards, Daniël

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk