https://github.com/qt4cg/qtspecs/issues/854
I’ll be offline pretty often until end of June, so @all please bear with me
if I won’t be that responsive.
Martin Honnen schrieb am Fr., 7. Juni 2024, 13:50:
>
> On 07/06/2024 13:45, Christian Grün wrote:
>
> > But it looks as if B
> But it looks as if BaseX 11 doesn't support ??
as a (deep) lookup operator so far. Is that right?
Correct. The exact syntax (including key specifiers, which will be similar
to XPath axis specifiers) is still subject to discussion, so we haven’t
included it yet in our official release.
but somehow trying to follow the
> link I always end up on the main page again.
>
>
> On 06/06/2024 13:09, Christian Grün wrote:
>
> Dear all,
>
> We’ve been hard at work finalizing version 11 of BaseX, our open source
> XML framework, database system, and XQuery processor.
Dear all,
We’ve been hard at work finalizing version 11 of BaseX, our open source XML
framework, database system, and XQuery processor.
First, we have revised our documentation, which is now generated with
RESTXQ:
https://docs.basex.org/
Next, you can now visit BXFiddle to launch XQuery and
…fixed.
On Wed, Jun 5, 2024 at 4:28 PM wrote:
> Mr. Grun,
>
> I tested the latest BaseX 11.0 beta build 9182be0.
>
> It emits the following result for the provided test case:
>
>
> valid
>url="file:/C:/Users/i300179/Downloads/Warning.xsd">FacetsContradict: For
> simpleType definition
…makes sense. A new snapshot is online, which only assigns the 'invalid'
status when errors or fatal errors are found.
On Wed, Jun 5, 2024 at 3:18 PM wrote:
> Mr. Grun,
>
> Thanks a lot for such a such quick turnaround.
>
> I tested the latest BaseX 11.0 beta build 88ebdb9.
>
> It emits the
Hi Yitzhak,
Though Oxygen XML IDE shows the following upon validation:
> For simpleType definition '#AnonType_ADDR_TYPE', the enumeration value ''
> contradicts with value of 'length' facet.
The warning is not shown as it occurs before the actual validation (i.e,
while the schema is compiled).
Hi Rob,
I think there are various way to achieve that. One way is to store both the
full document in the session as well as the path to the requested node:
let $xml :=
let $result := $xml//blu
let $path := path($result)
return (
session:set('xml', $xml),
session:set('xml', $path)
)
You can
o about accomplishing this? I'm afraid networking is not one of my
> strengths.
>
> Many thanks for your assistance.
>
> Best,
>
> Jack
>
> On Wed, 22 May 2024, 8:47 pm Christian Grün,
> wrote:
>
>> Hi Jack,
>>
>> It seems that the browser ignores di
Hi Marco,
> ("a", "b", "c")[trace(1 + random:integer(3))]
The filter expression is defined in such a way that the predicate is
evaluated anew for every item of the sequence. If you want
random:integer(3) to be evaluated only once, you can either bind it to a
variable…
let $r :=
Hi Marco,
Thanks for your suggestion. Some thoughts:
• Function items can depend on the currently evaluated code and its static
and dynamic context, but we could possibly design something similar as for
the Job Module, in which the query is passed on as a string or a URI
reference and evaluated
Hi Jack,
It seems that the browser ignores different ports when handling session
data (just a guess). Does it work if you change the session key of your
second DBA instance [1]?
Best,
Christian
[1]
appears), but wanted to bring it to your attention in
> case you weren't aware.
>
> Cheers,
>
> Jack
>
>
> On Fri, 10 May 2024, 7:37 pm Christian Grün,
> wrote:
>
>> Hi Hack,
>>
>> That’s been helpful, thanks. We’ve aligned our Damerau/Levenshtein
Hi Hack,
That’s been helpful, thanks. We’ve aligned our Damerau/Levenshtein
algorithms, the latest version should behave as expected [1, 2].
Best,
Christian
[1] https://files.basex.org/releases/latest/
[2]
https://github.com/BaseXdb/basex/commit/6889ac108c6b32d448d640d53ec098bbb8938f06
On
Thanks for the insight. We’ll need to ensure that the check runs with all
versions of Windows that we support, but if a similar problem is reported
back to us again, we’ll think about a multi-step version check.
Best,
Christian
On Thu, May 9, 2024 at 11:09 PM wrote:
> Mr. Grun,
>
> It seems
>
> Where and how BaseX installer got into old Java v1.6 and missed a
> legitimate
> Eclipse Temurin JRE with Hotspot 17.0.8.1+1?
>
Good question. We would need to better understand the NSIS installer code
[1]. The installer provided dedicated Java checks, but those did not work
with newer JDK
/
On Tue, May 7, 2024 at 10:40 PM Christian Grün
wrote:
> Thanks for reporting this, Yitzhak.
>
> It seems something is going wrong in the Java version check of the
> installer:
>
> *https://github.com/BaseXdb/basex-dist/blob/20c565a4b8b79c27d276a191b35cb224ce537ef3/win/Base
Thanks for reporting this, Yitzhak.
It seems something is going wrong in the Java version check of the
installer:
*https://github.com/BaseXdb/basex-dist/blob/20c565a4b8b79c27d276a191b35cb224ce537ef3/win/BaseX.nsi#L50
Hi Rob,
Thanks. The current documentation will soon be replaced by a new version
(generated with BaseX) [1].
Best,
Christian
[1] https://help.basex.org/main/Database_Functions#db:type
On Fri, May 3, 2024 at 11:16 AM Rob Stapper wrote:
> Hi Christian,
>
> I stumbled on this minor issue in
Thanks. Here’s one way to do it:
let $body := document {
<_ type="object">
ba03177
0.83175087
ba
1810-40
Heinrich von Kleist
Die heilige Cäcilie
https://kleist-digital.de/...
Die Aebtissinn, ...
Hi Günter,
2. I'm getting a full Object (but I dont know, if its the raw JSON-Object
> like above), but I am not able, to parse it, to get a list in html.
>
Could you share the result of your response with us (possibly shortened)?
It would be interesting to learn something about the type of the
tps://docs.basex.org/wiki/Options#DEFAULTDB
On Mon, Apr 22, 2024 at 9:32 AM Christian Grün
wrote:
> Hi Antonio,
>
> As Liam indicated, you may get better performance when adding your
> documents to a database.
>
> In general, though, the runtimes of BaseX and Saxon have aligned pretty
Hi Gerrit,
If you don’t need the canonical path to a file resource on the file system,
file:resolve-path may be the better choice. It can be used for both file
URIs and local (relative or absolute) paths.
Hope this helps,
Christian
On Mon, Apr 22, 2024 at 8:00 AM Imsieke, Gerrit, le-tex <
Hi Antonio,
As Liam indicated, you may get better performance when adding your
documents to a database.
In general, though, the runtimes of BaseX and Saxon have aligned pretty
much over the years, and I assume there’ll be a trivial reason behind the
drastic difference in the runtime.
Your test
…I agree with Andy: This looks like a Java issue. You could try enabling
IGNORECERT in your .basex configuration [1] and executing REPO INSTALL to
see if that changes anything.
[1] https://docs.basex.org/wiki/Options#IGNORECERT
On Wed, Apr 10, 2024 at 1:57 PM Andy Bunce wrote:
> Hi Régis,
>
Hi Leo,
I came across this question because I needed to know whether there are city
> elements twice in the file. For that I wrote version 2 and the result was
> wrong. Then I wrote version 1 with
> … satisfies . => deep-equal($city)
> that gave the correct answer. I noticed that I do not fully
Hi Leo,
Yes, they are equivalent. Version 2 is a bit faster because "." will only
need to be atomized once.
We’ll examine if BaseX can automatically rewrite version 1 to version 2.
Best,
Christian
On Mon, Apr 8, 2024 at 11:59 PM Leo Studer wrote:
> Hello
>
> are the following queries
Hi Vladimir,
There’s currently no such function available. Even if we had a user:kill
function, we could not ensure that a user logs in a millisecond later when
user:drop is going to be executed. We could enrich user:drop et al. with an
“enforce” option to kill users, but the challenge is that a
Hi Graydon,
Folks tell us it’s time to stop delaying BaseX 11… We’re trying hard.
The good news: The only difference between hof:until [1] and fn:do-until
[2] is the order of parameters. The following queries will do the same
thing:
hof:until(function($a) { $a > 16 }, function($a) { $a * 2 },
Hi Marco,
I’m sorry, I can’t give any explanation on why BaseX performs worse with
NFS. In principal, we rely on standard Java IO/NIO.
Does it make a noticeable difference if you store copy many small files a)
locally and b) to the NFS exported disk?
Ciao,
Christian
On Thu, Mar 14, 2024 at
e add more XML documents
> routinely as we digitize more books over time. Therefore updates and
> additions are commonplace, such that keeping indexes up to date is
> important, to allow full-text searches to stay performant. I’m wondering if
> there are techniques for optimizing such
Hi Greg,
A quick reply: If only parts of your documents are relevant for full-text
queries, you can restrict the selection with the FTINDEX option (see [1]
for more information).
How large is the total size of your input documents?
Best,
Christian
[1]
Hi Greg,
A helpful observation. With XQuery 4, parameters can directly be addressed
by their name, and optional arguments can be omitted:
validate:xsd($doc, options := $options)
The changes that were required to make this work led to a bug that is now
fixed in the latest snapshot [1].
est.
>
>
>
> Thanks,
>
> Greg
>
>
>
> *From: *BaseX-Talk on behalf
> of Christian Grün
> *Date: *Monday, March 11, 2024 at 3:12 AM
> *To: *Andy Bunce
> *Cc: *BaseX
> *Subject: *Re: [basex-talk] xslt:transform-report result
>
> Hi
fect. Please edit or revert if
> my understanding is incorrect.
>
> /Andy
> .
> [1] https://docs.basex.org/wiki/XSLT_Module#Examples
> [2] https://help.basex.org/main/XSLT_Module
>
>
> On Wed, 4 May 2022 at 22:16, Christian Grün
> wrote:
>
>> I agree it's somewh
ggest any simple ways
> around it? I'm afraid applying %basex:inline hasn't helped.
>
> Very best,
>
> Jack
>
> On Fri, 1 Mar 2024, 8:12 pm Christian Grün,
> wrote:
>
>> Hi Jack,
>>
>> > When you say you can't reproduce it, do you mean you get
Hi Tim,
Thanks for spending so much time on this, and the visual “proof”.
A mysterious one! The query seems to be correctly evaluated on my system,
whatever I do.
>- There’s no error that’s thrown, so I’m not certain about how to
>share a stack trace?
>
>
Good to know. If no stack
8
>
> servicenow.com <https://www.servicenow.com>
>
> LinkedIn <https://www.linkedin.com/company/servicenow> | Twitter
> <https://twitter.com/servicenow> | YouTube
> <https://www.youtube.com/user/servicenowinc> | Facebook
> <https://www.facebook.com/ser
…just a quick reply: That’s probably related to [1], an ancient issue, in
which I tended to recommend the usage of db:path. I wish we’d finally find
time and ressources to tackle this.
[1] https://github.com/BaseXdb/basex/issues/1172
On Mon, Mar 4, 2024 at 11:49 AM Eliot Kimber
wrote:
> Using
Hi Tim,
Thanks for your observation. We need more help to reproduce this: Could you
describe in detail, and step by step, how to trigger this issue?
In addition, you could…
• tell us more about your OS and JDK version
• start BaseX on command line and share a possible stack trace with us
•
> servicenow.com <https://www.servicenow.com>
>
> LinkedIn <https://www.linkedin.com/company/servicenow> | Twitter
> <https://twitter.com/servicenow> | YouTube
> <https://www.youtube.com/user/servicenowinc> | Facebook
> <https://www.facebook.com/servicenow&g
Hi Eliot,
We have aligned the behavior of the DBA editor to the BaseX GUI. Saved
files are only executable if they are detected as XQuery file.
But maybe we need to support some more file suffixes (.xq is the default
extension). How do you name your files?
Best,
Christian
Eliot Kimber
now> | YouTube
> <https://www.youtube.com/user/servicenowinc> | Facebook
> <https://www.facebook.com/servicenow>
>
>
>
> *From: *Christian Grün
> *Date: *Wednesday, February 28, 2024 at 9:36 AM
> *To: *Eliot Kimber
> *Cc: *basex-talk@mailman.uni-konstanz.de <
>
enow.com <https://www.servicenow.com>
>>
>> LinkedIn <https://www.linkedin.com/company/servicenow> | Twitter
>> <https://twitter.com/servicenow> | YouTube
>> <https://www.youtube.com/user/servicenowinc> | Facebook
>> <https://www.facebook.com/se
/files.basex.org/xml/factbook.xml
>
>
>
>
> When you say you can't reproduce it, do you mean you get 14 results from
> running this script?
>
> Cheers,
>
> Jack
>
> On Thu, 29 Feb 2024, 1:02 am Christian Grün,
> wrote:
>
>> Hi Jack,
>>
>> Than
…this one could be related to a bug that was recently fixed in the latest
snapshot [1]. About time to get BaseX 11 finished…
[1]
https://github.com/BaseXdb/basex/commit/45d97f8065615fb734b712bc4c77c39899e9d496
On Mon, Feb 26, 2024 at 5:25 PM Eliot Kimber
wrote:
> Using Basex 10.7 on Linux.
>
Hi Eliot,
It’s difficult to tell which requests are sent to BaseX. Maybe you can use
a networking monitoring tool such as Wireshark to get more hints?
Best,
Christian
On Sun, Feb 25, 2024 at 11:59 PM Eliot Kimber
wrote:
> I have an application (our Mirabel system) running on a server inside
Hi Jack,
Thanks for your observation.
> The first result of this query is the entry for Austria. I would expect
> both of the instances of the word 'German' in that entry to be surrounded
> by tags. However only the first instance is.
>
I couldn’t reproduce this yet. Here’s a command script
Hi Max,
Thanks for your report.
The behavior is correct, but I agree it’s surprising:
• //* returns two results: and
• the atomized value of is '14588204311438466813'. This value
exceeds the BaseX limit for integers (2^64), which is why [not(. castable
as xs:integer)] returns true for this
Hi Owen,
Do you have specific problems with whitespace in your query service? If
yes, which version of BaseX are you using?
Best,
Christian
On Wed, Feb 14, 2024 at 6:22 PM Owen Ambur wrote:
> Lack of capability to deal appropriately with whitespaces (and
> punctuation) results in false
Hi Vincenzo,
Thanks for your observation and the easily reproducible test case; we’ve
uploaded a new stable snapshot with a bug fix.
Please note that it’s generally risky to explicitly return empty sequences,
as the optimizer will always try to get rid of code that may not contribute
to the
Dear Greg,
In BaseX, it’s the text nodes that are indexed. Here are some query that
take advantage of the full-text index:
db:get("theocom")[.//text() contains text 'apple']
db:get("theocom")//page[text() contains text 'apple']
db:get("theocom")//text()[. contains text 'apple']
...
If you check
:
> On Tue, 2024-02-13 at 20:29 +0100, Christian Grün wrote:
>
>
> If your XML input has been properly indented to improve readibility, you
> can reduce the size of your database by dropping superfluous whitespace
> during the import:
>
> SET STRIPWS ON; CREATE DB ...
Hi Dietmar,
> Or is there a way to speed this up?
The fastest solution is to import all documents during database creation,
either with the CREATE DB command or the corresponding XQuery function:
CREATE DB name-of-db /path/to/documents
db:create('db', '/path/to/documents')
The database command
Hi Deepak,
For deletions, you can write:
let $db := 'db'
for $path in db:list($db, '2023')[matches(., '/\d\d')]
return db:delete($db, $path)
When accessing documents, it’s faster to iterate over the resources:
for $doc in db:get('db', '2023')
where matches(db:path($doc), '/\d\d')
return ...
resentation of XML fragments', I upgraded to
> 10.7 and the problem appears to be resolved (and wow, there is a big
> difference in performance – kudos!).
>
> Many thanks,
>
> Jack
>
> On Wed, 7 Feb 2024, 6:09 pm Christian Grün,
> wrote:
>
>> Hi Jack,
>>
Hi Jack,
If you run the query via basexhttp, how do you retrieve the results, i.e.,
which client do you use?
Can you possibly provide us with a self-contained example, something like…
for $i in 1 to 50
return update {
insert node into .
}
…and some steps to reproduce the behavior?
>
> I avoided "OPTIMIZE" since it caused OOM issues and I was fine without the
> index which looks like a double edged sword : ).
>
If you don’t need the indexes, you can disable them when running
db:optimize, and setting textindex and attrindex to false.
QQ, Is there some stat on how much RAM
Salut Pierre-Yves,
Sorry for not giving a helpful answer so far. Indeed it’s the sophisticated
setup that makes it difficult to give quick advice. Can you successfully
stop your server when you run a single basexhttp instance, or does this
already fail? Is it reproducible with 2 instances?
In
Hi Deepak,
Some more time would have to be spent to explain this in full detail.
In a nutshell, deleted space is not immediately reduced to a minimum size
because inserts are more regular. If you want to minimize your database
structure after extensive updates, you can call OPTIMIZE (ALL).
Hope
cause I was using v9 at the time.
>
> I now think the "Q" is required in BaseX v9, but optional in all V10+.
> Is this correct?
>
> /Andy
>
> [1]
> https://docs.basex.org/index.php?title=Command-Line_Options=146=16921=16694
>
>
>
>
> On Sat, 3 Feb 2024
Hi Andy,
Thanks for the raised finger. Indeed it’s the specification of XQuery 4
that takes much more time than anticipated. The process is highly dynamic,
with confirmed features being revised again. Some weeks ago, we have
stopped updating the old documentation, and we are working on a new one
Salut Pierre-Yves,
The home directory can be specified via the Java system property
“org.basex.path”. As it’s required before BaseX is even started, it must be
passed on to the JDK, e.g. via “-Dorg.basex.path=/path/to/my/basex”. This
string can be…
• statically added to the BASEX_JVM property in
/
On Wed, Jan 24, 2024 at 4:14 PM Christian Grün
wrote:
> Hi Eliot,
>
> Thanks for your observations, and some first debugging.
>
> The idmap file is only created and required if UPDINDEX is enabled. Well,
> let’s say it should: Maybe this file is not created in due time.
>
Hi Eliot,
Thanks for your observations, and some first debugging.
The idmap file is only created and required if UPDINDEX is enabled. Well,
let’s say it should: Maybe this file is not created in due time.
I haven’t managed to reproduce the bug yet. If you are more successful,
please let us
Hi Dharmendra,
I invite you to share a little self-contained example with us.
Can you reproduce it with the latest version of BaseX?
Thanks in advance,
Christian
DK Singh schrieb am Mo., 22. Jan. 2024, 12:44:
> Hi,
> I am using BaseX 9.5 and we are using the prof:dump() function for
>
gt; command itself is OK, so I have to check the content. Up to now I check the
> resulting string if it contains either "Warning: Database is inconsistent."
> or "RuntimeException". I hope, these are the only possible failure
> responses. Or are there any other?
>
Hi Omar,
we’ve re-added the stack trace to the latest 11.0 snapshot [1], and will
document this properly soon. I’ve slightly changed the behavior: Instead of
a single descriptive string, the stack trace is now returned as a string
sequence (the first entry points to the position in the code that
Dear Jürgen,
It turned out that the invocation of the INSPECT command raised an
exception that was not caught by the command itself, but was only sent to
stderr. We’ve revised this with the latest snapshot [1].
Best (and good luck for your power connection in 2024)
Christian
[1]
Hi Dharmendra,
We can only give limited free support for older versions of BaseX. Please
check if the behavior can be reproduced with the latest release.
Thanks in advance
Christian
DK Singh schrieb am Fr., 12. Jan. 2024, 17:11:
> Hi i am executing the simple
> command
Dear Jürgen,
Thanks for the observation.
In fact, the existing consistency checks won’t allow you to completely rule
out inconsistencies in databases. If your data is not strictly
confidential, we invite you to share the corrupt database instance with us,
it may help us to improve our checks. In
ces were removed in this commit from
> basex-core/src/main/java/org/basex/query/expr/Catch.java
>
> Revision: fc2376f6c9c250babfac7a7161b8a61740878b2b
> Author: Christian Grün
> Date: 17.05.2023 11:25:01
> Message:
> [XQ4] try/catch, $err:map
>
>
> Modified: basex
st did that, it still crashes ...
>>
>> Jonathan
>>
>> On Wed, Jan 10, 2024 at 1:22 PM Jonathan Robie
>> wrote:
>>
>>> Thanks for the prompt, helpful response!
>>>
>>> Jonathan
>>>
>>> On Wed, Jan 10, 2024 at 5:54 AM Chri
:new, "xsd-init()",
>
> Regards,
> Yitzhak Khabinsky
>
> -Original Message-
> From: ykhab...@bellsouth.net
> Sent: Wednesday, January 10, 2024 10:16 AM
> To: 'Christian Grün'
> Cc: 'BaseX'
> Subject: RE: [basex-talk] How to invalidate XSD ca
Hi Martin,
BaseX 8.6.7 is pretty old now. Could you please if the behavior can be
reproduced with the latest version of BaseX?
Thanks in advance,
Christian
On Wed, Jan 10, 2024 at 6:09 PM Martin Dowling <
martin.dowl...@bloomsbury.com> wrote:
> Hi
>
>
>
> I’m trying to run a query in BaseX
Hi Yitzhak,
Thanks for the suggestion. Feel free to check out the latest stable
snapshot, it contains two new functions for discarding cached XSD schemas
and XSL transformers [1,2].
Best,
Christian
[1] https://github.com/BaseXdb/basex/issues/2267
[2] https://files.basex.org/releases/latest/
Hi Jonathan,
This problem is related to Homebrew and Apple [1], and does not seem to be
solved yet.
There are alternatives, though. One solution that has been suggested by my
colleague Michael is to:
1. Uninstall the homebrew openjdk:
brew uninstall openjdk --ignore-dependencies
2. Manual
Hi Matt,
Your assumption is correct: Database backups are nothing else than zipped
archives of the corresponding database subdirectory located in the 'data'
directory.
If you create backups on your own, you should ensure that no updates are
currently running during your update operation. If you
Hi France,
I’m sorry to hear that.
Times are busy, especially with the end of the year approaching. As the
number of our clients has increased, and as we want to do justice to
everyone, our consulting is now based on SLAs that give you guaranteed
response times. Are you interested in a quote?
Hi Johan,
we've disabled the highlighting in the Wiki. We're working on a new
documentation based on RESTXQ, which will hopefully deliver a better user
experience.
Best,
Christian
Christian Grün schrieb am Do., 30. Nov. 2023,
13:35:
> Thanks, Johan, for the reminder. We’re work
>
> Hi Eliot,
> let $doWrite := file:write('/Users/eliot.kimber/temp/apps-to-topics.csv',
> $report)
>
file:write-text should do the job. An alternative is to use the
serialization method 'text':
file:write($path, $value, map { 'method': 'text })
Hope this helps,
Christian
Thanks, Johan, for the reminder. We’re working on it and will hopefully be
able to fix it soon. All the best, Christian
Johan Mörén schrieb am Do., 30. Nov. 2023, 12:37:
> Hi,
>
> Just discovered that the code samples on the basex wiki doesn't seem to be
> working fully. Noticed it a couple
>
> Hi Rob,
> Just a thought: shouldn’t util:if not just be part of the regular BaseX
> syntax? Together with fn:for-each, the fn:fold functions and
> hof:fold-left1, they represent the group of procesflow-controll-functions.
>
>From a syntactical view, util:if is just a function (which simulates
Hi Andy, hi Rob,
util:if is back again.
Just give me a note if there are other functions in the Utility Module (or
in the HOF Module) that you rely on.
Best,
Christian
On Mon, Nov 20, 2023 at 1:15 PM Andy Bunce wrote:
> Hi,
> The documentation for the utility module [1] says certain
Thanks, Tim,
That was helpful: You came across a hidden bug that was introduced three
years ago (and which was probably triggered by some newer optimizations).
The bug has been fixed [1,2].
Best,
Christian
[1] https://github.com/BaseXdb/basex/issues/2261
[2]
…thanks, Rob, thanks Andy, for the inquiry. I think we can re-add the
function, it shouldn’t cause problems.
I learned over time that the best (and sometimes only) way to find out
which features are used is to simply remove them…
On Wed, Nov 22, 2023 at 1:07 PM Rob Stapper wrote:
> Christian,
gt;])'||my:escapeText(head($search)), head($replace),'j')
>
> };
>
>
>
> perhaps there is a better way to do this... how would one do this sort of
> replacement on mixed content without having to parse this back to XML?
>
> But this works for me when being careful to add so
gt; clearly eating the text (“DUMMY”) which might be an edge case, but is
> obviously a problem when you think the function will give you an error in
> case of non-wellformedness – some text has silently been deleted.
>
>
>
> Daniel
>
>
>
> *Von:* Christian Grün
Hi Daniel,
Yes, I assume we’ll need to call it a bug… Although what BaseX is currently
doing is known to us to be out of spec behavior. The function
fn:parse-xml-fragments is based on our internal XML parser, which is much
faster than the standard XML parser (in particular for small input), and
Hi Tim,
Thanks for the pointer. It seems that the reported bug has been fixed just
recently (at least I couldn’t reproduce it anymore). Could you try the
latest snapshot? [1]
Thanks in advance,
Christian
[1] https://files.basex.org/releases/latest/
On Mon, Nov 20, 2023 at 9:00 PM Thompson,
…thanks for the pointer. I’ve revised the documentation.
One property of util:if was that you could omit the argument for the else
branch. We decided to drop util:if, because the specification now provides
a new syntax for if expressions where the else branch is optional:
if ($test) { $then }
Hi Andy,
Thanks for the observation. I’ve fixed the problem (backed by an additional
JUnit test), and a new snapshot is online [1].
Best,
Christian
[1] https://files.basex.org/releases/latest/
On Mon, Nov 20, 2023 at 12:36 PM Andy Bunce wrote:
> Hi,
>
> Back in the winter of 2017, BaseX 8.6
Hi Andre,
It’s probably out of scope to give a reasonable response to your questions
via the public mailing list (feel free to ask for our commercial services),
but here’s a quick shot:
>
>- why is the whole database read even for a "small" query ? (looks
>like a missing index or bad
BaseX use
the same JRE? You can e.g. check this with the following query:
for $p in proc:property-names()[starts-with(., 'java.vm.')]
return $p || ': ' || proc:property($p)
> 16.11.2023, 15:00, "Christian Grün" :
>
> Hi, this definitely looks like a bug in the JDK context. W
Hi, this definitely looks like a bug in the JDK context. What happens if
you upgrade your JDK to a newer version?
Best, Christian
On Thu, Nov 16, 2023 at 12:56 PM Ветошкин Владимир
wrote:
>
> Hi everyone.
>
> Since I have changed jdk version to 12 (azul) - I get error, when I copy
> database
…difficult to tell what might be the reason; we didn’t get similar reports
so far. Most of the BaseX caching algorithms rely on the file system, but
we don’t differ between Windows- and UNIX-based systems.
Does it make a difference if you change another JDK distribution?
Best,
Christian
On
Hi Csaba,
If you want to perform parallel/concurrent read and write operations on
your databases, you must exclusively use the client/server architecture.
See [1] for more details.
Best,
Christian
[1] https://docs.basex.org/wiki/Startup#Concurrent_Operations
Csaba Fekete schrieb am So., 12.
Hi Csaba,
The variable types of the REST API are limited to atomic values. With BaseX
11, however, it will be possible to bind multiple values [1]:
http://localhost:8080/rest?run=query=3=4=5
(: XQuery file: query.xq :)
declare variable $n as xs:integer* external;
array { $n }
You can try the
ta/element
> where $x/child3/child4/id = '123'
> return $x
>
> Let me know if this is helpful -- if not, I could share more info in a
> direct email about the actual structure of the database and the Info output.
>
> Thanks,
> Matt
>
> On Mon, Oct 30, 2023 at 4:40 PM Chr
Hi Matt,
In general, all nodes are treated identically, no matter what the hierarchy
is or regular the target path is.
Could you share some more information with us? How do the queries look like
(the slow and the fast one)? Is the text index applied in both cases?
Thanks in advance,
Christian
1 - 100 of 4288 matches
Mail list logo