On Fri, Apr 01, 2016 at 03:46:50AM +0000, Elluru, Krishna Mohan wrote: > I am observing one of the behavior with ovsdb(2.5), for which I would > like to seek clarity. As per the RFC 7047, if a column on table X with > attribute is set to mutable:false, the value can't be changed after > creation and on attempt the constraint violation error would be thrown > to the caller. However, if the column is a weak reference and pointing > to UUID of another table (say y) with mutable:false on the column, and > on row deletion in Y table, what is the intended action on table X's > row?. Currently my observation shows that the corresponding row in > Table X is being deleted. Is this behavior is a bug or intended > behavior?
This is a hole in the constraint system that had not previously been brought to my attention. I'd prefer to solve it by forbidding weak references from immutable columns. Does this suit you? > On the similar note, > > 1. if the column is an index, and a weak reference with mutable:false, the > similar behavior can be expected? > 2. if the column is an index, and a weak reference with mutable:false, and > the table is ROOT table, what behavior should be expected, if the referenced > row is deleted? The solution I suggested above would also eliminate these issues. _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
