Co-authored-by: Marcela Poffald mpoffald@flur.ee

This allows us to properly retrieve commit flakes from the cache.

Co-authored-by: Marcela Poffald mpoffald@flur.ee

Both the dbId subject flake and the ledger time had the @id of :f/time.

It turns out if you have a flake with a predicate of `const/$iri` (0), the datatype of the
flake must be a `const/$xsd:string` (1). Otherwise the query select mechanism will try
to resolve the flake object's @id, but that requires the flake object to be a subject
id.

These commit schema flakes had predicate: iri and datatype iri, which was causing
queries that referenced them to blow up.

The problem was we were only using the `(next-sid)` result in the new issuer flake but
not in the reference pointing to it. Now we use it in both flakes if we need both
flakes.

Co-authored-by: Marcela Poffald mpoffald@flur.ee

We were not creating an @id for the commit, which was inserting nils for the commit
subject.

Also refactored the creation of commit flakes to make each group of flakes more clear
and only create new sids when we actually use them.

Updated the s+p+o query test to not expect nil subjects and control for the source of
non-determinism in a commit.

Co-authored-by: Marcela Poffald mpoffald@flur.ee

Co-authored-by: Marcela Poffald mpoffald@flur.ee

Also refactored commit to generate flakes first and the merge them into novelty.

Co-authored-by: Marcela Poffald mpoffald@flur.ee

Now we can rebuild the Commit document from a query.

Co-authored-by: Marcela Poffald mpoffald@flur.ee

Changed the commit data to all share the same subject id: t. Added one missing
vocabulary term for commitdata-address. Now s+p+o returns all flakes with no nils.

Co-authored-by: Marcela Poffald mpoffald@flur.ee

# Conflicts:
#	dev/user.clj
#	src/fluree/db/api/query.cljc
#	src/fluree/db/json_ld/api.cljc
#	src/fluree/db/json_ld/vocab.cljc

The `vocab/update-with` function didn't do what I expected - it takes a db and returns a
schema, and I was expecting it to return a db with the updated schema. Instead I swapped
it with the `vocab/update-with*` which takes a schema and some vocab flakes and returns
a new schema cache.

Also added the `test-with-files` dep to the :dev deps so I can run the test from
api-tests from the repl.

…e cleanup

   We don't need flakes of the type `[s const/$rdf:type o ...]`, now that we have a `.-dt` field on flakes

…nd asserts/retracts

Co-authored-by: Daniel Petranek <dpetranek@flur.ee>

We don't need special iris for commit-related flakes, eg `iri-commitdata-v`. The property `v` is the same property, denoting a version, regardless of whether it appears in a commit document or elsewhere.

`asserts` should include just the actual data transacted by user

# Conflicts:
#	src/fluree/db/api/query.cljc
#	test/fluree/db/query/history_test.clj

Co-authored-by: Marcela Poffald <mpoffald@flur.ee>

We're now no longer duplicating the key compaction work at several levels.

Co-authored-by: Marcela Poffald <mpoffald@flur.ee>

This should fix the cljs tests.

closes #339

Co-authored-by: Marcela Poffald <mpoffald@flur.ee>

Co-authored-by: Marcela Poffald <mpoffald@flur.ee>

These are so close to being the same thing that we thought we'd try them with a unified
query syntax.

Co-authored-by: Marcela Poffald <mpoffald@flur.ee>

Unified the query syntax for history and commit queries. Specifying a time range is now
required, which should simplify the explanation of the query syntax.

also:
- removed some dead code
- updated docstrings

Co-authored-by: Marcela Poffald <mpoffald@flur.ee>

… result

This updates `add-commit-details` to loop through the commit results and chunk together those results with continuous `t`s. We then retrieve commit details for the range of that chunk, rather than for each result.

In cases where history results have such continuous results, we can reduce the number of times we make `tspo` range calls to retrieve commit data.

# Conflicts:
#	src/fluree/db/json_ld/commit.cljc
#	test/fluree/db/query/misc_queries_test.clj

We had to sneak the previous commit into the commit-flake-addition process in order to
get the previous commit and commit data ids.

We also had to update how we were constructing the results to not filter the iri flakes
out of the commit flakes because we need ids in the final map.

Co-authored-by: Marcela Poffald <mpoffald@flur.ee>

Co-authored-by: Marcela Poffald <mpoffald@flur.ee>

This way we are not unnecessarily realizing the whole list of history results before going through them again to add commit-details.

We removed some unnecessary go-blocks, added more explicit error handling, tried pushing
the realization of the final results as high up the call stack as we could.

Co-authored-by: Marcela Poffald <mpoffald@flur.ee>

We changed the default sort order of the history query to be in ascending order by t -
earliest change first. This matches the default tspo sort order, so we no longer have to
sort the commit flakes. History still needs to be sorted because sometimes it uses
non-tspo indexes to satisfy the query.

Moved the async into calls as high up the call stack as we could, and removed
unnecessary go blocks.

Co-authored-by: Marcela Poffald <mpoffald@flur.ee>

time-range returns a stream of flake slices, where each slice is the subset of flakes
from an index leaf. Up to now we have been treating this as a promise and only taking
the first result off the time-range chan. Now we treat it as a proper stream.

Co-authored-by: Marcela Poffald <mpoffald@flur.ee>