Re: Applause for ZODB! And a question: How do you get pending change info from a transaction object?

> On Apr 28, 2018, at 1:17 PM, David Pesta <[email protected]> wrote:
> 
> Correct me if I'm wrong, but isn't the _p_changed flag on the object itself?

That is correct. I apologize I have never read the code for the transaction object.  I am more focussed towards the client experience. 

> I read that transactions are more than just ZODB and could also be combined with pretty much anything, so I have a general idea of the strategy you are talking about with MQTT, which I'll spend time looking into. Yes, that would be interesting.
That is also my understanding.  For example emails can be sent out only if the transaction completes.  But again I do not know the details of how all of that works.  I am sure that you can read the source code.  There is always great documentation hidden in the files called interfaces.py


> 
> Subscribing to a tree of objects would be interesting, yes. As long as I can also get surgical and subscribe to specific objects if I want to.
That is why I think that MQTT and ZODB are such a natural fit. Because you can subscribe to any branch of the tree down to a single object.  In fact you could even have a different topic  for every event on the object, and only subscribe to some events.  Or to all the events on any branch of the tree. Or to multiple branches of the tree. 

The reason that I like both MQTT and ZODB is that they get the abstractions correct.  If you have a solid foundation you can build a much higher structure.   Now we just need to merge their transaction machinery.  

Warm Regards
Chris



-- 
You received this message because you are subscribed to the Google Groups "zodb" 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.