The enclosed patch -- would you prefer a github pull request? -- makes
xslt:transform() aware of XML catalog files, as other XML parsing
already is. The same CATFILE preference is used (via the query
context).
I refactored CatalogWrapper slightly so it could be reused. I also took
away the line
Am 26.02.2019 um 18:52 schrieb Mark Bordelon:
A follow-up: starting basex -w does NOT seem to solve completely my
issue after all. Real data (more complicated than the simplified
example) still does not query correctly: text nodes from after later
elements are displayed in the place of null
A follow-up: starting basex -w does NOT seem to solve completely my issue
after all. Real data (more complicated than the simplified example) still does
not query correctly: text nodes from after later elements are displayed in the
place of null text nodes.
I’ll try to get a better example,
My follow-up was too hasty, and I forgot to mention that I had tried starting
up basex with -w, but it break so many other things that I cannot use this
GLOBAL approach.
I need to instruct either at the XQUERY command level or at the xml file level.
By the way, Kirstian, THANK YOU does work in
Hi,
I tried both ways of enabling gzip compression for JSON and js (and
others). I can't see it actually working. The GzipFilter method from the
web.xml sample seems to be deprecated with a warning of "it is bug
ridden" ... But then in a browser debugger I cannot see it actually
zipping
Thanks Martin and Michael for the “sofortige Antoworten”.
Forgive my lack of understanding about the particular of whitespace processing
and how BASEX deals with them.
To answer Martin’s questions:
1) I stored that xml (as I do all of my email) in the database using this
commands in the basex
Hi,
Looks likt I got BaseX 9.1.2 to work.
I configured the AUTHMETHOD in .basex to Digest
In the %perm:check funktion I return 401 if I want authentication. As
noted in commit
https://github.com/BaseXdb/basex/commit/acd4713e99f618c8dc9dda8d5f994d0139c2bf42
for 9.2 there is no way to send a
Hi Mark,
Hi Martin,
yes Martin is right, the whitespace will be chopped by default leading to the
observed behavior.
If you wanted to preserve whitespace globally, you can do that when creating
your database.
If you only want to preserve whitespace for a given element you may do this as
Hi Jacob,
well — the geo distance computes the distance of the direct line between the
two coordinates:
>52.519881,13.407338
and
>51.507351,-0.12766
Which happens to be 13.57281797796 <=>
https://en.wikipedia.org/wiki/Euclidean_distance
Yet, the earth is spherical, so you
Hi! For example, it's need to get the distance between Berlin and
London, which is 934 km.
So I've put the coordinates as they can be found in Google Maps, etc.:
let $berlin :=
52.519881,13.407338
let $london :=
51.507351,-0.12766
return geo:distance($berlin, $london)
Hi Jacob,
I’ve never really used the geo:module but according to the documentation:
> in the units of the spatial reference system of geometry1
If I understand it correctly, you would have to convert your coordinates to map
them to miles or kilometers for example.
Maybe you can provide an
11 matches
Mail list logo