This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-18
Channels
- # aleph (4)
- # announcements (2)
- # babashka (48)
- # beginners (59)
- # calva (5)
- # cider (14)
- # clj-kondo (4)
- # cljs-dev (3)
- # clojure (77)
- # clojure-europe (6)
- # clojure-italy (6)
- # clojure-nl (5)
- # clojure-spec (4)
- # clojure-uk (67)
- # clojurescript (19)
- # clr (3)
- # cursive (7)
- # datomic (36)
- # duct (33)
- # events (3)
- # figwheel (1)
- # fulcro (4)
- # funcool (2)
- # graalvm (3)
- # jobs (1)
- # joker (25)
- # kaocha (1)
- # leiningen (45)
- # malli (17)
- # off-topic (103)
- # quil (1)
- # re-frame (16)
- # reitit (1)
- # rewrite-clj (27)
- # shadow-cljs (39)
- # spacemacs (3)
- # sql (11)
- # tools-deps (14)
- # vim (41)
is it not possible to use reverse navigation style in tx-data within entity maps? im getting an invalid lookup ref error:
{:cognitect.anomalies/category :cognitect.anomalies/incorrect,
:cognitect.anomalies/message "Invalid list form: [#:db{:id 17592186045418}]",
:db/error :db.error/invalid-lookup-ref}
when trying this:
{:db/ident :new-entity-being-pointed-to-by-a-card-many-attr
:card-many/_attribute [{:db/id 132} {:db/id 345} ...]}
or "Invalid list form: [17592186045418]"
when just trying :card-many/_attribute [123 345]
it would be the inverse of a pull expression containing reverse navigation, eg:
;; pattern
[:artist/_country]
;; result
{:artist/_country [{:db/id 17592186045751} {:db/id 17592186045755} ...]}
https://docs.datomic.com/on-prem/pull.html#org31dcc1a[{:db/ident :new-entity-being-pointed-to-by-a-card-many-attr :card-many/_attribute 132} {:db/ident :new-entity-being-pointed-to-by-a-card-many-attr :card-many/_attribute 345} {:db/ident :new-entity-being-pointed-to-by-a-card-many-attr :card-many/_attribute ...} {:db/ident :new-entity-being-pointed-to-by-a-card-many-attr :card-many/_attribute ...}]
hmm... interesting. thx.
i guess it's simpler to just use the forward reference than and the :db/add
function style
Datomic cloud question: is it possible to run local only integrations test without access to aws infra ?
I tried https://github.com/ComputeSoftware/datomic-client-memdb based on peer
library for an in memory db.
But it looks like it doesn't support tuples
during schema creation.
it uses datomic-free by default, which hasn’t been updated in a while (i.e. since before tuples were introduced)
anyway, all on-prem licenses are perpetual, so you can keep using this forever. plus you are not actually running a transactor
I don’t remember datomic string being limited to 256 chars, is this a change? Or am I misremembering?
@U09R86PA4 just wondering if there was ever any plan to do edn or blob type? Or is string supposed to be for that usecase?
they never give roadmaps, so I donno for sure, but this table talks about “LOB” types: https://docs.datomic.com/on-prem/moving-to-cloud.html#other
this is a technique you should use with large objects in datomic anyway (strings or binary) even for on-prem
@U064X3EF3 Sorry to bug you, but just wondering if there’s any way of knowing if/when LOB
types are planned for?
I'm not on the Datomic team
so I don't know any more than you :)
Are there any tools to validate datalog? For instance you can’t use (and ...)
as a direct descendant of :where
. My use case is to validate something that programmatically generates datalog from some input.
https://lambdaforge.io/2019/11/08/clj-kondo-datalog-support.html is new, might help
For anyone who may run into this in the future.... Our team was seeing datomic cloud deploys work for one developer while failing for another developer when we had the exact same clj files, deps.edn, and ion-config.edn files (copied and pasted from the dev who successfully deployed). The deploy ended up working on a clean git clone into a new directory. We figured out that we had run a "compile" in the local directory of the dev with the failing build and the "classes" directory was being executed instead of the new clj source files. Removing the classes directory solved our problem and we can now deploy.....