Ask questions on the official Q&A site at https://ask.datomic.com!

+1 for pyry’s suggestion, keeping an index outside of the main Datomic database

tvaughan 2020-11-25T11:10:28.001200Z

Thanks. I worked with Postgres and Elasticsearch and this is the approach we took then too.

favila 2020-11-25T16:48:11.003400Z

I noticed attribute predicates check explicitly retracted values (from user-supplied tx data or tx-fn expansions) but not implicitly retracted values (from cardinality-one attributes with a new assertion). 1) Why check retractions at all? 2) Why this difference? I’m observing this on on-prem 1.0.6165 if it makes a difference.

favila 2020-11-25T16:49:46.003500Z

I would prefer that attribute predicates are never run on retracted values as it makes it much easier to migrate to cleaned-up values. In our case we’re installing string length limits, and would be ok with old values being too long as long as new values are not.

favila 2020-11-25T16:50:26.003700Z

It also means we need some kind of atomic tx fn to install an attribute predicate safely.

alexmiller 2020-11-25T17:01:43.003900Z

might be better to log this at https://ask.datomic.com ...

favila 2020-11-25T17:10:30.004200Z

IMO this is a bug report; I’m just being polite 🙂

alexmiller 2020-11-25T17:15:39.004400Z


alexmiller 2020-11-25T17:16:52.004600Z

standard support channels are best, then ask.datomic as it creates a searchable archived record for the future, and then here is good for conversation but checked less frequently than the above