> > I suppose it would be difficult to track changes on comment updates, as >>> there are no links from comments to posts. What if using a Graph model, >>> with edges (regular or lightweight) connecting posts to comments -- in that >>> case, presumably it would be easier to register changes on any connected >>> posts, no? Would that currently work, or is it something that might be >>> added in the future? >>> >> >> That's right, using edges you can do the live query on the comment and >> then fetch the post navigating the edge backwards. It already works. >> > > Got it. That's good to know. I was actually thinking of going in the > opposite direction, though. So, you have a live query on posts, with > bidirectional edges to comments. When a comment is changed, it would > somehow trigger a "change" event on the linked post, and the live query on > posts would therefore register a change. In RethinkDB, this would be > equivalent to a changefeed on a join (which RethinkDB does not actually yet > support, though it is/was planned sometime in the next release or two). >
@Luigi, not sure if you saw my final comment above. I take it it doesn't work that way now, but would it be feasible/desirable to implement something like that? One additional question -- does OrientDB de-duplicate live queries (i.e., if multiple live queries are made with the same requested query, does OrientDB recognize that and process only one version, sending the changes to all subscribers)? Thanks. Anthony -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
