@mbutler You probably need to flip attribute and entity when using :db.install/_attribute and actually use :db.install/attribute. See here: https://github.com/Datomic/day-of-datomic/blob/master/tutorial/schema_queries.clj

@yonatanel Awesome thanks 🙂

@jaret or @marshall, could you confirm that this is sufficient S3 permissions for a restore process, please?

http://docs.datomic.com/backup.html only shows ”s3:*"

i want to restore from one AWS account’s backup to another AWS account, and don’t want to give write capability to the reading account

read only should be sufficient, but I’m not positive what specific perms that would be (other than get and list objects required for the full nested s3 bucket)

ok, great. i guess i will soon find out the Zen way 🙂

@marshall can one use pull query over a REST endpoint?

@robert-stuttaford sorry 🙂

@karol.adamiec I believe you can use pull in a find specification via REST, but I’d have to double check

if you could throw an example at me that would be great, i am having issues trying to google that

ah

nevermind

made it work 🙂

[:find [(pull ?e [*]) ...] :in $ :where [?e :bracket/name "GT-C1"] ]

@marshall so i q like above, how do i get all entities that do have attr :bracket/name?

:where [?e :bracket/name] is valid datalog

👍

i tried putting in _ :slightly_smiling_face:

_ works as well. lost a bracket ]. Argh.

thanks guys

@marshall or @jaret; curious: does there need to be a running transactor while restoring?

@robert-stuttaford :dev and :free storages currently require a running transactor during restore, because storage resides inside the transactor process.

on other storages

all system processes can be down, run restore, then start transactor and peers

thanks!