Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2024-03-28

Channels

#datomic
<
2024-03-28
>
icemanmelting12:03:22

Currently when '*' is used, it seems like it pulls everything but the references that are not components. Is there a way to include everything even the non component ones?

cch112:03:52

I know of no way to do that... and it would be very very expensive in my database for many entities!

icemanmelting12:03:27

yeah, in my case it is limited, but I guess I need to bite the bullet and build a complete pattern

cch112:03:52

At least it is only data!

Dave Mays18:03:16

Does anyone offer a sync service for Datomic or XTDB similar to what https://electric-sql.com/ and https://www.powersync.com/ offer for Postgres? Would Electric (by Hyperfiddle - not Electric SQL) be the closest thing to this? It is not exactly the same use case - but maybe in tandem with another library would be able to fulfill the same role? (The pieces to fill in might be something to watch for dropped connections and reconnect automatically, and the tricky one - another piece for the CRDT stuff, which sounds tough enough to get right to be a PHD project, and so why I was curious if a service like this targeting Datomic or XTDB already existed?)

respatialized19:03:30

you may be interested in the peer to peer system described here: https://lambdaforge.io/2019/12/08/replicate-datahike-wherever-you-go.html

danbunea07:03:09

this is not only easy to achieve with datomic ( I think also with xtdb ) but also more flexible. Using a websocket you can send back to the client(s) the result (datoms transacted ). It is literally a few lines of code. With electric it's even easier as the transport is done for you optimally.

danbunea07:03:00

In the past, I used a combination of re-posh/datascript on the client and datomic on the server and syncing the datoms between them using a websocket

Dave Mays18:03:26

The piece I'm missing on the datascript side is it doesn't seem like there's a standard practice for persisting the Datascript data when offline. That's one benefit of Electric SQL so far. I'm hoping local client side persistence comes to the similar Asami database though.