Thanks Ben. BTW, Got one more clarification: Say there is a client using ovsdb-idl for all transactions and reading data from ovsdb-server's db. Now the client has started a transaction I.e. txn_create and txn_insert(New row) for row-5 in table-1. But it hasn't committed the txn. Now if the client walks through the table-1 using idl, whether it would see the uncommitted row-5 as well??
Thanks, Arun On Wednesday, May 3, 2017, Ben Pfaff <b...@ovn.org> wrote: > On Wed, May 03, 2017 at 07:53:23PM +0530, Arunkumar Rg wrote: > > Hi All, > > > > I was going through the ovsdb-idl.h file. But I could not understand the > > below comment mentioned in this file: > > > > * The IDL always presents a consistent snapshot of the database to its > > client, > > * that is, it won't present the effects of some part of a transaction > > applied > > * at the database server without presenting all of its effects. > > * > > > > Please share some details, probably some example on the above statement. > > > > I think I understood how monitoring works and some basics of how a > > transaction has to be triggered by the IDL client. But not clear on what > > the above comment mean. > > The database is transactional. If a single transaction modifies two > rows, then the IDL will either show both modifications or neither. > _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
