Queries passed to db fns #1
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1. Queries containing `not` clause 2. Queries using rules that contain `or` clause Running against latest Datomic Free transactor 0.9.5703.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Report 1 2018-11-22
Running against latest Datomic Free transactor 0.9.5703 (but same issue shows
when running against lastest Datomic Pro version 0.9.5786 too).
Details
Two issues show up, but they might be somewhat related.
Suppose that a database function is used to ensure correct atomic updates. Such
a generic function could, for instance, take a query and arguments for a query
as function arguments. Based on the query results, the function may allow the
transaction or throw.
Using such a function, we discover two issues:
notclause behave unexpectedly.orclause break.See src/datomic_bug_report/core.clj for
example.
Since neither issue manifests when using the Datomic in-memory database, it
seems that the underlying cause might be something related to serialization on
the wire.