This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-01-23
Channels
- # aatree (72)
- # aws (12)
- # beginners (34)
- # boot (256)
- # braid-chat (12)
- # cider (20)
- # clara (8)
- # cljs-dev (1)
- # cljsjs (1)
- # cljsrn (38)
- # clojure (61)
- # clojure-dev (10)
- # clojure-ireland (1)
- # clojure-japan (1)
- # clojure-sg (2)
- # clojurescript (48)
- # community-development (3)
- # conf-proposals (3)
- # core-async (6)
- # cursive (8)
- # datomic (4)
- # emacs (9)
- # hoplon (1)
- # leiningen (1)
- # mount (9)
- # off-topic (4)
- # om (109)
- # parinfer (26)
- # perun (4)
- # proton (5)
- # reagent (14)
- # vim (3)
@currentoor: you might want to look at om next.
@currentoor: Any Datomic Peer (or anything with unrestricted access to a Peer, like the ReST interface) can do anything to the database. If you are offering a service to untrusted clients, you'll want to provide a service interface that limits what they can do. For example, you could write your own parser for a restricted subset of Datomic's datalog that you know is safe. You have to decide what to allow: For example, parentheses could be either rule invocation or method invocation.
in case anyone else finds this useful...I created a db function to compose an existing parent identifier with another association in an entity transaction: https://gist.github.com/tylermorten/d8484a07229ec4d4f5ff
@nxqd, @stuartsierra thanks for the advice