Dennis Heihoff
Dennis Heihoff
Sure, I'm familiar with pull but it's slower and not dynamic in the sense that relationships can be traversed downstream.
> The main problem with transacting entities is exactly dynamic relationships. How far to transfer? I see what you mean here. For example, a deep `assoc-in` would result the whole...
Hmm, okay the following is simpler and would work better: 1. treat entities as refs in transactions, e.g. entity `{:db/id 1}` is treated as eid `1` in a transaction. 2....
All good. I might be able to implement this myself. Will keep you posted. Thank you for discussing the idea.
FYI @tonsky implemented this for Datalevin. It preserves all Entity functionality and is fully backwards compatible: https://github.com/juji-io/datalevin/issues/48#issuecomment-862566868 What do you think?
In my experience it eliminates a lot of code. For example, in a UI that uses Entity and passes down its ref entities through a component tree it's nice to...
The common use case where this matters anytime one wants to run a pull query on one database and transact the result into another. In my case I have a...
Have the same issue. Timeouts don't help it either.
The distinction lies in the event source. Are events triggered by the user or code? In my case I want to listen to user triggered events, but also set the...
Thats essentially what I'm doing @alexandrudima. To avoid race conditions I think it would be great to have a way to **know** what caused the event, e.g. the user or...