[basex-talk] Unconfirmed bug: NPE using cached transformer

Hello, I'd like to run a transform on multiple documents using a cached transformer, accumulating any errors that occur. This minimal example - for $doc in (,, ) return try{ xslt:transform( $doc, http://www.w3.org/1999/XSL/Transform; version='2.0'> , map{}, map{'cache':'true'} )

Re: [basex-talk] Unconfirmed bug: NPE using cached transformer

Many thanks, Christian. - Andrew On Sun, 26 Apr 2020 at 11:15, Christian Grün wrote: > Hi Andrew, > > > Error in xsl:sequence/@select on line 1 column 135 of [...]: > > FOER: Error signalled by application call on error()Improper use? > Potentia > > l bug? Your feedback is welcome: > >

Re: [basex-talk] User group meeting in Prague?

Excellent idea, Gerrit - have appended my name to the list on the wiki. (Great group name, btw.) Andrew On Fri, 17 Dec 2021 at 16:02, Imsieke, Gerrit, le-tex < gerrit.imsi...@le-tex.de> wrote: > Fellow BaseX Users! > > You might have heard that XML Prague 2022 will take place in June. > (Unless

Re: [basex-talk] Techniques for Unit Testing Updating Operations

> > within a single unit:test function that itself performs an updating > function there’s no way to then evaluate the result of the update as any > asserts will be in the same transaction. > That's where %unit:before and (more likely) %unit:after come in. You can't make the update and assertion

Re: [basex-talk] Techniques for Unit Testing Updating Operations

> > I don’t see a way to use %unit:before-module to initialize my databases > before running unit tests in the same module. > I've successfully used %unit:before-module and %unit:after-module to set up (db:create) and tear down (db:drop) databases respectively, and then %unit:before to update

Re: [basex-talk] Techniques for Unit Testing Updating Operations

> > But maybe the test runner runs unit:before-module() as a separate > transaction? > That does look to be the behaviour -- the phrase "This extension is e. g. helpful if the results of updates need to be tested." and the accompanying code snippet [1] imply as much to me, but it would be good

[basex-talk] Timeframe for supporting fn:load-xquery-module()?

Hello, The docs say: "The three functions fn:transform, fn:load-xquery-module and fn:collation-key may be added in a future version of BaseX as their implementation might require the use of additional external libraries." Is there a timeframe for this? I'm interested in particular in the

Re: [basex-talk] Timeframe for supporting fn:load-xquery-module()?

ow> | YouTube > <https://www.youtube.com/user/servicenowinc> | Facebook > <https://www.facebook.com/servicenow> > > > > *From: *BaseX-Talk on behalf > of Christian Grün > *Date: *Thursday, June 8, 2023 at 2:46 AM > *To: *Andrew Sales > *Cc: *BaseX >

[basex-talk] xquery:eval() - handling of

Hello, The query xquery:eval( 'contains(.,"")', map{'':} ) results in: [XPST0003] Invalid entity: '&")...'. I can get the expected result if I double-escape the entity: 'contains(.,"amp;")' or wrap in a call to serialize: serialize('contains(.,"")') However, both xquery:eval(

Re: [basex-talk] xquery:eval() - handling of

Many thanks for explaining, Christian - that makes sense. Thank you also for 10.6! All the best, Andrew On Wed, 10 May 2023 at 21:34, Christian Grün wrote: > Hi Andrew, > > > 'contains(.,"")', > > … > > return true, as expected. > > The difference is that < and > don’t have to be encoded if