Hi Alex (cc to the list), This might be an OS-specific problem (I tried to reproduce the problem with Windows and Ubuntu, but I didn’t succeed). Which operating system are you using, and what’s the default encoding of your file system?
> '../xqm/path:frequently used paths.xqm'; This is actually an invalid path in XQuery, as spaces should be encoded via %20. BaseX accepts it anyway, at least in version 9 (we might change that in future). Maybe you’ll generally encounter less issues if you use standard URI characters in your file paths. But as soon as I’ll manage to reproduce the encoding problem you encountered, I’ll be happy to have a closer look at it. Feel free to provide me with a minimal step-by-step procedure; maybe I missed something. Saludos, Christian On Fri, Dec 21, 2018 at 5:28 AM Alex R. Loayza <arx.in...@gmail.com> wrote: > Hello Christian, > > I have encountered an issue in BaseX 9.1.1 after migrating from 8.5.3. It > seems to be a character encoding problem. > > In many queries, I import a module with a relative path: > > import module namespace path = 'http://myns' at '../xqm/path:frequently > used paths.xqm'; > > While this worked fine in 8.5.3, in 9.1.1 I get the following error > message: > > If I substitute the absolute path to the module for the relative path, > > import module namespace path = 'http://myns' at > '/home/arx/devWorks/otherProjects/almacén/procRep/xqy/xqm/path:frequently > used paths.xqm'; > > ...the import again succeeds. This tells me that the code resolving the > relative path in 9.1.1 is having problems with non-ascii characters: the > *é* in this case, which is changed to *?* in the resolved path. > > I see no way to fix this myself. Is this is a bug, or is there some > workaround? > > Cheers, > > Alex > > > --------------------------- > From: Christian Grün <christian.gr...@gmail.com> > <christian.gr...@gmail.com> > To:Alex R. Loayza > Cc:BaseX > Dec 20 at 3:36 AM > Hi Alex, > > All changes in the 9.0 storage layout are backward compatible. If you > update your database, it will be optimized incrementally. > > Breaking changes in BaseX will be documented explicitly. For example, if > you have written a lot of XQuery code, you may need to update some > BaseX-specific function calls. You will find those changes in the docs by > searching for "9.0" or "9.1". > > Hope this helps, > Christian >
