[basex-talk] html document retrieval runs out of main memory

2022-04-07 Thread Graydon Saunders
Hello -- I'm using the basexgui to run (minus some identifying actual values defined previously in the query) (: for each path, retrieve the document :) for $remote in $paths let $name as xs:string := file:name($remote) let $target as xs:string := file:resolve-path($name,$targetBase) let

Re: [basex-talk] Basexgui Feature suggestion

2022-04-07 Thread Tamara Marnell
Hi Steven, Just another small tip for this: > I would say that for my use cases, a few extra clicks is less trouble than > managing temporary edits to files and reverting them back again. In the BaseX GUI you can make changes on the fly in the Editor window and click the Run query button,

Re: [basex-talk] Basexgui Feature suggestion

2022-04-07 Thread Majewski, Steven Dennis (sdm7g)
Reading the docs closer https://docs.basex.org/wiki/Graphical_User_Interface#Editor It looks like the best shortcut would be saving the results to an .xml file, and using the feature of right clicking on the file to bind to ‘.’ ,

Re: [basex-talk] Basexgui Feature suggestion

2022-04-07 Thread Tamara Marnell
Hi Steven, To save a few clicks, you can create a new database directly from your results in XQuery, without saving them to a file first. Instead of returning the results outright, assign them to a variable to pass as the input to db:create() in the return, with a made-up file name for the path.

[basex-talk] Basexgui Feature suggestion

2022-04-07 Thread Majewski, Steven Dennis (sdm7g)
It would be handy if there was a way to bind results to current context for additional inspection/investigation/query of results. Currently, it seems, you would have to save results to a file and then create database from that file to make an additional query on results. That binding would be

[basex-talk] An automated workflow for creating tested and sustainable REST API/RestXQ containers that use BaseX

2022-04-07 Thread Omar Siam
For the last few years, I tried to integrate BaseX into a CI/CD workflow (the one used by gitlab [1]). My understanding of CI/CD explicitly includes automated tests so I can be as sure as possible I don’t break anything when doing further development. I pondered with using BaseX’ built in