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

Strange "group by" behavior
by Alexander Krasnogolowy 07 Oct '23

07 Oct '23

Given the following XQuery: let $input := <root> <item><key>a</key><value>1</value></item> <item><key>b</key><value>2</value></item> <item><key>b</key><value>3</value></item> </root> let $map := map:merge(( map:entry(1, "A"), map:entry(2, "B"), map:entry(3, "C") )) for $result in $input/* let $key := $result/key/text() let $value := $result/value/text() group by $key return map:get($map, $key) When trying to execute that query, I get the error "Item expected, sequence found: (map {1:"A",2:"B",3:"C"}, map {1:"A",2:"B",3:"C"}). But why does it group the map? It isn't part of that for-loop but rather some kind of global variable. Or do I misunderstand the "group by" clause? I only expect the $value to be grouped which results in a sequence. Thanks, Alex

3 3

BaseX-10.7: error selecting CSV parser when creating a new database in the GUI
by ron.vdbranden＠gmail.com 03 Oct '23

03 Oct '23

Hi all, I think I'm experiencing a regression in the BaseX-10.7 GUI w.r.t. the CSV parser, when creating a new database. When I select CSV in the "Input format" dropdown on the "General" tab, nothing seems to be selected: * the dropdown stays open * no file mask is changed in "File patterns" * the "Parsing" tab doesn't show the CSV parsing options Additionally, I'm seeing logs starting with: Exception in thread "AWT-EventQueue-0" java.lang.ArrayIndexOutOfBoundsException: arraycopy: length -1 is negative at java.base/java.lang.System.arraycopy(Native Method) at org.basex.util.Array.copy(Array.java:124) This looks like an error to me; worked perfectly in 10.6. Best, Ron

2 2

XSLT in BaseX - no node parameters
by Hans-Juergen Rennau 25 Sep '23

25 Sep '23

Dear BaseX folks, the documentation of the XSLT module says: "Variables can be bound to a stylesheet via $arguments (only strings are supported when using XSLT 3.0 and Saxon). " That is a pity! Are there plans to remove this limitation? Kind regards,Hans-Jürgen

2 3

Element construction - namespace error - bug?
by Hans-Juergen Rennau 25 Sep '23

25 Sep '23

Dear BaseX folks, constructing elements, I encounter a problem with namespaces which I do not understand. Is it a bug or do I overlook something? To reproduce the problem you need to create an XML file "doc.xml" with this content: <doc xmlns="http://basex.org/simply/the/best"> <foo bar="1"> <peng/> </foo></doc> And here's the query: declare namespace f="http://basex.org/does/its/thing"; declare function f:pretty($n as node()) as node()? { typeswitch($n) case document-node() return document {$n/node() ! f:pretty(.)} case element() return element {node-name($n)} { in-scope-prefixes($n) ! namespace {.} {namespace-uri-for-prefix(., $n)}, $n/@* ! f:pretty(.), $n/node() ! f:pretty(.) } default return $n}; let $doc := doc('doc.xml')return f:pretty($doc) What I get is this error: Stopped at C:/projects/tableman/prototype/thieme-showcase/xq/demo-namespace-problem.xq, 8/33:[XQDY0102] Duplicate declaration of namespace 'http://basex.org/simply/the/best'. Stack Trace:- C:/projects/tableman/prototype/thieme-showcase/xq/demo-namespace-problem.xq, 11/33- C:/projects/tableman/prototype/thieme-showcase/xq/demo-namespace-problem.xq, 11/33- C:/projects/tableman/prototype/thieme-showcase/xq/demo-namespace-problem.xq, 6/63- C:/projects/tableman/prototype/thieme-showcase/xq/demo-namespace-problem.xq, 17/16 Strangely enough, you do not get the error if you copy the contents of doc.xml into the query: let $doc := <doc .../>return f:pretty($doc) You also do not get the error if you remove the @bar attribute in the document. Kind regards,Hans-Jürgen

2 3

Re: [basex-talk] Set Strip Whitespace Mode
by Christian Grün 15 Sep '23

15 Sep '23

Hi Hans-Jürgen, > question: what is the recommended way of ensuring that an application calling BaseX via command-line (basex ...) uses a certain strip whitespace mode (true or false), if the application is deployed on servers with different BaseX versions? Option -w cannot naively be used, as it toggles the strip whitespace mode, so the effect depends on the version. Sounds challenging. You can set the STRIPWS option to an explicit value… basex -c"SET STRIPWS false" query.xq ... …but this will fail as the comparable BaseX 9 option was called CHOP. You could use XQuery to retrieve the version number… data(db:system()//version) …or to check if a specific option is supported: try { prof:void(db:option('chop')), '!' } catch * { '?' } In general, I would recommend updating to the latest version whenever possible… Hope this helps, Christian

1 0

Set strip whitespace mode
by Hans-Juergen Rennau 15 Sep '23

15 Sep '23

Dear BaseX folks, question: what is the recommended way of ensuring that an application calling BaseX via command-line (basex ...) uses a certain strip whitespace mode (true or false), if the application is deployed on servers with different BaseX versions? Option -w cannot naively be used, as it toggles the strip whitespace mode, so the effect depends on the version. I have not found out how to determine the version of BaseX reliably, using XQuery or a command. So how can a script decide whether or not to use -w? Thank you for help. Kind regards,Hans-Jürgen

1 0

Variable declaration of variable containing a recursive function triggers an error! (golden oldy)
by Rob Stapper 12 Sep '23

12 Sep '23

Hi Christian, I’ve addressed this issue already in feb 2022 and nov 2020. Since I think it is a bug I am coming back on it again. Hopefully with a better formulated argument this time. There is a easy workaround but if code is generated, as in my case, having to change the code manually each time after generation is getting pretty tedious. (and I very much like my code to be consistent) So, why is it that a function-declaration of a function that is recursive doesn’t trigger an self-depending-error and a variable-declaration that has such a function assigned to, does? In the first situation preventing an endless loop is, obviously and rightly so, treated as a programmers responsibility. However in the second situation this responsibility is taken away from the programmer by not even allowing the situation. This is not consistent. Sure, the compiler should and does detect cyclic variable-assignments but that is actually not the case here. Assigning a function to a variable is per definition a non-cyclic assignment. Possible recursiveness in this case should be treated the same as with a function-declaration, that is, as a programmers responsibility. I hope the above makes some sense. Is it worth an effort to address this issue? It would probably make the compiler code even less complex. Cheers, Rob Stapper Sent from Mail for Windows -- This email has been checked for viruses by Avast antivirus software. www.avast.com

2 1

Docker
by Diego Alcorta 05 Sep '23

05 Sep '23

I see that docker images have not been updated in over 2 years. I was wondering what the best way to deploy basex in kubernetes is. -- Diego Alcorta dalcorta(a)gmail.com ----------------------------------------------------- "If patience is a virtue, and ignorance is bliss, you can have a pretty good life if you're ignorant and willing to wait" -----------------------------------------------------

2 1

Suche in allen BaseX-Talk Archives
by Dietmar Posselt 04 Sep '23

04 Sep '23

Hallo, gibt es eine Möglichkeit in allen BaseX-Talk Archives nach Begriffen, "weblogic" oder "tamino", zu suchen? Gruss Dietmar

2 1

Support non-admin user access to database admin interface (DBA)
by Matthew Dziuban 30 Aug '23

30 Aug '23

Hi all, While the subject might sound contradictory, I'm curious what you think about opening up the DBA code to allow non-admin users to access it and perform actions for which they have permissions? I currently maintain and run a fork of the DBA web app at work to make this possible, but I'd love to have the behavior built into BaseX if possible. You can view the changes I've made against BaseX 10.7 here: https://github.com/mblink/basex-webapp/compare/upstream-webapp...webapp-10.7 If you're open to this, I'd be happy to open a pull request with my changes! Thanks, Matt

2 5