This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-08-17
Channels
- # admin-announcements (63)
- # beginners (1)
- # boot (83)
- # cider (17)
- # clojure (33)
- # clojure-android (3)
- # clojure-france (3)
- # clojure-gamedev (1)
- # clojure-russia (20)
- # clojure-sg (9)
- # clojurescript (81)
- # core-async (77)
- # cursive (13)
- # datomic (30)
- # hoplon (7)
- # instaparse (54)
- # ldnclj (1)
- # off-topic (4)
- # om (2)
- # onyx (23)
- # re-frame (16)
- # reagent (3)
- # yada (2)
@joshg: I'm not currently using datomic but I think this question has come up before so you might want to check the archives if you haven't already: http://clojurians-log.mantike.pro/datomic/
@meow: Thanks. The best resource I’ve found thus-far has been: https://www.youtube.com/watch?v=7lm3K8zVOdY
@joshg: if you're planning to give your clients arbitrary query power (even on a subset of your db using filter
) keep in mind that they still can build queries that will consume all of your resources. So I don't recommend that in the general case.
I personally used the old way: parameterize all my endpoints with some access restriction configuration, using Ring middlewares to query the db for the right authorization. I have found that recursive rules can be a very powerful tool for this.
hi guys, this question was kind of answered before but I didn’t have the database in front of me like I do now so I couldn’t quite get the spoon feeding that I need 😊
but I cannot work out how to ask datomic… give me the entity that changed as a result of that tx
I’m still breaking my head with this stuff so anything on a spoon would be happily received!
raymcdermott: you have a txid and you want a list of entities it touched?
(d/q '[:find ?e :where ?t [?e _ _ ?t]] db tx-id)
the transact function returns a bunch of data. included are all the new datoms, as well as a map of temp -> storage ids
@raymcdermott: I usually return the tempid then d/entity
on it
you should find everything you need in there
https://github.com/clojure-cookbook/clojure-cookbook/blob/master/06_databases/6-12_transact-basics.asciidoc covers the essentials
What major changes would someone upgrading from Datomic Free 0.8.4218 to Datomic Free 0.9.5206 encounter?
Only one I've found so far is "Alter Schema" in 0.9.4470, which says "This feature breaks compatibility with older versions. Once a schema alteration has been performed on a database, only connect peers and transactors running at least [this version] to that database." but I don't quite know how to interpret that.
@sdegutis: re: alter schema: it's just saying that once you use the alter schema feature of >=0.9.4470, there is no going back to an earler version of datomic
Thanks @bostonaholic.
and I would suggest going through the changelog to get the best answer
@bostonaholic: That's all it says. I've been going through the 500 lines in the full changelog between our current version and the latest.
Successfully upgraded from 0.8.4218 to 0.9.5206 with no visible issues so far. It was pleasantly smooth. Just FYI.
my secret plan to start moving to datomic by using the ruby gem was deflated today, Yoko said the gem is behind and I’m better off using clojure