BaseX-Talk January 2018

basex-talk@mailman.uni-konstanz.de

21 participants
27 discussions

BaseX 9.0 sql:prepare not working
by Jan Dölle 22 Jan '18

22 Jan '18

Hi, the function sql:prepare it not longer working Best Regards Jan ( sql:init("org.sqlite.JDBC"), let $conn := sql:connect("jdbc:sqlite:database.db") let $prep := sql:prepare($conn, "select 'Nothing'") let $result := sql:execute-prepared($prep) return ( $result, sql:close($prep), sql:close($conn) ) ) -> Improper use? Potential bug? Your feedback is welcome: Contact: basex-talk(a)mailman.uni-konstanz.de Version: BaseX 9.0 beta Java: Oracle Corporation, 1.8.0_151 OS: Linux, amd64 Stack Trace: java.lang.NullPointerException at org.basex.util.Token.string(Token.java:87) at org.basex.query.func.sql.JDBCConnections.add(JDBCConnections.java:42) at org.basex.query.func.sql.SqlPrepare.item(SqlPrepare.java:27) at org.basex.query.func.sql.SqlPrepare.item(SqlPrepare.java:1) at org.basex.query.expr.ParseExpr.value(ParseExpr.java:71) at org.basex.query.expr.gflwor.Let$LetEval.next(Let.java:177) at org.basex.query.expr.gflwor.GFLWOR$1.next(GFLWOR.java:87) at org.basex.query.QueryContext.next(QueryContext.java:398) at org.basex.query.expr.List$1.next(List.java:119) at org.basex.query.QueryContext.next(QueryContext.java:398) at org.basex.query.scope.MainModule$1.next(MainModule.java:122) at org.basex.query.QueryContext.next(QueryContext.java:398) at org.basex.query.QueryContext.cache(QueryContext.java:620) at org.basex.query.QueryProcessor.cache(QueryProcessor.java:112) at org.basex.core.cmd.AQuery.query(AQuery.java:86) at org.basex.core.cmd.XQuery.run(XQuery.java:22) at org.basex.core.Command.run(Command.java:257) at org.basex.core.Command.execute(Command.java:93) at org.basex.gui.GUI.exec(GUI.java:430) at org.basex.gui.GUI.lambda$4(GUI.java:373) at java.lang.Thread.run(Thread.java:748) -- Jan Dölle E-Mail: basex-list(a)id1.de Telefon +49-69-244502-0 Home: www.id1.de Information Design One AG, Baseler Straße 10, 60329 Frankfurt am Main Registereintrag: Amtsgericht Frankfurt am Main, HRB 52596 Vorstand: Robert Peters, Aufsichtsrat: Christian Hecht (Vorsitz)

2 1

Licensing issue
by Benoit Maisonny 19 Jan '18

19 Jan '18

Hello, I just realised that the basex-api Maven artifact depends on milton-api 1.8, which is released under GPLv3 (this is declared in its parent pom). That means that basex-api, and any software that is distributed with it, must be released under GPLv3 as well... Are BaseX developers aware of that? Note that the current milton library v2 is released under Apache license. Is there any intention to upgrade to milton v2 (is it even possible)? Thanks, Benoit

3 3

delete .jar without version using repo:delete()
by Wissemann, Bodo 19 Jan '18

19 Jan '18

2 2

Web Applications: permission handling
by Christian Grün 18 Jan '18

18 Jan '18

Hi everyone, With BaseX 9.0, permission handling in web applications will be further simplified. We have just finalized a new light-weight permission layer that allows you to: • attach permission strings to RESTXQ functions and • disallow evaluation of such functions via annotated security functions. More details can be found in the documentation [1]. Thanks to those who gave helpful feedback! A new snapshot is available [2]; the DBA has already been rewritten to take advantage of the new annotations. In future versions, we might provide built-in support for various authentication methods (LDAP, OAuth, etc.), and the permission layer could possibly be extended to the other BaseX APIs as well. Looking forward to your feedback, Christian [1] http://docs.basex.org/wiki/Permissions [2] http://files.basex.org/releases/latest/

1 0

proc:system and bash redirecting
by Kristian Kankainen 18 Jan '18

18 Jan '18

Hello! I need to redirect the content of a file into a program using stdin. In my shell I would do like this (silly example): wc < somefile Is this possible to do with proc:system? Giving "<" as an argument to the command doesn't work: proc:system("wc", ("<", "somefile")) outputs [BXPR0001] wc: <: No such file or directory Is there any way around this? The program I need to call can only read from stdin. Best regards, Kristian K

2 1

Can BaseX support absolute/relative paths in validation:xsd(doc) if no second argument provided?
by Aleksandr Shapovaov 17 Jan '18

17 Jan '18

Hello, I've just discovered BaseX and decided to make some experiments. One of them is, suppose I have several documents (data + schemas), something like this: sys/core.xsd <?xml version="1.0"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="urn:SYS-CORE" targetNamespace="urn:SYS-CORE"> <xs:attribute name="category" type="xs:normalizedString"/> </xs:schema> lib/album.xsd <?xml version="1.0"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:SYS-CORE ../sys/core.xsd" xmlns:sys="urn:SYS-CORE" xmlns="urn:LIB-ALBUM" targetNamespace="urn:LIB-ALBUM"> <xs:import namespace="urn:SYS-CORE"/> <xs:element name="album"> <xs:complexType> <xs:sequence> <xs:element ref="title" minOccurs="1" maxOccurs="1"/> </xs:sequence> <xs:attribute ref="sys:category" use="required"/> </xs:complexType> </xs:element> <xs:element name="title" type="xs:normalizedString"/> </xs:schema> usr/albums/album1.xml <?xml version="1.0"?> <album xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:LIB-ALBUM ../../lib/album.xsd" xmlns:sys="urn:SYS-CORE" sys:category="albums" xmlns="urn:LIB-ALBUM"> <title>Album #1</title> </album> I'm uploading these documents using a Python script (I'm using BaseXClient) preserving the file system hierarchy structure I defined above. If I open the documents in IntelliJ IDEA, I can be sure that the documents are valid (I mean, I don't see XSD validation errors), therefore I'm assuming they are valid by fact. However, if I'm trying to validate the XML documents on the BaseX side session.execute('XQUERY for $doc in collection("%s") where fn:ends-with(fn:base-uri($doc), ".xml") return validate:xsd($doc)' % database) I'm getting the following error [bxerr:BXVA0001] Validation failed: 1:186: schema_reference.4: Failed to read schema document '../../lib/album.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. I'm wondering, what am I doing wrong trying to validate documents directly in BaseX? Can BaseX resolve absolute/relative paths in this case? Thanks in advance! P.S. Apologies if I made something wrong (wrong subject, mailing list, non text/plain email, etc), this is my first time sending an email to a mailing list. P.P.S. This email may contain an ad footer since I use this free email service. If possible, please trim the ad away before it's sent/archived. Thanks! -- реклама ----------------------------------------------------------- http://FREEhost.UA - Купи хостинг или домен и получи сертификат Google AdWords номиналом 900 грн.в подарок! - http://goo.gl/EcgF4I

3 3

Historical reasons in the Database Module
by Kristian Kankainen 17 Jan '18

17 Jan '18

Hello I once again ran into giving the arguments in wrong order to the db:replace function. The docs state, that "For historical reasons, the order of the 2nd and 3rd argument is different to db:add and db:create". Since XQuery is typed, wouldn't it be possible to add to new "cosmetic" functions with the arguments in the "right" order like the following: db:replace($db as xs:string, $input as item(), $path as xs:string) as empty-sequence() db:replace($db as xs:string, $input as item(), $path as xs:string, $options as map(*)?) as empty-sequence() Since the arguments are typed with different types (xs:string vs item()) this over-loading would work without colliding with the historical and swapped ones. Am I wrong? Cheers, Kristian K

2 1

Error: Processing instruction has illegal name: xml
by Thomas Zehrer 16 Jan '18

16 Jan '18

Hi there, if i want start a new xml document or open a exist one (factbook.xml e.g.), every time i get this error: Error: Processing instruction has illegal name: 'xml' i have already searched your website first steps and crawled the internet. there was just one entry on stackoverflow, the solution there wont work. how can i go on with it? thanks a lot. Thomas

2 1

DFDL module
by Kristian Kankainen 15 Jan '18

15 Jan '18

Hello, I started writing a small wrapper module for using DFDL with XQuery in BaseX. For this I simply use system calls. This is not an elegant way of doing it, so I wonder, has anyone else had any experience with using DFDL or even integrated it in a more sustainable way? My project will evolve here: https://github.com/keeleleek/basex-daffodil I would like to add a sentence on how cool DFDL is, but I wont. Best regards, Kristian K

2 2

Encoding problem with proc:system
by Kristian Kankainen 15 Jan '18

15 Jan '18

Hello all, I am running a system command with proc:system. The command should return xml, but because of non-ascii letters, the returned string gets scrambled. (I am aware that proc:system receives a string, proc:execute returns an element.) Running the system command in a shell works fine, I get this (snippet) <element>aapõ</element> When running the command through proc:system, I get this instead <element>aap....lement> Where the õ (= C3 B5 in hex representation) has been replaced with F5 BC AF B0. I get the same result specifying the encoding option of proc:system with "utf-8" or just leaving blank. My shell uses utf-8. How could I find out what encoding I need to use in the proc:system function? Best regards, Kristian K

2 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk January 2018