This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-11-26
Channels
- # admin-announcements (70)
- # aws (1)
- # beginners (17)
- # boot (37)
- # business (1)
- # cider (2)
- # cljs-dev (56)
- # cljsrn (6)
- # clojure (151)
- # clojure-germany (1)
- # clojure-nl (5)
- # clojure-poland (5)
- # clojure-russia (34)
- # clojure-taiwan (1)
- # clojurescript (289)
- # clojurex (2)
- # cursive (16)
- # datavis (3)
- # datomic (12)
- # editors (10)
- # emacs (3)
- # hoplon (17)
- # ldnclj (5)
- # lein-figwheel (12)
- # leiningen (1)
- # liberator (1)
- # off-topic (23)
- # om (116)
- # onyx (39)
- # parinfer (44)
- # portland-or (1)
- # reagent (34)
- # yada (6)
@sdegutis: we have an Onyx system that watches the Datomic log and inspects the datoms to figure out if it needs to do any stats work
Hi! Not sure if this the right place to ask or the clojure channel is better. But here it goes: is there some sort of naming convention for functions that call datomic queries?
for instance how would you name a query function that retrieves all entities of a specific type and how one that takes a specific input?
we use Datomic as our sole database. i don’t think we have any sort of definable convention for our function names
we’ve taken the pragmatic approach of naming them as simply as possible, based on the semantic meaning - (defn active-users-for-group [group])
- that sort of thing
thanks @robert-stuttaford. Probably it is a good enough approach. Only it can get verbose I suppose for multiple inputs?
I was wondering if there was some kind of styling standard a bit like https://github.com/bbatsov/clojure-style-guide#naming
it definitely can get verbose, but we apply pragmatism to that, too. quite often, we end up breaking the function part
wonderful thing about Datomic; no need to query the whole world in one go!
i don’t think Datomic has seen broad enough use to warrant there being a guide such as that
what’s really cool about Datomic is that you can almost forget that the data is not inside your app process… that is, it’s just normal data filtering code like any other FP