HI Ben,
So, the fix is instead of throwing error, we apply mutable:true
property to the weak reference column, though the schema passed it as
mutable:false?
Thanks
Krishna Mohan
-----Original Message-----
From: dev [mailto:[email protected]] On Behalf Of Ryan Moats
Sent: Sunday, April 03, 2016 1:37 AM
To: Ben Pfaff <[email protected]>
Cc: [email protected]
Subject: Re: [ovs-dev] [PATCH] ovsdb: Force columns that contain weak
references to be immutable.
"dev" <[email protected]> wrote on 04/02/2016 11:46:30 AM:
> From: Ben Pfaff <[email protected]>
> To: [email protected]
> Cc: Ben Pfaff <[email protected]>
> Date: 04/02/2016 11:46 AM
> Subject: [ovs-dev] [PATCH] ovsdb: Force columns that contain weak
> references to be immutable.
> Sent by: "dev" <[email protected]>
>
> An immutable weak reference is a hole in the constraint system: if
> referenced rows are deleted, then the weak reference needs to change.
> Therefore, force columsn that contain weak references to be mutable.
>
> Reported-by: "Elluru, Krishna Mohan" <[email protected]>
> Signed-off-by: Ben Pfaff <[email protected]>
> ---
> AUTHORS | 1 +
> ovsdb/column.c | 24 +++++++++++++++---------
> ovsdb/ovsdb-server.1.in | 6 ++++++
> python/ovs/db/schema.py | 8 +++++++-
> tests/ovsdb-schema.at | 19 ++++++++++++++++++-
> 5 files changed, 47 insertions(+), 11 deletions(-)
Acked-by: Ryan Moats <[email protected]>
_______________________________________________
dev mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/dev
_______________________________________________
dev mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/dev
