Christian Grün
Christian Grün
Thanks for the summary, Adam. If you got some spare time, it would be interesting to see timings for the fold-left and window solutions added.
Lots of surprises indeed! I learned quite something by comparing the different approaches.
I didn't think of that.. Sounds like a good idea!
Good point. Option 2 sounds more attractive to me; I think the output of this function should be as intuitive as possible.
A flag may indeed be the best choice. As `prof:variables` is not supposed to be used in productive code, we can change or extend the function signature without too much...
Do you know what's the most convenient way to access all potentially reachable variables? This is the current code... https://github.com/BaseXdb/basex/blob/master/basex-core/src/main/java/org/basex/query/var/QueryStack.java#L132-L141
Issues to solve: - If the BaseX command-line interfaces are run (`basex`, `basexclient`, `basexgui`?), output should probably always be directed to standard out/err. This could e.g. be solved by an...
Hi @BenoitMaisonny, thanks for your offer; pull requests are always welcome. I guess one challenge will be to preserve the CLI features of BaseX (i.e. to decide when output to...
Thanks for the inspiring feedback… I'm trying to summarize our first ideas: **Smallest Entities** We'll probably settle down on having database resources (XML, binary) as smallest observable entity. Once we...
> So wouldn't it make sense to move all functionality there? Right, that's what I would propose. Your example makes sense. > This way, we could have a simple TRIGGER...