This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-08
Channels
- # 100-days-of-code (4)
- # aws (1)
- # beginners (69)
- # business (1)
- # calva (1)
- # cider (10)
- # cljdoc (1)
- # cljs-dev (7)
- # clojure (49)
- # clojure-dev (4)
- # clojure-italy (2)
- # clojure-nl (11)
- # clojure-russia (2)
- # clojure-spec (7)
- # clojure-uk (64)
- # clojurescript (18)
- # clojurex (1)
- # core-async (11)
- # cursive (22)
- # datascript (7)
- # datomic (45)
- # editors (6)
- # emacs (7)
- # events (1)
- # fulcro (20)
- # graphql (1)
- # jobs (18)
- # jobs-discuss (132)
- # leiningen (2)
- # nyc (5)
- # off-topic (6)
- # onyx (2)
- # pedestal (3)
- # re-frame (8)
- # remote-jobs (6)
- # ring-swagger (2)
- # shadow-cljs (64)
- # specter (2)
- # tools-deps (4)
- # unrepl (1)
- # yada (3)
@jarppe I get that. But I’m assuming Ions handles all the Lambda work so you essentially just write Clojure code? I’m not up on all of it. I’m in the front end world
question on ions push: it complains that there is a :local/root
dependency and hence you have to specify a uname. However, what if this local dependency is in the same git repo, shouldn't that use the git commit then? (we are migrating to ions, but have to keep the existing API available, so we have introduced multiple deps.edn projects in the same git repo)
looking for some advice on data modeling best practices. I'm currently using a compound key to track information but my intuition tells me that this is an anti-pattern
Obviously it would be ideal if I could omit the :item/key
and have the uniqueness of the datoms be predicated on :item/name
, :item/category
, and :item/subcategory
but predictably if I make those :db.unique/identity
it's steam-rolling other datums
Have you looked at https://github.com/arohner/datomic-compound-index? It does not solve the problem but sheds light into it
interesting. Well at least I'm not the first person to run into this 🙂
@goomba There’s nothing inherently “wrong” with modeling compound uniqueness as a munged-key
but, if you actually require compound uniqueness semantics, then you need to do something like that
yayyyy okay great.
vector
of keywords
ahh sorry I'm actually putting the hash value of the vector but for omitted that for simplicity
"simplicity"
but if you made them something like compound strings, they would sort more ‘realistically’
ahh good point. yeah I'm at the dev phase where I just throw everything at the wall and see what ticks
but that's a better idea
thank you 🙂
hi all, im struggling to find out how to determine the txinstant of the last commit to the db
Is there any way to query and get one or a few results that doesn't require retrieving a large amount of data (assuming a cold peer, in this case my local [on-prem] REPL)? I think (is this correct?) that both the :find ?e .
find specification and the sample
aggregation function retrieve the complete result set before cutting it down. It's fairly common (for me at least) to want to get a couple of representative matching entities in a fast way, and it seems like there would be some way to achieve that with a query.