You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, sorry that I'm informing about issue instead to provide a solution, I just start to use this library in the java project which builds datalog queries from SQL dialect so Clojure is something very new for me :) Let me describe the cases when optimized queries became not executable by the datomic:
But makes sense to mention for the case not-join within or-join that if there is condition within or-join which populates ?Root then [?Root :typeName ?typeName] can be put at the bellow of total query, so the next optimized query will be executed
nikolayandr
changed the title
Do not move datoms which create variables used in functions or not-join which is inside or-join
Do not move datoms which create variables used in functions/not-join which are inside or-join
Jan 6, 2021
Hi, sorry that I'm informing about issue instead to provide a solution, I just start to use this library in the java project which builds datalog queries from SQL dialect so Clojure is something very new for me :) Let me describe the cases when optimized queries became not executable by the datomic:
Original query:
Optimized query is:
On attempt to execute such query Datomic says:
:db.error/insufficient-binding [?Root] not bound in expression clause: [(missing? $ ?Root :attribute)]
Similar situation is for a case when not-join is used within or-join
Original query:
Optimized query is:
The text was updated successfully, but these errors were encountered: