On Wed, 2019-03-13 at 20:15 +0100, Imsieke, Gerrit, le-tex wrote:
>
> On 13.03.2019 19:55, Liam R. E. Quin wrote:
> > Yes, they are a bit of a nightmare. Actually i’ve thought about
> > having
> > the ability to write a URI Resolver in XQuery,
> > db:resolve-identifier($system, $public,
On 13.03.2019 19:55, Liam R. E. Quin wrote:
Yes, they are a bit of a nightmare. Actually i’ve thought about having
the ability to write a URI Resolver in XQuery,
db:resolve-identifier($system, $public, $purpose, $types) as
xs:anyURI?
but maybe it is too scary!
I’ve already written a
On Wed, 2019-03-13 at 11:57 +0100, Christian Grün wrote:
> > Note that i have a public identifier, so using prefer-public lets
> > that
> > be resolved.
>
> xmllint and BaseX seem to behave differently on my system. With
> xmllint and xsltproc, your examples run fine.
That's good at least...
>
> Note that i have a public identifier, so using prefer-public lets that
> be resolved.
xmllint and BaseX seem to behave differently on my system. With
xmllint and xsltproc, your examples run fine.
When running the following query…
fetch:xml('all.xml', map { 'dtd': true(), 'catfile':
Hi Andreas,
Yes, that’s true, it got lost in 9.1.2 [1]. Sorry for that.
BaseX 9.2 will be available soon. For now, feel free to use 9.1.1 or
the latest snapshot [2].
Best,
Christian
[1] https://github.com/BaseXdb/basex/issues/1669
[2] http://files.basex.org/releases/latest/
On Wed, Mar 13,
Hi
The "j" flag for regular expressions introduced in version 9.1 doesn't seem
to work in 9.1.2 anymore. For example, matches("Fenster", "\bfenst", "ij")
produces [FORX0001] invalid regular flag 'j'. The same expression works in
9.1.1.
Best Greetings,
Andreas
6 matches
Mail list logo
