say I have a relationship between two entities foo and bar --I can express it with a join :foo/bar-join or :bar/foo-join. If I know that the majority of the time I will be querying for bars given some foo instead of vice versa, would it be much more efficient to have :foo/bar-join instead of :bar/foo-join? My best guess is that the performance of this query for :foo/bar-join has to be the most performant one, since the query engine would just have to look at what values are in the join attribute on the entity whose ID we already know, but I'm not sure just how much worse I can expect a :bar/foo-join to be

Evening - 1.18.0 is out 🚀 * Significant improvements to the Lucene module - it now supports checkpointing, in-memory Lucene, and Crux will now ensure the Lucene index is up-to-date on startup. Requires a Lucene re-index for folks who have Lucene indices. * Ability to add 'secondary indices' (of which Lucene is the first) - custom indices that follow the Crux tx-log alongside the main indices. Can be used (for example) to create materialized views of your Crux transactions in other formats/stores - we're intrigued to see how folks use this 🙂 * First alpha release of crux-corda - adds the Corda blockchain (https://corda.net) as a possible source of Crux transactions, allowing you to query both the current and historical state of your Corda nodes using Crux's temporal queries. Keep your eyes peeled for some blogs over the coming weeks! * All the usual bugfixes 🐛 For more details, see the release notes at https://github.com/juxt/crux/releases/tag/1.18.0. As always, a big thanks to everyone contributing to this release by raising/fixing issues, and helping us with repros!

hey Im trying to delete all crux entries in between tests, whats the best way of doing it? reading all entries and evicting one by one in a tx?

I need some help understanding entity-history

;; When submitting a single tx for valid range 2001 to 2002 on an in-memory node
(crux.api/submit-tx 
                   crux
                   [[:crux.tx/put {:crux.db/id "test"} #inst "2001" #inst "2002"]]

;; I expect no history when specifying a later valid time range,
;;  but get the tx with a valid time of 2001-2002
(crux.api/entity-history 
                   (crux.api/db crux) "test"
                   :asc 
                   {:with-docs? true
                    :start {:crux.db/valid-time #inst "2020"}
                    :end {:crux.db/valid-time #inst "2021"}})
                            
;; Result                   
[{:crux.tx/tx-time #inst "2021-07-30T21:43:43.644-00:00",
  :crux.tx/tx-id 0,
  :crux.db/valid-time #inst "2001-01-01T00:00:00.000-00:00",
  :crux.db/content-hash
  #crux/id "5357154b961bd22dc5ddbc7fec9580419964976c",
  :crux.db/doc #:crux.db{:id "test"}}
 {:crux.tx/tx-time #inst "2021-07-30T21:43:43.644-00:00",
  :crux.tx/tx-id 0,
  :crux.db/valid-time #inst "2002-01-01T00:00:00.000-00:00",
  :crux.db/content-hash
  #crux/id "0000000000000000000000000000000000000000",
  :crux.db/doc nil}]