via @whitchapman today if people have thoughts: https://blog.clubhouse.io/auditing-with-reified-transactions-in-datomic-f1ea30610285

feedback welcome 🙂

@kschrader Humm. I thought with the newer datomic, you dont need to use “d/tempid” - you can just use strings. A slight simplification.

I get connection refused when trying to connect to my peer server, any thoughts?

No tempid -> :db.part/user. He want to install this data on :db.part/tx @bherrmann

Ok, makes sense - thanks

Hello everyone... Does anyone have a quick answer to this: What data type should I use to store lattitude and longitude in Datomic?

@maleghast Depends on how you want to query it. Two decimal attributes seems like the most obvious. Datomic doesn't have any spatial-indexing capability, so if you're doing something like looking for entities within a range of latitude/longitude, it will be 2 index hits plus a join.

@stuartsierra Thanks that's very helpful 🙂

If you need true geospatial indexing, you'll need to maintain a separate index in a tool that supports that.

*nods* I am building a postgis database to handle geospatial data, but I want to associate the data I am putting in Datomic with as many attributes as possible, so that the data is richer beyond the bare minimum. I am using Datomic to store daily meteorological observations from a number of measuring stations, and so in defining the stations I am including their location and elevation as attributes.

What's the best way to get a one-off number of transactions in the txor?

(count (seq (d/datoms db :aevt :db/txInstant))) ?

@robert-stuttaford If I'm honest, wanted to make sure that wouldn't blow up my box 😛

But actually, I imagine count is pretty good

i can do this fine and we have in excess of 40 million

Good enough for me!

the problem is t values are sparse, so its not a valid representation of the count at all

Yeah, I noticed that. I also tried txid, but that gave me a different value.

I have two databases, named “dev” and “prod”. I’ve backed up “prod”, and now I want to restore it over “dev”. I get the error “The name ‘dev’ is already in use by a different database.” This is using Dynamo. Is it sufficient to delete and recreate the Dynamo DB, then restore to it?

@eraserhd I believe so

Let’s say I have a bunch of rules. They normally use an implicit database. However, I may want to query against a database and a seq of facts. It’s a little annoying to always have to type the $ arg as an argument to the rule. Is there a convenient way to do like, (with-db $2 ...)

Apparently, if I d/delete-database then d/create-database, I still can’t restore the database because it’s already in use by the other database.

So, it seems if I want to dump and restore different databases, they have to have the same ending segment in the database URI.

Just delete and restore

The restore will create it

@eraserhd ^

ahhh

this worked

Any known issues running Datomic in a Docker container on OSX via docker run my-image based on Pointslope image? (https://github.com/pointslope/docker-datomic). Exception on d/connect:

java.util.concurrent.ExecutionException: org.h2.jdbc.JdbcSQLException: Connection is broken: "java.net.ConnectException: Connection refused: localhost:4335" [90067-171]

docker run 8f4db5ba0824
Launching with Java options -server -Xms1g -Xmx1g -XX:+UseG1GC -XX:MaxGCPauseMillis=50
Starting datomic:, storing data in: dev-data ...
System started datomic:, storing data in: dev-data

You'll need to set alt-host to the ip of the docker machine @petrus

Managed to connect by mapping ports explicitly: docker run -p 4334-4336:4334-4336 0ac10e837e84 Now I'm getting Could not find mydb in catalog

Sounds like you need to create-database

so, I’m trying to initialize a database with a schema, but I’m getting errors about duplicate datoms in the transaction, but the ones it complains about are not duplicates.

{:d1 [63 :db/ident :user/guid 13194139534312 true], :d2 [63 :db/ident :user/email 13194139534312 true]}

"duplicate" meaning conflict @csm

both these datoms cannot be true

entity 63 cannot have both ident :user/guid and :user/email

I’m not specifying 63 anywhere

are you using the same tempid for two different schema maps?

this is the minimum that reproduces?

it is not, no. It is part of a larger schema

which I can’t share

I mean, if I issue this tx in isolation, will it cause an error?

I guess I'll just try

I wasn’t able to reproduce it on my machine, it’s only happening on my colleague’s system. Same version of datomic

works for me with test db

it is suspicious that :user/email lacks a db/id but the other one has

this happened before with two unrelated attributes; I added the :db/id "user/guid" to :user/guid and that worked

so, do I need to specify a temporary :db/id for every attribute?

in theory you don't but that's a new feature

But this sometimes happens when the transactor itself creates a tempid, and the client-set and server-set tempids collide

are you sure this is exactly what hits the d/transact call? no other transformations (e.g. adding tempids) beforehand?

or using a tx function

no tx functions, and I’m reasonably sure nothing adds tempids

we are also going through the peer server

ah, so this is sent from client api

I didn't test that, I just issued it directly

something is fishy

having explicit :db/id is likely going to resolve it

(as a workaround)

but this needs more investigating

yeah, I’m just going to add very unique :db/ids to everything

..which did indeed work

if you are paying for datomic support you should open a ticket @csm

(i.e. if you are licensed)

we have a starter license, and are planning on paying later (we are still only in development now)

@csm You should still open a ticket with us. We'd like to take a look at any repro you could provide.

<mailto:[email protected]|[email protected]>

Can you install db fns using the datomic client api?