basex
basex copied to clipboard
BaseXdb
BaseX Main Repository.
Besides type inspection (#2300), there is at least one more problem with the current representation of `enum` types: `MapType.keyType`, as a `Type`, can currently only hold `AtomType.ENUM` and misses the...
These changes add support for the `UnionNodeTest` grammar rule and maps it to a `UnionTest` instance, by also lifting the restriction that a `UnionTest` combines only tests with the a...
The support for calling user-defined functions needs to be extended by - handling keyword arguments, - establishing the correct order of parameters of partially evaluated functions. This may deviate from...
Function coercion of a map or array item is currently skipped, when the `funcType` of the item passes an instance test for the required function type. This however preserves its...
Per XQuery 4, the different forms of accessing an array element, by - using the array as a function item, - `array:get`, and - the lookup operator `?`, are all...
The type output of `inspect:type()` and `prof:type()` should be improved for enum types. To achieve this, the cleanest approach could be to introduce an `ItemType` that encapsulates the enumeration values.
Currently, global file write locks are enforced for updating file operations like `file:write`. We could implement a more fine granular file lock, and enforce sequential activity only if a file...
Caused at runtime by tail-call optimizations: ```xquery let $f := fn($p, $self) as xs:integer { if((1 to 10000)[$p + 1]
The following code raises `.: Context value is undefined.`: ```xquery declare record basex:r( f as fn() as item() ); basex:r(%method fn() { . })?f() ``` It works if the function...
One of the tests seems to fail occasionally: ``` Error: Errors: Error: ServerCommandTest>CommandTest.after:65->CommandTest.cleanUp:57 » BaseX User 'Sandbox2' is logged in. ```