@joshkh yes, you deploy to a group which can be a query group or a primary compute group

gotcha. so if we want different deployment stages for an ions related project we'd create two query groups with the same existing system name (storage) stack and different application names such as myapp-dev and myapp-prod?

yep

well

yes, you could do that

and/or you could leave the application name the same

and deploy separately to them

the group will be the stack name of the query group stack

okay, so then here's the part that's confusing me: what does :app-name represent in my project?

app-name defines the codedeploy target group

for the ion deployment

so having the same app-name in multiple query groups and/or primary compute groups allows you to deploy the same ion project to any/all of them

i.e. if you wanted to have one QG that got testing/beta builds of your app

ah!

you’d deploy the same ion project to it, but different versions (shas)

that way when you’re ready to promote a build/version to production you dont have to change your code at all

in fact, you wouldnt even need to re-push

you can just deploy it to additional/other QGs

whereas if you use different application names, you’d need to change the app name in the config and re-push to be able to ship it to your other group(s)

okay, so let's say for my myapp project i've created two query groups, one for dev and one for prod, and i've given them the same Application Name aka code deploy target. how do i choose to deploy to only one of them if they have the same group name?

> whereas if you use different application names, you’d need to change the app name in the config and re-push to be able to ship it to your other group(s) that's exactly what i'm trying to avoid 🙂

when you push you’ll see a list of possible groups to deploy to

in the return message from push

ah. this is what i get for automating my deployments 😉

thanks a lot marshall. i'll have a look.

and, in particular, that group name is the name of the stack

so if you have my-qg1 and my-qg2

when you deploy you replace $group in the command with whichever one you want to deploy it to

great, thanks for your help.

np

Hi quick question, had to do some work on an older on-prem project, and forgot to add :db/index true to some new attrs, I’ve since fixed it, but was just curious about the behavior for datoms that were already transacted. do they get indexed in the background or something?

Let's say I have a datomic db instance that I have by doing (let [db (d/db conn)] is there a way to go back and get the conn from the db i just made .... (let [conn (?some-method-to-extract-conn? db)])

no

remember that db instances are values, connections are stateful

oh well .. got it ..

kind of goofy thing to do you might think, but if you say why i wanted to do it you might thing .. oh ok .. not so goofy

how would i query for all of the datoms in a given transaction (equivalent to drilling in to the Transactions tab in the Datomic Console)? if i try this:

(d/q '[:find ?e ?a ?v ?t
       :in $ ?t
       :where
       [?e ?a ?v ?t]]
     (d/db conn)
     13194139536455)

Execution error (Exceptions$IllegalArgumentExceptionInfo) at datomic.error/arg (error.clj:57).
:db.error/insufficient-binding Insufficient binding of db clause: [?e ?a ?v ?t] would cause full scan

@esp1 one way is (first (d/tx-range conn {:start tx :end (inc tx)}))

I'm not sure how/whether it can be done in a query

@esp1 tx-data, See https://docs.datomic.com/on-prem/log.html#log-in-query