Releases: ad-freiburg/qlever
Releases · ad-freiburg/qlever
v0.5.45
There are now official QLever packages for Debian, Ubuntu, Ubuntu-derived distributions, and macOS; see https://docs.qlever.dev/quickstart/
What's Changed
- Allow writing materialized views from queries with less than four columns by @ullingerc in #2639
- Avoid hashing twice in
BlankNodeManager::allocateBlockby @RobinTF in #2648 - When writing a materialized view, remember the query string by @ullingerc in #2653
- Show name of materialized view in
IndexScandescriptor by @ullingerc in #2655 - Ensure that tests also compile and run for
LOGLEVEL < WARNby @Qup42 in #2671 - Unload materialized view when overwritten by @ullingerc in #2657
- Use the new binary names
qlever-indexandqlever-serverin all Dockerfiles by @ullingerc in #2677 - Load materialized views when starting the server by @ullingerc in #2659
- Native
WebAssemblyakaWasmbuild withEmscriptenby @ZamirCS-369 in #2577 - Fix blank node label consistency in parallel parsing by @joka921 in #2676
- Preparations for binary index rebuild by @RobinTF in #2660
- Fix destruction order of
transformation_andview_inCachingTransformInputRangeby @tanmay-9 in #2682 - Refactor code for the evaluation of
CONSTRUCTqueries by @marvin7122 in #2652 - More efficient size estimate for
IndexScan, in particular for a full index scan by @RobinTF in #2680 - Enable fast "binary" rebuilding of the index, including updates by @RobinTF in #2408
- Lazy and prefiltered
OPTIONALby @joka921 in #2695 - Prove
UndefStatus::AlwaysDefinedfor a variety of expressions by @joka921 in #2698 - Fix division by zero bug for
FILTER(... IN ())by @RobinTF in #2702 - Insert
ql:langtagtriple when inserting triple with an object with a language tag by @RobinTF in #2674
v0.5.44
There are now official QLever packages for Debian, Ubuntu, Ubuntu-derived distributions, and macOS; see https://docs.qlever.dev/quickstart/
Version for the Autocompletion Paper
Please use this version only for reproducing the results of our Autocompletion Paper.
In this case, please consider the Caveats from the README.md
For all other uses, a stable version from the master branch is probably better suited.