Clojurians Log v2

do you have a small sample of how you are making/querying the session?

In the RHS of my rule I have

(insert! (->TimeLimit "10 business days" "preliminary"))

(defquery nothing
  []
  [?time-limit <- e/TimeLimit])

; Execution error (IllegalArgumentException) at clara.rules.platform/throw-error (platform.cljc:5).
; The query {:lhs [{:type e/TimeLimit, :constraints [], :fact-binding :?time-limit}], :params #{}, :name "user/nothing"} is invalid or not included in the rule base.

is it fair to assume the loading/running of these rules looks something like:

(-> (mk-session [rulename nothing]) 
  (insert (->SomeEntryFact))
  fire-rules
  (query nothing))

Does it matter that I've bound my session to a var and then queried it using that name? I would assume that's fine.

binding it as a variable should be fine

hm deep_thinking I'm sure I'm doing something silly

Do my queries need to be defined in the same ns I load for my session? That must be what it is

if you aren’t explicitly providing namespaces or rule/query defs to the mk-session call, then they wouldn’t likely be loaded. something like:

(mk-session)

got it, I knew it was gonna be something dumb like that. Thanks.

dumb that I was doing I mean

its not really dumb. Im not a huge fan of default behavior all that much… feels a bit too “magic” to me

I definitely made a somewhat arbitrary decision here to have my rules in one ns and queries in another, so lesson learned there but yeah defaults not always my friend either.

to your credit, you are not the first and certainly not the last to decide to do it that way. I am aware of other implementations that decided to retroactively add “transitive namespace scanning” to their codebase to determine all of the possibly available rules. I highly recommend that everyone avoid that though 😄

> I highly recommend that everyone avoid that though transitively loading namespaces that is. Separation of of rules and queries is likely fine, but when loading them ideally be specific. ex.

(def session (mk-session `rules-namespace  `queires-namespace))