[basex-talk] is this a bug?

Hi, I stumbled upon this behavior. Is this a bug? I’m still using Basex version 9.7. Code[1]: let $e := abc update { replace value of node . with ./data() || "def" } return ( $e, $e/data() ) Result: abcdef abc Expecting: abcdef abcdef [1] attachment: “replace-value-of-bug.xq” Pleased

[basex-talk] BaseX 9.5.1: Minor Bug Fixes, XQuery Tweaks

Dear all, BaseX 9.5.1 is out. Some minor bugs have been fixed (nothing critical), and some more queries are rewritten to a faster representation. For example, consecutive for and let clauses will be merged now, and… for $e in 1 to 10 let $n := $e + 1 order by $n descending return string($n)

Re: [basex-talk] BaseX python replace bug

Thanks for your patience, Daniel, The issue has been resolved. A new snapshot is available [1]. Have fun, Christian [1] https://files.basex.org/releases/latest/ On Tue, Jan 12, 2021 at 10:38 PM Daniel Kaplan wrote: > > > Hello, > > I'm experiencing some issue(s) when using BaseX... wanted

Re: [basex-talk] BaseX python replace bug

Awesome, thanks! On Wed, Jan 13, 2021, 4:09 AM Christian Grün wrote: > Hi Daniel, > > Thanks for writing to the list. Based on your input files, I managed > to reproduce the bug via a BaseX command script. It seems to occur if > ADDCACHE is enabled, and if a document is replaced in an empty >

Re: [basex-talk] BaseX python replace bug

Hi Daniel, Thanks for writing to the list. Based on your input files, I managed to reproduce the bug via a BaseX command script. It seems to occur if ADDCACHE is enabled, and if a document is replaced in an empty database. I’ve created a new GitHub issues [1], we’ll fix this soon. Until then,

Re: [basex-talk] BaseX python replace bug

Ah, my bad. That's all relevant questions. I do get an error, an OS "Bad File Descriptor" error. Tracing it up, there's a java "Array out of bounds" error. Notably, the same files can be inserted into a clean database using "ADD", but not "REPLACE". I didn't check if the files get added to an

Re: [basex-talk] BaseX python replace bug

On Tue, 2021-01-12 at 16:38 -0500, Daniel Kaplan wrote: > Hello, > > I'm experiencing some issue(s) when using BaseX... wanted to report > it > here, but not sure what information you need. Imagine for a moment that it does not happen for anyone else... What exactly goes wrong, in detail? Is

Re: [basex-talk] Improper use/potential bug error

Sorry all for the surprises concerning the latest patch release. The full distributions included old library files. Both the library and the permission issues have been fixed. Have fun, stay healthy, Christian On Fri, Jan 8, 2021 at 12:55 AM Eliúd Santiago Meza y Rivera wrote: > > Hi, > > I

[basex-talk] Improper use/potential bug error

Hi, I just update to the latest version of BaseX 9.4.6, and the web server now do not refer correctly the link, checking every individually broken link, the server response this message: I attach the code. In advance I appreciate your help. HTTP ERROR 500 java.lang.NoSuchMethodError:

Re: [basex-talk] Improper use/potential bug error

Hi Giuseppe, The compilation info of all xquery:eval calls was added to the query info; this resulted in a huge list of info messages. With the new snapshot, only the compilation strings for the main expression will be added to the info output [1]. As indicated, the error can be avoided in 9.4.5

Re: [basex-talk] Improper use/potential bug error

One more hint: If you iterate over documents that are not stored in a database, you can save a lot of main memory by using fetch:xml instead of fn:doc. As fn:doc is deterministic, all intermediate documents must be kept in main memory in order to ensure that a future access to this file will

Re: [basex-talk] Improper use/potential bug error

Hi GIuseppe, The error message indicates that the info that’s to be output in the Info View panel gets too large. Does the error also occur if you disable the Info View before running the query? We’ll try to find the weak spot (usually, too large info output will be chopped), Christian On Sat,

[basex-talk] Improper use/potential bug error

Hi, I got an "Improper use? Potential bug?” error (see below) with a (complex) query which actually works when applied to many files (but not to all). This is the query (temporary links): https://git.informatik.uni-leipzig.de/celano/latinnlp/-/blob/master/scripts/03.00_normalize_spelling.xq

Re: [basex-talk] Improper Use? Potential bug?

esge > > buddy.kre...@known2u.com > > o: 860-800-6677 ext: 501 > > c: 860-986-4830 > > > > *From:* BaseX-Talk *On > Behalf Of *Buddy Kresge > *Sent:* Tuesday, June 4, 2019 8:55 AM > *To:* Christian Grün > *Cc:* BaseX > *Subject:* Re: [basex-talk] Improper U

Re: [basex-talk] Improper Use? Potential bug?

*Cc:* basex-talk@mailman.uni-konstanz.de > *Subject:* Re: [basex-talk] Improper Use? Potential bug? > > > > Hi Buddy, > > > > that looks like a bug. > > > > Would you mind sharing your XQuery or a SSCE? > > I think this is definitely something we migh

Re: [basex-talk] Improper Use? Potential bug?

Buddy Kresge Cc: basex-talk@mailman.uni-konstanz.de Subject: Re: [basex-talk] Improper Use? Potential bug? Hi Buddy, that looks like a bug. Would you mind sharing your XQuery or a SSCE? I think this is definitely something we might want to have a look at :-) Best from Konstanz Michael Am 03.0

Re: [basex-talk] Improper Use? Potential bug?

Hi Buddy, that looks like a bug. Would you mind sharing your XQuery or a SSCE? I think this is definitely something we might want to have a look at :-) Best from Konstanz Michael > Am 03.06.2019 um 13:12 schrieb Buddy Kresge : > > I am all of a sudden getting the below error (and things

[basex-talk] Improper Use? Potential bug?

I am all of a sudden getting the below error (and things were working just fine - weird). Works fine in 9.1.2 but not in 9.2.X. Any guidance would be greatly appreciated. Note: I tried to send you an email with the full stack trace, but the moderator rejected it because the email was too

Re: [basex-talk] possible basex 9.1.1 bug in java binding exception handling

The character in the example query between "new" and "java" was meant to be the "middle dot character" (), not an asterisk: Trying again... and hoping it gets through the various mailers :) Q{java.lang.String}new·java.lang.String(())

Re: [basex-talk] Improper use? Potential bug?

Aan: Rob Stapper CC: BaseX Onderwerp: Re: [basex-talk] Improper use? Potential bug? Hi Rob, Your queries are not equivalent. The hof:id function simply returns its argument (see [1]). In your example, it returns a function with two arguments ($v1,$2v), which is then passed on to local:exists

Re: [basex-talk] Improper use? Potential bug?

b) I would expect both versions behave the same. Thus: ( 1,2) as result > > -Oorspronkelijk bericht- > Van: Christian Grün [mailto:christian.gr...@gmail.com] > Verzonden: zondag 5 februari 2017 14:57 > Aan: Rob Stapper > CC: BaseX > Onderwerp: Re: [basex-talk] Improper u

Re: [basex-talk] Improper use? Potential bug?

> Van: Christian Grün [mailto:christian.gr...@gmail.com] > Verzonden: zaterdag 4 februari 2017 11:14 > Aan: Rob Stapper > CC: BaseX > Onderwerp: Re: [basex-talk] Improper use? Potential bug? > >> My program is heavily recursive so it is hard to create a running >> sni

[basex-talk] Improper use? Potential bug?

Hi Christian, I encountered this error-message. I have a strong feeling that this error is related to previous reports, see . my email dd 13-05-2013 and 03-12-2014 My program is heavily recursive so it is hard to create a running snippet but I will try. Hopefully in the mean

Re: [basex-talk] JSON serializer - slight bug

Oh thank you - now I understand.Of course, you needed a rule to represent zero-length string names, and "_" was the almost obvious choice! Sorry for the disturbance -Hans-Jürgen Christian Grün schrieb am 14:27 Mittwoch, 30.September 2015: Hi

[basex-talk] JSON serializer - slight bug

Dear BaseX, I think there is a very slight bug in the JSON serializer: when an element with type="object" has a <_> child, I think the serializer should report an error (as underscores must be doubled, if not using the name "_", reserved for array items. Instead, the serializer creates a

Re: [basex-talk] JSON serializer - slight bug

Hi Hans-Jürgen, You may be surprised, but the behavior is correct. It's defined in the conversion rules in our documentation [1]: " Empty names are represented by a single underscore (_).". The following example illustrates the behavior: json:parse('{ "":"" }') Hope this helps, Christian [1]

Re: [basex-talk] BaseX GUI minor bug with Preferences dialog in v8.0.3

Sounds good. Thank you. Regards, Amanda -Original Message- From: Christian Grün [mailto:christian.gr...@gmail.com] Sent: Tuesday, March 24, 2015 5:19 AM To: Amanda Galtman Cc: basex-talk@mailman.uni-konstanz.de Subject: Re: [basex-talk] BaseX GUI minor bug with Preferences dialog

Re: [basex-talk] BaseX GUI minor bug with Preferences dialog in v8.0.3

Hi Amanda, Ture, the behavior is confusing: As changes in the preferences dialog are applied with each key click in more recent versions of BaseX, an existing database will be closed before the changed database path will be assigned. Next, if databases are closed, all open dialog windows are

[basex-talk] BaseX GUI minor bug with Preferences dialog in v8.0.3

Hi, Here are reproduction steps for a bug I'm seeing in v8.0.3 on win64. The issue was present in v7.9, but not in 7.7.2. Those are the versions I happen to have installed; I don't know the exact version that introduced the issue. 1. Select Database Open Manage, select a database, and open

Re: [basex-talk] Update Facility / Files - bug?

Hi Hans-Jürgen, An old issue on the responsible WRITEBACK option has been chasing us for quite a while now [1]. I have updated the code base and the snapshots [2]; your example should work again! Thanks, Christian [1] https://github.com/BaseXdb/basex/issues/848 [2]

Re: [basex-talk] Update Facility / Files - bug?

Excellent, thank you very much! Cheers,Hans-Jürgen Christian Grün christian.gr...@gmail.com schrieb am 17:56 Mittwoch, 4.Februar 2015: Hi Hans-Jürgen, An old issue on the responsible WRITEBACK option has been chasing us for quite a while now [1]. I have updated the code base and

[basex-talk] Update Facility / Files - bug?

Dear BaseX-team, is there a problem concerning the update facility? Or do I have a blackout? Suddenly it seems as if the facility did not any more change files. doc.xml: a   bXXX/b /a replaceValue.xq:replace value of node //b with 'YYY' call:basex -u  -i doc.xml replaceValue.xq = no change

[basex-talk] is this a bug?

Hi, I can't figure out why the attached xquery-program triggers an error. Am I doing naughty things or is it a bug? Regards, Rob --- Dit e-mailbericht bevat geen virussen en malware omdat avast! Antivirus-bescherming actief is. http://www.avast.com nested_returnfunctions.xq

Re: [basex-talk] is this a bug?

Hi Rob, I'm pretty sure the raised error is correct. But I have a hard time to understand what you are trying to do? ;) Christian On Thu, May 8, 2014 at 1:01 PM, Rob Stapper r.stap...@lijbrandt.nl wrote: Hi, I can't figure out why the attached xquery-program triggers an error. Am I

Re: [basex-talk] Is this a bug?

Hi Rob, Am 01.03.2014 17:53, schrieb Rob Stapper: The enclosed example triggers stackoverflow-errror. I was wandering if it is a bug. yes, this definitely is a bug in the compiler. The function item `$go` is inlined even though it is (kind of) recursive, which leads to an infinite loop. I

Re: [basex-talk] Is this a bug?

Hi again Rob, Am 02.03.2014 13:34, schrieb Leo Wörteler: I raised an issue on GitHub [1] and will submit the fix as soon as possible. Thank you for reporting it! Christian merged my pull request [2] and uploaded a new snapshot [3], could you try that and see if the problem is fixed?

[basex-talk] Is this a bug?

Hi, The enclosed example triggers stackoverflow-errror. I was wandering if it is a bug. The example should collect all ID-attribute-values of the containerElements, which are iterative-recursive. The $go($go, ….) construction is inspired from Leo Wörteler’s xq-modules:

Re: [basex-talk] http:request post parameter bug? basex 7.01

Hi Andy, sorry for the late feedback. Could there be an encoding issue with http:request post requests? I send..  let $r:=http:request method='post'    http:body media-type=application/x-www-form-urlencoded method=texta=3amp;b=4/http:body  /http:request return