Hi Vijay, Live queries are mainly designed to be used in reactive architectures, where your application expects a push notification when something changes instead of querying the db periodically. For your needs, I suggest you to take a look at OrientDB hooks http://orientdb.com/docs/last/Hook.html
Thanks Luigi 2016-06-07 21:24 GMT+02:00 Vijay Mendiratta <[email protected]>: > Hi > > I apologise if the question is naive. I wanted to understand what could be > a few possible use cases of the live query feature. > > Let's say - My database state changes but it doesn't change every minute > (or hour). If I execute a live query against my database/class/cluster, I'm > not really expecting the callback to be called anytime soon. But, hey, I > would still want to be notified when there's a state change. > My need with Orientdb is more on lines of ElasticSearch's percolator > bundled with a publish-subscribe system. > > Is live query meant to cater to such use cases too? Or is my understanding > of live query very limited? What could be a few possible use cases for the > live query feature? > > Thanks! > > -- > > --- > 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. > -- --- 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.
