xquery
Here are 207 public repositories matching this topic...
Values of an HTTP request will be assigned to the parameters of the invoked function. If the assignment fails, the returned error message should be more intuitive:
- Right now, it indicates what went wrong during the variable assignment in XQuery.
- The returned message should rather indicate how the request can be rewritten by the client to be successfully processed.
Examples
-
Updated
Jun 14, 2020 - Pascal
Is your feature request related to a problem? Please describe.
Running the code below will result in two different error messages:
xquery version "3.1";
try { [1,2,3,4](-1) } catch err:FOAY0001 { $err:description },
try { array:get([1,2,3,4], -1) } catch err:FOAY0001 { $err:description }- "Array index out of bounds. Position -1 does not exist in this array. Length
Is your feature request related to a problem? Please describe.
There are existing data in one DB which I need to harmonise and customise data using data hub.
What is the user-facing scenario that prompted this gap in functionality?
Existing data is in one DB, need the best practice to further harmonise and customise such data using data hub.
Describe the solution you'd like
A
Thank you for submitting an issue!
If this is a bug, please use the bug template below. If this is an enhancement request, please use the RFE template below. Before submitting your issue, please do us a favor and search currently open issues. If your issue already exists, please make a comment there advocating your issue be addressed sooner.
Bug Template
The issue
Short des
-
Updated
Jul 4, 2020 - HTML
The link in the JavaDoc comments for PojoQueryBuilder:
Is generating a broken link pointing to appendix B of the Rest Developer's guide in the JavaDocs.
-
Updated
May 11, 2018 - XQuery
collections can be assigned a number of handlers/processors, who can
- perform data encryption
- manage document TTL (retention policy)
- manage document accessibility
in, general, this is to make collections a common mechanism to perform some actions on group of documents. the set of actions must be extendable and it must be possible to develop and register new handlers/processors
From @Frederic-P in eXist-db/documentation#231 (comment):
There should be at least a link referencing the documentation of eXide where users are informed about. The current reference material (at http://exist-db.org/exist/apps/eXide/docs/doc.html and https://exist-db.org/exist/apps/doc/learning-xquery.xml) do not cover the following things:
- The
-
Updated
May 6, 2018 - JavaScript
As you're developing your project websites, some of you will want to review or take a crash tutorial on flexboxes. I've just located a terrific video tutorial on this, with great visual examples of how to do everything: https://www.youtube.com/watch?v=k32voqQhODc
And here's one of my favorite static (non-video) tutorials on flexboxes:
https://medium.com/@js_tut/the-complete-css-flex-box-tutori
-
Updated
Apr 20, 2020
-
Updated
Jul 1, 2020 - Java
-
Updated
Nov 29, 2017
-
Updated
Jun 16, 2020 - Java
Add support for running MarkLogic Roxy/Unit tests.
-
processor.test-- API -
processor.impl.roxy.test-- https://github.com/marklogic-community/roxy -
processor.impl.roxy.test-- https://github.com/marklogic-community/marklogic-unit-test
NOTE: Both roxy and marklogic-unit-test provide the same test API.
- Write a quick query-update-map snippet in a new buffer and debug it (“Launch”)
- Start with ml-gradle Data Services example
- Paste in the snippet from 1
- From terminal 1:
./gradlew mlDeploy - From terminal 1:
./gradlew -i mlWatch - Create launch configuration
{
"type": "ml-jsdebug-
Updated
Oct 29, 2017 - Java
Improve this page
Add a description, image, and links to the xquery topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the xquery topic, visit your repo's landing page and select "manage topics."
This would give us a better starting point for getting a Kubernetes cluster up and running in the future.
Maybe also using the GraalVM with native binaries. As we didn't use reflection and other stuff which would prohibit the use of native binaries the only thing now is that we moved to Java 13 and the GraalVM just started to support Java 11.