This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-08-16
Channels
- # announcements (1)
- # beginners (83)
- # boot (10)
- # cider (23)
- # cljdoc (24)
- # cljs-dev (3)
- # clojure (138)
- # clojure-finland (1)
- # clojure-italy (12)
- # clojure-losangeles (2)
- # clojure-mexico (1)
- # clojure-nl (18)
- # clojure-russia (23)
- # clojure-sg (1)
- # clojure-spec (15)
- # clojure-uk (126)
- # clojurescript (94)
- # cloverage (2)
- # core-async (1)
- # cursive (98)
- # datomic (54)
- # figwheel-main (19)
- # hyperfiddle (21)
- # jobs (1)
- # jobs-rus (4)
- # leiningen (4)
- # liberator (4)
- # off-topic (15)
- # parinfer (9)
- # re-frame (23)
- # reagent (19)
- # reitit (2)
- # ring-swagger (3)
- # rum (3)
- # shadow-cljs (244)
- # sql (4)
Datomic Ion Parameters look good. All makes sense and I'm glad to see it added. +1
One thing which got my attention was the example. It shows using it to discover the db-name. That struck me as unnecessary since there can only be one ion app per datomic ion stack. Can someone give me an example of why it would be useful to have a configurable db name?
hi @U055DUUFS -- separate db names for dev, staging, CI, and production
Hi Stuart. I think dev, staging and production can't share a cloud deployment. Can you elaborate with a simple use case.
create two systems: one for dev and one production, both sharing the same code deploy application
push/deploy against the dev system until you are happy, then deploy (no new push!) to the production system
I guess my point is that in your example it's not useful for the two systems to have different db-names. There's never a conflict.
ah, right
this becomes much more interesting with query groups
when there are N deploy targets in the same system
@U055DUUFS I use multiple db-names in a multi-tenant system and its a dream.
That is going to become very exciting in our architecture and is an example where thats useful.
@U0CJ19XAM can see value in separate dbs in a multi-tenant system. Nice to know that's proven useful.
Hello, I'm trying to connect the Datomic console to an in memory database (local dev). Is it feasible?
Found this from 3 yrs ago, says âConsole cannot connect to in-memoryâ http://datomic.narkive.com/4RyKpVMd/can-the-console-be-used-against-either-an-in-memory-or-dev-database
Thereâs no such thing as read-only Datomic, right? Like if App A wants to look at App Bâs data without ever modifying it (e.g. a reporting front end), I canât just give App A read-only access to App Bâs data.
I think you could do this at the storage level
No, in the end, everyone connects to a transactor, and the transactor needs write-access to the storage
the peers can have read-only access to storage; but since they can send txs to the transactor that doesn't matter
Ok, thatâs what I was thinking, just wanted to confirm, thanks.
Thanks @manutter51.
That is sad since I have a very smooth dev workflow with integrant. I can reset the whole database with fresh dev data after a simple cider-refresh
. Also I do everything in the same JVM instance.
I wonder if there is a similar dev workflow that makes it possible to also easily have the datomic console.
Thanks @marshall. I saw that do but it doesn't seem easy to reset the database from the REPL. I made a mistake in my last post. I don't use cider-refresh
but a custom reload-with-dev-data
from the dev namespace with integrant.
(defn reload-with-dev-data []
(halt)
(go)
(dev-data/load-dev-data! @db-conn-ref))
(halt)
calls (d/delete-database db-uri)
and (go)
calls (d/create-database db-uri)
. It's instantaneous.
Do you think that I can have something similar with the dev storage without restarting the JVM process?@dam for dev purposes you might also want to check out datomock: https://github.com/vvvvalvalval/datomock
Thanks @timgilbert, I'll check that. Also I see Valentin often during Paris Clojure Meetups. I'll discuss about that with him directly next time (ping @val_waeselynck (Salut Val !)).
hi. have a datomic cloud question for any of the cognitect folks who might be around. We have a pretty complex VPC setup, and one of our requirements is that traffic from any of our âinternalâ VPCs (dev,test,etc and associated datomics) has to traverse a transit VPC to get out to the world. It looks like the IGWâs that get created are used for license checking or something? We tried just disabling one and things just broke đ . In any case, we wanted to get some input from you guys on how we might best accomodate this..
@eoliphant Datomic uses the internet gateway to access some AWS services
I donât recall which ones off the top of my head, but any AWS service for which there are not VPC endpoints available or which we havenât yet been able to transition to using VPC endpoints
let me let my guys know. weâll try to figure it out but if you guys could scare up a list thatâd be great
yeah i was wondering about the lambdas. and yeah I think my dev noticed the issue during a deploy. SO codedeploy is a likely place to look
with datomic cloud supporting :limit and :offset is there planned support for :sort-by perhaps?
nevermind apparently the sort aggregate is a thing (but I can not see it in the docs?)
I'd like to know more about this "sort aggregate". If you find something, can you share it?
Afaik, there's no in built sort aggregate. The custom aggregate example finds the mode, which of course requires sorting. At this point you'll still have to roll your own. I hope they add something. It's pretty easy to write your own, but it gets hinky if you want to use datomic's :limit and :offset. You usually want the sort applied first, then limit and offset that result. But using the native stuff its effectively reversed. In those situations i just use my own sort, limit, offset logic