anyone generating squuids in clojurescript?

i see https://github.com/lbradstreet/cljs-uuid-utils – is this compatible with datomic.api/squuid?

There is an implementation in datascript

is there a way to get the t value of the transaction within a transaction?

@chrisblom (datomic.api/next-t db)

cool thanks, i'll need to create a tx function for this right?

Well I assume that's what it does.

@chrisblom yeah, probably

why do you need this though ?

for syncing with datascript, i want to store the t of latest transaction so i can use it to generate diffs

i could use the transaction id, but the t value is a more readable

but is that not what d/basis-t gives you?

yes, normally it would, but only some of my transactions are relevant for the diffing

i have transaction that update some data model, and transactions that update metrics

and only the data model needs to be synced with datascript

i was tagging each transaction with a type

and using a query to find the latest datamodel transaction

ok thanks, i got it working with the transaction function

maybe i should use separate db's instead

yeah storing derived data is currently a bit hacky in Datomic IMHO

is querying across 2 databases easy? is there a performance penalty?

I don't think there's a performance penalty, but there may be an expressivity penalty, especially when using Datalog rules, and not / not-join / or / or-join clauses

Having said that, you may be able able to circumvent those limitations using db functions in query

yeah, sounds good, i will try that, i don't need complicated queries for my use case

Well there may be an performance penalty too, you may need to go through 2 scalar indexes instead of 1 ref index at some point.

If you run into the expressivity penalties, don't forget that you can use the secondary db as a dumb key-value store using db functions (a dumb key-value store with awesome local caching and time-travel features 😉 )

👍

@curtosis: we use conformity with mount, but we just load all norms when we initialize the datomic connection

I think your idea is mildly crazy, but if you want to do it, the result of running conformity does give you a list of the norms that were transacted, and conceivably you could stash those somewhere and hook them into the component lifecycle

For my use case it's much easier just to load everything all at once so as to ensure the latest code runs against the latest schema. I could see needing to mess around with it in a more finicky manner if you have more complex deployments though

@timgilbert thanks, that’s helpful. Realistically, the codebase isn’t likely to be that disjoint from the schema. The main use case I’m working toward is “build this version using these 4 of 7 available schema chunks”, but I should probably resist the temptation to overabstractify it.

Anyone know of a lib for visualizing datomic schema. Something reminiscent to a generated ERD of sorts, even if the relationships themselves were missing? ED instead of ERD, heh.

@b2berry there’s https://github.com/shaunxcode/datomicism

anyone have a solution for being able to directly upsert entitymaps? would be nice to do something like (d/transact conn [(s/assert ::some-entity (assoc some-entity :prop :val))]) for example

Thanks a lot @wei

reason for doing this over just using :db/add is to validate the entity with spec before putting it in the db