Hi. I'm new to datomic, so not sure if I'm missing anything: I recently tried upgrading to the latest version of datomic (5927) in order to use tuples. However, when I specify the schema, I get the following error: :db.error/not-an-entity Unable to resolve entity: :db/tupleTypes

This is when running the following code

(d/transact c
              [{:db/ident :player/location
                :db/valueType :db.type/tuple
                :db/tupleTypes [:db.type/long :db.type/long]
                :db/cardinality :db.cardinality/one}])

@mjmeintjes https://docs.datomic.com/cloud/operation/upgrading.html#datomic-schema

Err thats the cloud doc

One sec

https://docs.datomic.com/on-prem/deployment.html#ugprading-schema

On prem ^

@marshall Excellent, thanks, that worked! I assumed it was something to do with upgrading the schema but couldn't find the right function to call.

(d/administer-system {:uri "DB-URI"
                        :action :upgrade-schema})

:thumbsup:

What's in your deps.edn

Can you create and use a new db on that system?

And you have upgraded the transactor to the latest?

yes, transactor is latest, let me try creating a new db

the transactor crashes after running d/administer-system

Can you open a ticket with support (<mailto:[email protected]|[email protected]>) and include your transactor logs? I can have a look at it tomorrow morning

creating database does work sure, thanks

Ok. Glad that works.

is there any way to call peer function from transactor function?

eg I have myproj.utils.datetime ns with function shift-date and I want to call it from datomic tx function currently I have

Execution error at datomic.error/deserialize-exception (error.clj:154).
Syntax error compiling at (0:0).

I see that the on-cloud Cloudformation templates have been bumped across the board for 480-8770, however only Compute is mentioned in the Release history. To be clear, if I'm on storage-470-8654.1, I don't need to update storage, correct? (doing a quick diff of the two storage templates indicates they aren't identical, though I haven't gone further to see if it's only whitespace)

@grzm Correct. You’ll see here: https://docs.datomic.com/cloud/operation/upgrading.html#how-to-upgrade that you can check when the latest storage update was, and anything more recent than that is compute-only

excluding anything listed as a critical release

hello guys, I am trying to figure out how to make use of websockets with Datomic Cloud. So that pushes are directly sent to the user

just like when using Datomic's tx-report-queue

@dlorencic1337 What have you tried?

Is this anything to be alarmed about (pun intended)? It seems like CloudWatch is having trouble locating the auto-scaling policies for the datomic DynamoDB tables. I’ve updated my stack once or twice via CloudFormation…maybe they’ve been lost somehow?

I’m reading through the pull documentation and it’s referring to a pull syntax like (d/pull db [_release/artists] led-zeppelin) but when I attempt it with (d/pull the-db [_user/recommends] 11263397115183903) I get No such namespace: _user, however with (d/pull the-db [:user/_recommends] 11263397115183903) I get #:user{:_recommends [#:db{:id 66353327713036842}]}. Does anyone have an example with the [_user/recommends] syntax that the documentation is referring to? Am I misunderstanding how it works?

link?

that looks like a typo to me

https://docs.datomic.com/cloud/query/query-pull.html#reverse-lookup

I think that is just a typo

Ok thanks favila.