a little confused as it's been awhile since I played with datomic. I am trying pro starter. What I remember doing in the past was setting up license key, storage, adding the postgres driver, adding datomic-pro (not client) to my deps, running the transactor, requiring datomic.api :as d, specify URI, create-db on it, make connection

the docs now refer to starting a peer server, does this start a transactor?

I tried it the old way with the latest datomic-pro library using the URI, but it failed to transact my schema. now trying it with the client library and it's complaining about "SSL doesn't have a valid keystore" when trying to make the client

got it figured out. had some problems with conflicting dependencies that caused a few of the issues, and then there was some confusion over small diffs in the API, like the client using {:tx-data ...} when transacting vs the peer library.

i'm back with more performance questions. last time I found that my query was slow because of some naive mistakes. now the same query is slow because of a not-join across :db/id values.

This is the part of the query that's slowing it down:

(not-join [?c ?u]
  [?v :comment-viewing/user ?u]
  [?v :comment-viewing/comment ?c])

where ?c and ?u are ids

total in the database there are up to 114 ?u datoms, 1649 ?c datoms, and 6846 ?v datoms

the query takes over 5 seconds with the not-join, 500 ms without the not-join, 700 ms when I drop the [?v :comment-viewing/comment ?c] clause, and 99 ms when i drop the [?v :comment-viewing/user ?u] clause.

are :db.type/ref indexed by default?

@stuarthalloway / @marshall: We talked about Html and CSS blowing up the indexing service. Would prepending something like <!-- rev 0x0f32f3ffff --> fix that, if I remove all history on these entities?

@laujensen prepending to the value with something that changes (i.e. the sha of the value itself) would help with the segment size issue Note that enabling noHistory will not remove existing history from an attribute

When I get :restore/collision from datomic restore-db, is there any way to tell it to overwrite without having to manually delete the db?

I’m upset that I have to delete it at all, because I don’t know what that would do to a datomic client/peer connected to it

What am I missing?

@alex438 Why are you restoring into a ‘live’ database? You must restart all peers and transactor after a restore: https://docs.datomic.com/on-prem/backup.html#sec-5

and transactor? aww

It’s more of a “migrate latest real db into a staging db” than “restore into live db”

yeah, you’ll need to restart

if you dont you should get a transactor failover the first time you try to write anyway

What’s the meaning of “You do not need to do anything to a storage (e.g. deleting old files or tables) before or after restoring.“, which seems to be at odds with the :restore/collision error?

what version of Datomic?

datomic-pro-0.9.5561.62 more or less

and you get that error on the peer that is running the restore job?

yes

the transactor is created by the ensure* commands

and I’m calling bin/datomic restore-db file:/etc file:/Users/etc/Desktop/etc datomic:

are you getting “is already in use by a different database” or “database already exists under the name”

It worked if I gave it a db name that didn’t exist yet

> already in use by a different database

ok. yes you can’t ‘fork’ a DB within the same storage under two different names

the basis from which that database was created (call it foo) has been restored into that storage before

oh I read that but didn’t realize that’s the rule I broke, but yeah of course

ok so I can restore, but not update

so if you restore foo into storage then change some stuff in it (and in the original source of foo) then try to backup the original source again and restore into the same storage you’ll see that error

is that something that can be fixed in a later release of datomic - to use new ids for restored data?

b/c those two databases share some history (whatever was there before the original restore), but diverge later

it’s something that could be suggested in our Feature request portal

ok, just wondering if it’s design or implementation

thanks marshall

sure

where's the right place to report an issue with the peer api? I've found that tx-range doesn't work when supplied a tx id for start (but does when using (d/tx->t tx-id))

I'm using [com.datomic/datomic-pro "0.9.5561"]

I saw a video where the presenter mentioned tricking the transactor into inserting custom transaction timestamps. What is the best way to do that?

Fun fact: midtaco is an anagram for datomic

one of my prouder local repo naming moments, thought i'd share

@clojurians873 https://docs.datomic.com/on-prem/best-practices.html#set-txinstant-on-imports