Ran
|
Files
119
|
Run time
5s
|
Badge
Embed ▾
README BADGES
|
push
github
Fix explicit dataset (`FROM` and `FROM NAMED` clauses) (#2794) * fix explicit dataset: FROM and FROM NAMED clause When using a FROM or FROM NAMED clause: redefine entirely the query's RDF dataset. Include only the graphs in FROM clause in the query's default graph Include only the graphs in the FROM NAMED clause in the query's named graphs Try to load external graphs only if they don't already exist in the given ConjunctiveGraph * Formatting with back and flake8 for commit d6858e0f9 Using rdflib rules * Fix import order on test_dataset_exclusive * Use Dataset instead of ConjunctiveGraph in test_dataset_exclusive and test_dataset_inclusive Since ConjunctiveGraph has been deprecated. Also define if dataset is inclusive or exclusive at Dataset init instead of using global param SPARQL_DEFAULT_GRAPH_UNION * Fix graph name def in test_dataset_inclusive and test_dataset_exclusive * Only get_context on default and named graphs once and use Dataset instead of ConjunctiveGraph * Update rdflib/plugins/sparql/sparql.py Co-authored-by: Ashley Sommer <ashleysommer@gmail.com> --------- Co-authored-by: Nicholas Car <nick@kurrawong.net> Co-authored-by: Ashley Sommer <ashleysommer@gmail.com>
5882 of 7632 branches covered (77.07%)
18820 of 21396 relevant lines covered (87.96%)
0.88 hits per line
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
---|