On Wed, Oct 28, 2015 at 05:45:17AM +, Ansari, Shad wrote:
> Ovsdb-idl notifies a client that something changed; it does not track
>
> which table, row changed in what way (insert, modify or delete).
>
> As a result, a client has to scan or reconfigure the entire idl after
>
> ovsdb_idl_run()
Ovsdb-idl notifies a client that something changed; it does not track
which table, row changed in what way (insert, modify or delete).
As a result, a client has to scan or reconfigure the entire idl after
ovsdb_idl_run(). This is presumably fine for typical ovs schemas where
tables are relative
